From: Oleksij Rempel <bug-track@fisher-privat.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: IVB-eDP regression with on latest git
Date: Sun, 14 Oct 2012 14:49:43 +0200 [thread overview]
Message-ID: <507AB4E7.1010300@fisher-privat.net> (raw)
In-Reply-To: <CAKMK7uGsW2c6kW8QmGvs+nEEhGeEGX9PyWnsHo3ixyPhbkfjYw@mail.gmail.com>
Am 14.10.2012 10:55, schrieb Daniel Vetter:
> On Sun, Oct 14, 2012 at 9:18 AM, Oleksij Rempel
> <bug-track@fisher-privat.net> 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 <chris@chris-wilson.co.uk>
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 <keithp@keithp.com>
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 <chris@chris-wilson.co.uk>
Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
Reverting it makes laptop work again.
--
Regards,
Oleksij
next prev parent reply other threads:[~2012-10-14 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 7:18 IVB-eDP regression with on latest git Oleksij Rempel
2012-10-14 8:55 ` Daniel Vetter
2012-10-14 12:49 ` Oleksij Rempel [this message]
2012-10-15 19:07 ` Oleksij Rempel
2012-10-16 8:03 ` Daniel Vetter
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=507AB4E7.1010300@fisher-privat.net \
--to=bug-track@fisher-privat.net \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.