After ages, the moderators finally approved my thread. In the meantime i found out at least something about this issue:
- EDID is a kind of informationstring which is published by the LCDs (in this case, the built-in screen of the notebook)
- The way how BT is polling for EDID (and handling the result) is implemented totally noobish and buggy. It simply doesn't work with a lot of displays, escpecially those built-in LCDs in newer notebooks.
- I didn't find a solution/patch
- I found a workaround:
echo 0 > /sys/module/drm_kms_helper/parameters/poll
This stops polling for hotplug-devices, therefore also stops polling+missinterpreting the EDID of the display, therefore stops flooding useless errormessages.
Does anybody have a more sane solution?