From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Richard Purdie <rpurdie@rpsys.net>
Subject: Re: [2/2] 2.6.21-rc7: known regressions
Date: Mon, 16 Apr 2007 02:29:21 -0400 [thread overview]
Message-ID: <20070416062921.GB7528@redhat.com> (raw)
In-Reply-To: <20070416011636.GO3691@stusta.de>
On Mon, Apr 16, 2007 at 03:16:37AM +0200, Adrian Bunk wrote:
> On Sun, Apr 15, 2007 at 08:54:46PM -0400, Dave Jones wrote:
> > On Mon, Apr 16, 2007 at 02:37:23AM +0200, Adrian Bunk wrote:
> >
> > > Subject : ThinkPad X60: resume no longer works (PCI related?)
> > > workaround: booting with "hpet=disable"
> > > References : http://lkml.org/lkml/2007/3/13/3
> > > Submitter : Dave Jones <davej@redhat.com>
> > > Jeremy Fitzhardinge <jeremy@goop.org>
> > > Caused-By : PCI merge
> > > commit 78149df6d565c36675463352d0bfe0000b02b7a7
> > > Handled-By : Eric W. Biederman <ebiederm@xmission.com>
> > > Rafael J. Wysocki <rjw@sisk.pl>
> > > Status : unknown
> >
> > note that this workaround doesn't seem to work in all cases.
> > Mine may a slightly different model (I have the tablet version)
> > but disabling hpet shows the same regression.
> > I've been fighting Eric's USB debug cable code in the hope
> > of getting _something_ useful out of it other than a black screen,
> > but I've been getting nowhere with it.
>
> I'm not sure why I thought you two ran into the same regression.
I'm not sure why I never hit the same bug that Jeremy did
(again, maybe subtle hardware differences between our models),
but I finally got somewhere. -rc7 with the same config I've
been testing exhibited exactly the same bug. Disabling
the FB_BACKLIGHT option (and all the FB drivers that 'select' it),
I get a working display on resume again.
This makes a lot of sense. As before, when I resumed, the backlight
wasn't coming back on, but I knew the machine was alive, as
capslock was working. (Amusingly, I never noticed the backlight
wasn't coming back on until tonight, when I started debugging this
with the lights off. Late-night debugging ftw).
I'll try and narrow down exactly where it's failing in the
backlight code next, but it's getting late here, so I may
leave this until tomorrow for further investigation.
Some other clues for anyone playing along at home:
This X60 has Intel graphics. ie, I'm not using any of
the drivers that 'select FB_BACKLIGHT', so somewhere in
the common fb code is code that I'm guessing is dependant
upon the framebuffer driver doing something or other
if FB_BACKLIGHT is set.
(Adding Richard to Cc: as he seems to be responsible for
the FB backlight code from what I can tell.)
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-04-16 6:31 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 0:05 Linux 2.6.21-rc7 Linus Torvalds
2007-04-16 0:37 ` [1/2] 2.6.21-rc7: known regressions Adrian Bunk
2007-04-16 21:44 ` Chuck Ebbert
2007-04-17 10:09 ` Takashi Iwai
2007-04-19 20:03 ` Michal Piotrowski
2007-04-20 10:34 ` Takashi Iwai
2007-04-20 18:18 ` Andrew Morton
2007-04-20 18:26 ` Takashi Iwai
2007-04-23 10:19 ` Takashi Iwai
2007-04-16 0:37 ` [2/2] " Adrian Bunk
2007-04-16 0:54 ` Dave Jones
2007-04-16 1:16 ` Adrian Bunk
2007-04-16 3:44 ` Jeremy Fitzhardinge
2007-04-16 6:29 ` Dave Jones [this message]
2007-04-16 6:54 ` Antonino A. Daplas
2007-04-16 7:23 ` Dave Jones
2007-04-16 7:32 ` Antonino A. Daplas
2007-04-16 7:55 ` Dave Jones
2007-04-16 9:26 ` Richard Purdie
2007-04-17 3:34 ` Dave Jones
2007-04-17 23:48 ` Antonino A. Daplas
2007-04-18 0:35 ` Dave Jones
2007-04-16 10:06 ` Rafael J. Wysocki
2007-04-20 4:57 ` Jeremy Fitzhardinge
2007-04-20 5:03 ` Dave Jones
2007-04-20 5:15 ` Jeremy Fitzhardinge
2007-04-20 5:19 ` Dave Jones
2007-04-20 5:33 ` Jeremy Fitzhardinge
2007-04-20 14:51 ` Dave Jones
2007-04-20 15:28 ` Jeremy Fitzhardinge
2007-04-20 16:03 ` Dave Jones
2007-04-20 17:16 ` Jeremy Fitzhardinge
2007-04-20 17:21 ` Dave Jones
2007-04-21 0:02 ` Jeremy Fitzhardinge
2007-04-21 9:45 ` Rafael J. Wysocki
2007-04-17 0:01 ` Linux 2.6.21-rc7 Chuck Ebbert
2007-04-23 21:48 ` [1/3] 2.6.21-rc7: known regressions (v2) Adrian Bunk
2007-04-23 22:18 ` Greg KH
2007-04-24 9:32 ` Wolfgang Erig
2007-04-25 0:14 ` Greg KH
2007-04-25 0:29 ` Adrian Bunk
2007-04-25 0:51 ` Greg KH
2007-04-25 1:21 ` Adrian Bunk
2007-04-25 8:19 ` Eric W. Biederman
2007-04-25 16:20 ` Wolfgang Erig
2007-04-23 21:48 ` [2/3] " Adrian Bunk
2007-04-23 21:49 ` [3/3] " Adrian Bunk
2007-04-25 11:06 ` Andrew Morton
2007-04-25 11:31 ` Adrian Bunk
2007-04-25 13:01 ` Dave Jones
2007-04-25 13:50 ` Antonino A. Daplas
2007-04-25 13:52 ` Antonino A. Daplas
2007-04-25 14:33 ` Dave Jones
2007-04-25 15:24 ` Antonino A. Daplas
2007-04-25 16:31 ` Dave Jones
2007-04-25 23:00 ` Adrian Bunk
2007-04-25 14:06 ` Jeremy Fitzhardinge
2007-04-25 11:43 ` Ingo Molnar
2007-04-25 13:45 ` Jeff Chua
2007-05-02 21:44 ` Thomas Gleixner
2007-04-25 17:57 ` Ingo Molnar
2007-04-25 18:08 ` john stultz
2007-04-26 0:33 ` Len Brown
2007-04-26 0:49 ` john stultz
2007-04-25 19:34 ` Rafael J. Wysocki
2007-04-25 23:40 ` 2.6.21-rc7: known regressions with patches Adrian Bunk
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=20070416062921.GB7528@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=torvalds@linux-foundation.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
Powered by JetHome