Bug 199085
| Summary: | Multiple [drm] Got external EDID base block and 0 extensions messages | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Stuart Foster (smf-linux) |
| Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
| Status: | RESOLVED WILL_FIX_LATER | ||
| Severity: | normal | ||
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 4.14.25 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | dmesg log | ||
|
Description
Stuart Foster
2018-03-12 09:57:56 UTC
Created attachment 274677 [details]
dmesg log
Started getting these "[drm] Got external EDID base block and 0 extensions..." messages with recent 4.14 kernels. Is this a bug or a configuration issue on my part ?
Also present with recent 4.15 kernels. That's an info level message from your use of the edid_firmware option. Been there since 2012. Yes thanks, the message is not new to me but the repeated loading of the firmware edid blob does appear new to me. Why the repeated loading of the firmware blob once should be sufficient ?? If I remove drm_kms_helper.edid_firmware=edid/hp_lp2065.bin from the kernel boot line the messages go away and as far as I can seen no edid data is loaded by the kernel is this the correct behaviour ? thanks The firmware EDID handling was moved at a lower level in the stack to be a more transparent replacement for the display EDID. Without this, many features were erroneously parsed from the display EDID, which was in conflict with the firmware EDID. This means that any time the driver would read the EDID, it gets loaded as the firmware EDID. It's arguably something that should be improved in the driver to not keep reading the EDID so many times over, whether it's display or firmware EDID. Thanks for the explanation, hopefully there will be an improvement in the future. |