linux-kernel - Re: HPD flood warning since b8f102e8b

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <21093.23168.424554.698941@linux-qknr.site>
Date:	Mon, 21 Oct 2013 18:46:56 +0200
From:	Egbert Eich <eich@...e.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Daniel Vetter <daniel.vetter@...ll.ch>, Egbert Eich <eich@...e.de>,
	Jani Nikula <jani.nikula@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>
Subject: Re: HPD flood warning since b8f102e8b

Hi Jiri,

Just found your email, it got missed do to a temporary inaccessibility to
my email.

Jiri Kosina writes:
 > 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 cannot find anything obviously wrong in the code. 
However there are several code paths for different hardware though - could 
you give me an 'lspci -n' output so I can narrow them down?

Thanks!
Cheers,
	Egbert.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/