From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleksij Rempel Subject: Re: IVB-eDP regression with on latest git Date: Mon, 15 Oct 2012 21:07:33 +0200 Message-ID: <507C5EF5.4010607@fisher-privat.net> References: <507A6735.90102@fisher-privat.net> <507AB4E7.1010300@fisher-privat.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by gabe.freedesktop.org (Postfix) with SMTP id 3E8519F311 for ; Mon, 15 Oct 2012 12:07:36 -0700 (PDT) In-Reply-To: <507AB4E7.1010300@fisher-privat.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Daniel Vetter Cc: Intel Graphics Development List-Id: intel-gfx@lists.freedesktop.org I'll repost it, looks like last message got lost. Am 14.10.2012 14:49, schrieb Oleksij Rempel: > Am 14.10.2012 10:55, schrieb Daniel Vetter: >> On Sun, Oct 14, 2012 at 9:18 AM, Oleksij Rempel >> wrote: >>> With latest kernel (vanilla/master, or intel.drm-next) i do not have >>> image >>> on build in screen (eDP). Hardware Asus Zenbook UX32A. Vendor: 0x8086, >>> Device: 0x0166, Revision: 0x09 (??) >>> Is it know issue? >> >> Nope, this is a new one. Can you grab the dmesg with drm.debug=0xe of >> the broken kernel please? Also, a bisect usually helps a lot, too. >> >> Thanks, Daniel >> > > > I can't access this laptop with broken kernel. > > The patch caused this regression is: > commit 2477367083b3eaa97f87993ab26627a02f350551 > Author: Chris Wilson > Date: Wed Sep 26 16:48:30 2012 +0100 > > drm/i915: Try harder to complete DP training pattern 1 > > In commit cdb0e95bf571dccc1f75fef9bdad21b167ef0b37 > Author: Keith Packard > Date: Tue Nov 1 20:00:06 2011 -0700 > > drm/i915: Try harder during dp pattern 1 link training > > extra passes were made to retry the same voltage and then retry a full > clock reset. However, as coverity pointed out, we never tried the full > clock reset as we broke out of the loop early. > > Signed-off-by: Chris Wilson > Reviewed-by: Damien Lespiau > > > Reverting it makes laptop work again. > -- Regards, Oleksij