From: Andi Kleen <ak@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3] drm: Print bad EDID notices less often
Date: Fri, 27 Sep 2024 04:33:15 -0700 [thread overview]
Message-ID: <ZvaX-0wBGiHd8YHS@tassilo> (raw)
In-Reply-To: <87frplzboj.fsf@intel.com>
On Fri, Sep 27, 2024 at 12:30:04PM +0300, Jani Nikula wrote:
> On Thu, 26 Sep 2024, Andi Kleen <ak@linux.intel.com> 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?
>
> 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.
-Andi
next prev parent reply other threads:[~2024-09-27 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 18:01 [PATCH v3] drm: Print bad EDID notices less often Andi Kleen
2024-09-27 9:30 ` Jani Nikula
2024-09-27 11:33 ` Andi Kleen [this message]
2024-09-27 12:23 ` Jani Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZvaX-0wBGiHd8YHS@tassilo \
--to=ak@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.