From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Ben Skeggs <bskeggs@redhat.com>, David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [linux-next] DDC responded, but no EDID for %s errors
Date: Thu, 6 Sep 2018 11:42:43 +0900 [thread overview]
Message-ID: <20180906024243.GB749@jagdpanzerIV> (raw)
In-Reply-To: <20180802024648.GA499@jagdpanzerIV>
On (08/02/18 11:46), Sergey Senozhatsky wrote:
> Hi,
>
> My dmesg is filled up with these errors
>
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for HDMI-A-1
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for HDMI-A-1
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
> [..]
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
> nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
> [..]
>
> Basically, a message every 10s or so. Any chance we can make them
> go away?
A gentle ping?
It literally floods my logbuf with that "DRM: DDC responded, but no EDID
for VGA-1" thing.
name -a
4.19.0-rc2-dbg-00118-gb9a3bad8af2d
$ dmesg | tail -42
[ 3615.796938] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3626.036865] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3636.276878] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3646.516866] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3656.756750] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3666.996949] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3677.236884] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3687.476865] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3697.716858] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3707.956934] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3718.196925] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3728.436884] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3738.676861] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3748.916731] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3759.156754] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3769.396861] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3779.636826] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3789.876892] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3800.116686] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3810.356926] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3820.596887] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3830.836909] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3841.076932] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3851.316681] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3861.556926] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3871.796869] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3882.036750] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3892.276836] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3902.516803] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3912.756640] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3922.996957] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3933.236700] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3943.476851] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3953.716928] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3963.956915] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3974.196861] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3984.436928] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 3994.676885] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 4004.917030] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 4015.156935] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 4025.396872] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
[ 4035.636877] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
-ss
next prev parent reply other threads:[~2018-09-06 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 2:46 [linux-next] DDC responded, but no EDID for %s errors Sergey Senozhatsky
2018-09-06 2:42 ` Sergey Senozhatsky [this message]
2018-09-06 2:46 ` Ben Skeggs
2018-09-06 2:49 ` Sergey Senozhatsky
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=20180906024243.GB749@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox