From: Jeff Chua <jeff.chua.linux@gmail.com>
To: tytso@mit.edu
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: suspend-to-ram broken on X61 thinkpads in 2.6.30-rc1?
Date: Sat, 11 Apr 2009 12:58:52 +0800 [thread overview]
Message-ID: <b6a2187b0904102158r5e37860cw2f45bee5578ebcf0@mail.gmail.com> (raw)
In-Reply-To: <900814656-1239422746-cardhu_decombobulator_blackberry.rim.net-2124207137-@bxe1152.bisx.prod.on.blackberry>
On Sat, Apr 11, 2009 at 12:04 PM, Theodore Tso <tytso@mit.edu> wrote:
> So I tried to do a bisect using a reduced config, and I wasn't able to reproduce. So I went back to 2.6.30-rc1 and started playing with configurations. I was able to finally get a reproduction, and I found that the af_packet module seems to be responsible. If I move the modules directory out of the way and reboot, then manually insmod the af_packet module, then suspend, it fails by hanging with the flashing moon LED. If I reboot and don't load the af_packet module, the suspend works. Needless to say this falls into the WTF category. I will do more testing to see what's up...
Latest linux git-pull seems to fix the problem. Suspend-to-ram and
resume now works. I've tried a few times and it works. Reverting the
patch makes it hang during suspend.
Latest git pull from 62b8e680e61d3f48f2a12ee248ca03ea8f376926 to
d848223808c5d21e1b3cea090047e34722c6254b
Thanks,
Jeff.
next prev parent reply other threads:[~2009-04-11 4:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 6:03 Theodore Ts'o
2009-04-10 12:48 ` Rafael J. Wysocki
2009-04-10 13:00 ` Jeff Chua
2009-04-10 16:48 ` Theodore Tso
2009-04-10 17:58 ` Rafael J. Wysocki
2009-04-10 17:57 ` Pavel Machek
2009-04-10 18:08 ` Rafael J. Wysocki
2009-04-11 1:12 ` Jeff Chua
2009-04-11 4:04 ` Theodore Tso
2009-04-11 4:58 ` Jeff Chua [this message]
2009-04-11 10:51 ` Rafael J. Wysocki
2009-04-11 22:33 ` Theodore Tso
2009-04-12 16:49 ` Rafael J. Wysocki
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=b6a2187b0904102158r5e37860cw2f45bee5578ebcf0@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tytso@mit.edu \
/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®