From: "Jeff Chua" <jeff.chua.linux@gmail.com>
To: "Pavel Machek" <pavel@suse.cz>
Cc: "Christian Borntraeger" <borntraeger@de.ibm.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.29-rc1: thinkpad problems during resume
Date: Tue, 13 Jan 2009 21:33:23 +0800 [thread overview]
Message-ID: <b6a2187b0901130533m118e9401k8a7152d6f5982708@mail.gmail.com> (raw)
In-Reply-To: <20090113132805.GE30352@atrey.karlin.mff.cuni.cz>
On Tue, Jan 13, 2009 at 9:28 PM, Pavel Machek <pavel@suse.cz> wrote:
>> Am Dienstag 13 Januar 2009 schrieb Rafael J. Wysocki:
>> > On Tuesday 13 January 2009, Pavel Machek wrote:
>> > > Hi!
>> > >
>> > > Just when I thought long merge window means less problems...
>> > >
>> > > ...suspend seemed to work until last tuesday or so. Now it hanged two
>> > > times; once so hard that power button powercycle did not result in
>> > > booting machine. (thinkpad x60)
>> > >
>> > > I'll do some more tests...
>> >
>> > There are a couple of things you may want to revert, like
>> > 7503bfbae89eba07b46441a5d1594647f6b8ab7d and
>> > a0d4922da2e4ccb0973095d8d29f36f6b1b5f703 .
>> >
>> > Please let me know if that helped.
>>
>> I tested rc1+ these two reverts yesterday on my T61p. Doesnt work. There must
>> be at least one more patch that broke S2R on my thinkpad. In fact, it is cpu
>> hotplug that is broken (unplug works).
>
> I reproduced that: echo 0 > online works, echo 1 > online hangs. Will
> compile SMP-less kernel to verify that there are no more problems...
> Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
I've a X61 running 32-bit and it's able to suspend-to-ram.
Please see "[Bug #12422] 2.6.28-git can't resume from str" if it's
fixes your problem. Try to pull Linus' latest tree first and you need
apply only Rafael's latest patch.
Thanks,
Jeff.
next prev parent reply other threads:[~2009-01-13 13:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 8:13 Pavel Machek
2009-01-13 11:39 ` Rafael J. Wysocki
2009-01-13 12:42 ` Christian Borntraeger
2009-01-13 13:03 ` AW: " Morten P.D. Stevens
2009-01-13 13:28 ` Pavel Machek
2009-01-13 13:33 ` Jeff Chua [this message]
2009-01-16 10:44 ` Pavel Machek
2009-01-16 13:23 ` Jeff Chua
2009-01-17 14:46 ` Christian Borntraeger
2009-01-17 15:48 ` 2.6.29-rc1: [SOLVED] " Christian Borntraeger
2009-01-17 16:49 ` Maciej Rutecki
2009-01-17 19:48 ` Mike Travis
2009-01-17 23:42 ` Christian Borntraeger
2009-01-19 16:59 ` Mike Travis
2009-01-19 17:09 ` Ingo Molnar
2009-01-13 13:05 ` 2.6.29-rc1: " Pavel Machek
2009-01-13 14:06 ` Rafael J. Wysocki
2009-01-13 14:36 ` Pavel Machek
2009-01-13 14:36 ` Pavel Machek
2009-01-13 15:21 ` Jeff Chua
2009-01-16 14:39 ` Pavel Machek
2009-01-16 22:06 ` Rafael J. Wysocki
2009-01-16 23:56 ` Mike Travis
2009-01-17 0:13 ` Rafael J. Wysocki
2009-01-26 15:44 ` Pavel Machek
2009-01-26 16:40 ` 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=b6a2187b0901130533m118e9401k8a7152d6f5982708@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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 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®