From: Egbert Eich <eich@suse.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Egbert Eich <eich@suse.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Egbert Eich <eich@suse.de>, Jani Nikula <jani.nikula@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: HPD flood warning since b8f102e8b
Date: Thu, 24 Oct 2013 15:41:24 +0200 [thread overview]
Message-ID: <21097.9092.222306.970168@linux-qknr.site> (raw)
In-Reply-To: jkosina@suse.cz wrote on Thursday, 24 October 2013 at 08:08:10 +0100
Jiri Kosina writes:
> On Mon, 21 Oct 2013, Egbert Eich wrote:
>
> > > On Thu, 3 Oct 2013, Daniel Vetter wrote:
> > >
> > > > Can you please attach full dmesg from boot up to the first WARN with
> > > > drm.debug=0xe? This really shouldn't happen and indicates a bug
> > > > somewhere ...
> > >
> > > A bit difficult ... I originally thought that it was reliably
> > > reproducible, but now I didn't get it after 10 suspend/resume cycles. Will
> > > keep following it, and once it appears, will send you the dmesg.
> > >
> > Could you check if you get any messages regarding HPD storms after
> > suspend/resume ie messages like:
> > "[drm] HPD interrupt storm detected on connector HDMI-A-1"
> > but without the annouing warn messages?
>
> I have this:
>
> [357128.184113] [drm] HPD interrupt storm detected on connector DP-3: switching from hotplug detection to polling
>
> It appeared in the log approximately 5 seconds after resume has been
> completed.
>
:( You seem to get this on different connector.
Any chance for a 'lspci -n' output?
Cheers,
Egbert.
next prev parent reply other threads:[~2013-10-24 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 9:46 HPD flood warning since b8f102e8b Jiri Kosina
2013-10-03 10:13 ` Daniel Vetter
2013-10-03 14:33 ` Jiri Kosina
2013-10-21 16:46 ` Egbert Eich
2013-10-24 7:08 ` Jiri Kosina
2013-10-24 12:36 ` Jiri Kosina
2013-10-24 13:41 ` Egbert Eich [this message]
2013-10-24 14:02 ` Jiri Kosina
2013-10-11 10:25 ` Jiri Kosina
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=21097.9092.222306.970168@linux-qknr.site \
--to=eich@suse.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eich@suse.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.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