linux-kernel - Re: [PATCH] Revert "drm/i915: try to train DP even harder"

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] [day] [month] [year] [list]

Date:	Mon, 18 Mar 2013 10:10:45 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Daniel Vetter <daniel@...ll.ch>
Cc:	Daniel Vetter <daniel.vetter@...ll.ch>,
	Paulo Zanoni <paulo.r.zanoni@...el.com>,
	intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Revert "drm/i915: try to train DP even harder"

At Sun, 17 Mar 2013 22:59:22 +0100,
Daniel Vetter wrote:
> 
> On Mon, Mar 11, 2013 at 06:40:16PM +0100, Takashi Iwai wrote:
> > This reverts commit 0d71068835e2610576d369d6d4cbf90e0f802a71.
> > 
> > Not only that the commit introduces a bogus check (voltage_tries == 5
> > will never meet at the inserted code path), it brings the i915 driver
> > into an endless dp-train loop on HP Z1 desktop machine with IVY+eDP.
> > 
> > At least reverting this commit recovers the framebuffer (but X is
> > still broken by other reasons...)
> > 
> > Cc: <stable@...r.kernel.org>
> > Signed-off-by: Takashi Iwai <tiwai@...e.de>
> Picked up for -fixes, thanks for the patch.

Thanks!

> Adding Paulo since it's his
> patch. To assign proper blame please cc: relevant people when sending out
> reverts.

Well, Paulo was on Cc in the first post, but I dropped in the next
patch series since I've got no reply since then.  (And intel-gfx was
on Cc, so he  could read it anyway...)


Takashi
--
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/