From: Theodore Tso <tytso@MIT.EDU>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Possible regression? 2.6.26-rc1: X61s failure after suspend/resume
Date: Thu, 8 May 2008 22:44:26 -0400 [thread overview]
Message-ID: <20080509024426.GB8871@mit.edu> (raw)
In-Reply-To: <200805082352.04352.rjw@sisk.pl>
On Thu, May 08, 2008 at 11:52:03PM +0200, Rafael J. Wysocki wrote:
> On Thursday, 8 of May 2008, Theodore Ts'o wrote:
> >
> > I'm running a kernel based off of commit afa26be8 (just six commits
> > after 2.6.26-rc1), and very shortly after I suspend/resume my X61s (with
> > the Intel video chipset), the X server will lock up. I can ssh into
> > the machine remotely, and restart the X server, but the newly restarted
> > X server will shortly lock up again, and the only way to solve the
> > problem is to reboot. If I drop back to a 2.6.25 based kernel, the
> > problem goes away.
> >
> > I've tried bisecting it, but the bisection points picked by git don't
> > boot at all, and given that I'm travelling I havent had much time to try
> > doing more bisecting; since I know a number of kernel developers have
> > Lenovo X61 laptops, I thought before I wasted more time trying to get
> > the git bisection to work, I'd check to see if anyone has seen this
> > problem and if the fix is known. I'll also try the latest bleeding edge
> > kernel and hope it's fixed there....
>
> This looks like another manifestation of
> http://bugzilla.kernel.org/show_bug.cgi?id=10620
Could be. On my system, the X server runs for about 15 seconds to
five minutes before it wedges up and locks up. This is why it took me
a while before I finally figured out that the way to reliably
reproduce the problem was to do a suspend/resume. So it's not
*identical* to the report, but its really close....
When I have more time I'll try to find some actual bisection points
that actually will successfully boot on the X61s laptop, and not die
within 6-8 seconds of the kernel loading.....
- Ted
next prev parent reply other threads:[~2008-05-09 2:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 19:53 Possible regression? 2.6.26-rc1: T61s failure after suspend/resume Theodore Ts'o
2008-05-08 21:48 ` Hugh Dickins
2008-05-09 2:59 ` Theodore Tso
2008-05-09 7:31 ` Hugh Dickins
2008-05-09 11:16 ` Peter Zijlstra
2008-05-09 11:36 ` Hugh Dickins
2008-05-09 11:49 ` Peter Zijlstra
2008-05-09 13:53 ` Theodore Tso
2008-05-09 14:18 ` Carlos R. Mafra
2008-05-09 15:28 ` Glauber Costa
2008-05-09 16:21 ` Hugh Dickins
2008-05-09 16:26 ` Glauber Costa
2008-05-09 16:47 ` Adrian Bunk
2008-05-08 21:52 ` Rafael J. Wysocki
2008-05-09 2:44 ` Theodore Tso [this message]
2008-05-09 9:49 ` Possible regression? 2.6.26-rc1: X61s " Ingo Molnar
2008-05-12 2:03 ` Theodore Tso
2008-05-12 11:35 ` Theodore Tso
2008-05-12 12:28 ` Theodore Tso
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=20080509024426.GB8871@mit.edu \
--to=tytso@mit.edu \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.