From: Keith Packard <keithp@keithp.com>
To: Emmanuel Benisty <benisty.e@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [GIT BISECT] 2c1756b12edc19fdd75c833699cb752e1bbb641e - Display corruption after blank screen state
Date: Thu, 06 Oct 2011 21:54:18 -0600 [thread overview]
Message-ID: <yun4nzllamt.fsf@aiko.keithp.com> (raw)
In-Reply-To: <CA+i8gK+H4Y=+ZMr9QHh-1mn0wEdhDzf4iSqUgD322UhyXoruCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Wed, 7 Sep 2011 23:33:13 +0700, Emmanuel Benisty <benisty.e@gmail.com> wrote:
(I'm sorry I missed this mail; I was preoccupied with family issues
that week).
> The following commit causes display corruption once the machine goes
> out from default X server power saving blank screen state. This is
> with an i3 330m.
Can you provide more information about which display is corrupted and
what the corruption looks like?
> commit 2c1756b12edc19fdd75c833699cb752e1bbb641e
> Merge: cf96e46 d74362c
> Author: Keith Packard <keithp@keithp.com>
> Date: Thu Jul 28 16:30:41 2011 -0700
>
> Merge branch 'drm-intel-fixes' into drm-intel-next
>
Can you provide the output of intel_reg_dumper from both working and
non-working kernels? Reverting this merge would be a fairly substantial
challenge at this point in the release cycle, so I'd like to see if we
can't narrow things down a bit and find the actual code change at fault.
--
keith.packard@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2011-10-07 3:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 16:33 Emmanuel Benisty
2011-10-07 3:54 ` Keith Packard [this message]
2011-10-21 3:01 ` Emmanuel Benisty
2011-10-21 5:28 ` Keith Packard
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=yun4nzllamt.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=benisty.e@gmail.com \
--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
all inboxes | Powered by JetHome®