Created an attachment (id=32070)
dmesg output w/ the dump_stack patch
My case is slightly different from the original poster now that I look at it. I don't get a spew of EDID invalid messages, but every time my system does something to try to read the EDID (say, running xrandr -q), a new EDID Invalid message shows up.
That said, it does appear that there are successful calls to drm_get_edid, as this attached file contains quite a few call stacks that are not followed by an EDID error.
Created an attachment (id=32070)
dmesg output w/ the dump_stack patch
My case is slightly different from the original poster now that I look at it. I don't get a spew of EDID invalid messages, but every time my system does something to try to read the EDID (say, running xrandr -q), a new EDID Invalid message shows up.
That said, it does appear that there are successful calls to drm_get_edid, as this attached file contains quite a few call stacks that are not followed by an EDID error.
Let me know if there's more information you need.