On Fri, 27 Sep 2024, Andi Kleen <ak@xxxxxxxxxxxxxxx> wrote: > On Fri, Sep 27, 2024 at 12:30:04PM +0300, Jani Nikula wrote: >> On Thu, 26 Sep 2024, Andi Kleen <ak@xxxxxxxxxxxxxxx> wrote: >> > I have an old monitor that reports a zero EDID block, which results in a >> > warning message. This happens on every screen save cycle, and maybe in >> > some other situations, and over time the whole kernel log gets filled >> > with these redundant messages. >> > >> > Make most of these prints conditional on bad_edid_count like other verbose EDID >> > messages. >> >> Honestly I think merging this would be counter-productive to addressing >> the issue properly. > > You think it's a problem on the host side, not the monitor side? Both. :) Having zero EDID block is an issue with the display, logging excessively about it is an issue on the host side. >> Please just give me the chance to look into it. >> >> Is your zero EDID block the base block or an extension block? > > It's an extension block I believe. Now that should be helpful in detecting display changes, and only logging once per display. Unless you unplug and plug, but that's not so common. BR, Jani. -- Jani Nikula, Intel
