From: Greg KH <gregkh@suse.de>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Frans Pop <elendil@planet.nl>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [2.6.25-rc1] System no longer powers off after shutdown
Date: Fri, 15 Feb 2008 13:00:08 -0800 [thread overview]
Message-ID: <20080215210008.GD7583@suse.de> (raw)
In-Reply-To: <b6a2187b0802150052jcfd9c96k2a6abcd1c7fea399@mail.gmail.com>
On Fri, Feb 15, 2008 at 04:52:18PM +0800, Jeff Chua wrote:
> On Fri, Feb 15, 2008 at 2:59 PM, Greg KH <gregkh@suse.de> wrote:
> > I swear someone else sent this in, but my archives don't show it at all.
> > I think the patch below should solve this, but I need someone to test it.
>
> I tested but it doesn't fix the problem for me. May be my problem is
> different ... as my X60s just doesn't power-off on suspend-to-disk.
>
> My .config says ...
> # CONFIG_CPU_FREQ is not set
> # CONFIG_CPU_IDLE is not set
>
>
> On Wed, Feb 13, 2008 at 3:54 PM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
> > due to softlockup changes, and setting CONFIG_DETECT_SOFTLOCKUP=n ...
>
> Also, I've tried CONFIG_DETECT_SOFTLOCKUP=n, but this doesn't fix it either.
Ok, this looks to be something else.
> Here's the last dmesg after suspend-to-disk and hang there...
>
> CPU 1 is now offline
> SMP alternatives: switching to UP code
> PM: Syncing filesystems ... done.
> Freezing user space processes ... (elapsed 0.00 seconds) done.
> Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> PM: Shrinking memory... ^H-^Hdone (0 pages freed)
> PM: Freed 0 kbytes in 0.10 seconds (0.00 MB/s)
> ACPI: Preparing to enter system sleep state S4
> Suspending console(s)
>
> [ ... it just hangs here ... press power-switch does the job, and
> system is able to resume upon powering on ]
Wait, this is a suspend-to-disk issue. Totally different than the "will
not power off" issue.
Can you start a new thread on this, and add the suspend people to it?
thanks,
greg k-h
next prev parent reply other threads:[~2008-02-15 21:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 15:23 [2.6.25-rc0 System no longer powers off after shutdown Frans Pop
2008-02-12 20:39 ` [2.6.25-rc1] " Frans Pop
2008-02-12 20:56 ` Greg KH
2008-02-12 21:45 ` Frans Pop
2008-02-13 7:54 ` Andrew Morton
2008-02-13 8:23 ` Jeff Chua
2008-02-13 9:24 ` Frans Pop
2008-02-13 11:39 ` Frans Pop
2008-02-13 16:58 ` Greg KH
2008-02-13 18:55 ` Rafael J. Wysocki
2008-02-15 6:59 ` Greg KH
2008-02-15 8:52 ` Jeff Chua
2008-02-15 21:00 ` Greg KH [this message]
2008-02-13 19:28 ` Frans Pop
2008-02-14 23:38 ` Yinghai Lu
2008-02-14 23:48 ` Ingo Molnar
2008-02-15 0:06 ` Yinghai Lu
2008-02-15 2:14 ` Yinghai Lu
2008-02-15 3:45 ` Yinghai Lu
2008-02-15 6:52 ` Greg KH
2008-02-15 8:41 ` Yinghai Lu
2008-02-15 20:58 ` Greg KH
2008-02-15 6:57 ` Greg KH
2008-02-15 10:19 ` Frans Pop
2008-02-15 19:38 ` Yinghai Lu
2008-02-15 20:31 ` Yinghai Lu
2008-02-15 20:58 ` Greg KH
2008-02-15 20:58 ` Greg KH
2008-02-13 8:41 ` [2.6.25-rc1] jerky mouse cursor and randoooom key repeats Frans Pop
2008-02-15 23:58 ` Pavel Machek
2008-02-16 1:23 ` Gabriel C
2008-02-16 6:19 ` Mike Galbraith
2008-02-16 10:09 ` Gabriel C
2008-02-16 14:03 ` Mike Galbraith
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=20080215210008.GD7583@suse.de \
--to=gregkh@suse.de \
--cc=elendil@planet.nl \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-acpi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox