From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-kernel@vger.kernel.org
Subject: Possible regression? 2.6.26-rc1: T61s failure after suspend/resume
Date: Thu, 08 May 2008 15:53:24 -0400 [thread overview]
Message-ID: <E1JuCBA-0002NZ-4E@closure.thunk.org> (raw)
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....
- Ted
next reply other threads:[~2008-05-08 19:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 19:53 Theodore Ts'o [this message]
2008-05-08 21:48 ` Possible regression? 2.6.26-rc1: T61s failure after suspend/resume 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 ` Possible regression? 2.6.26-rc1: X61s " Theodore Tso
2008-05-09 9:49 ` 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=E1JuCBA-0002NZ-4E@closure.thunk.org \
--to=tytso@mit.edu \
--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