From: Tomas Carnecky <tom@dbservice.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Zhao Yakui <yakui.zhao@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, lenb@kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: Suspned/resume can't work on the 2.6.29-rc1 but it can work well on the 2.6.28
Date: Tue, 20 Jan 2009 13:53:51 +0100 [thread overview]
Message-ID: <4975C95F.7000302@dbservice.com> (raw)
In-Reply-To: <20090120074534.GE16426@elte.hu>
On 01/20/2009 08:45 AM, Ingo Molnar wrote:
> * Zhao Yakui<yakui.zhao@intel.com> wrote:
>
>> Hi, All
>> I do some tests about suspend/resume on my two boxes. One is HP
>> laptop and the other is Asus EEEPC901. The suspend/resume can't work
>> well. Even after core is selected as the test mode, it still can't work
>> well.(echo core> /sys/power/pm_test)
>>
>> Then I do the same test by using the 2.6.28 kernel. And
>> suspend/resume can work well.
>>
>> Of course I will try to use the git-bisect to identify the first bad
>> commit ASAP.
>
> make sure you try this patch from Rafael first (it's not on lkml it
> appears - Rafael, mind resending the patch to this thread?):
>
> Subject: [PATCH] PCI PM: Restore standard config registers of all devices early
> (was: Re: EeePC resume failure - timers)
>
Would that also fix http://bugzilla.kernel.org/show_bug.cgi?id=12492?
I should add that pm_tests freezer, devices and platform work, but
processors fails (I didn't test core since I suppose that when
processors fails, core will fail as well).
tom
next prev parent reply other threads:[~2009-01-20 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 1:08 Suspned/resume can't work on the 2.6.29-rc1 but it can work well on the 2.6.28 Zhao Yakui
2009-01-20 7:45 ` Ingo Molnar
2009-01-20 12:53 ` Tomas Carnecky [this message]
2009-01-20 20:32 ` Rafael J. Wysocki
2009-01-20 22:01 ` [PATCH] PCI PM: Consistently use variable name "error" for pm call return values Frans Pop
2009-01-22 2:06 ` Suspned/resume can't work on the 2.6.29-rc1 but it can work well on the 2.6.28 ykzhao
2009-01-22 12:14 ` 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=4975C95F.7000302@dbservice.com \
--to=tom@dbservice.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=yakui.zhao@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).