From: Johannes Berg <johannes@sipsolutions.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Dave Vasilevsky <djvasi@gmail.com>, Pavel Machek <pavel@ucw.cz>,
Nigel Cunningham <nigel@suspend2.net>,
Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>,
linux-pm <linux-pm@lists.osdl.org>
Subject: Re: SMP suspend broken due to "swsusp: Change code ordering in disk.c" et al.
Date: Fri, 23 Feb 2007 14:31:59 +0100 [thread overview]
Message-ID: <1172237519.3870.34.camel@johannes.berg> (raw)
In-Reply-To: <1172233076.3870.26.camel@johannes.berg>
[-- Attachment #1.1: Type: text/plain, Size: 551 bytes --]
On Fri, 2007-02-23 at 13:19 +0100, Johannes Berg wrote:
> I can give it a go, but it doesn't look as though it'd help. It still
> freezes all threads before disabling CPUs, and my debugging certainly
> pinpointed to kthread_stop() in the workqueue.
As expected, it prints:
CPU#1 offline
CPU 1 dead (my message when it goes into the dead loop)
kthread_stop: stopping migration/1
kthread_stop: stopping ksoftirq/1
kthread_stop: stopping watchdog/1
kthread_stop: kcryptd/1
kthread_stop: stopping xfsdatad/1
and then hangs.
johannes
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2007-02-23 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 3:29 SMP suspend broken due to "swsusp: Change code ordering in disk.c" et al Johannes Berg
2007-02-23 11:54 ` Rafael J. Wysocki
2007-02-23 12:17 ` Johannes Berg
2007-02-23 13:25 ` Rafael J. Wysocki
2007-02-23 20:23 ` Johannes Berg
2007-02-24 0:01 ` Rafael J. Wysocki
2007-02-24 0:31 ` Johannes Berg
2007-02-24 8:57 ` Rafael J. Wysocki
2007-02-24 20:54 ` Rafael J. Wysocki
2007-02-24 21:07 ` Johannes Berg
2007-03-12 16:57 ` Roman Jarosz
2007-03-12 18:14 ` Rafael J. Wysocki
2007-02-23 13:31 ` Johannes Berg [this message]
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=1172237519.3870.34.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=akpm@osdl.org \
--cc=alexey.y.starikovskiy@linux.intel.com \
--cc=djvasi@gmail.com \
--cc=linux-pm@lists.osdl.org \
--cc=nigel@suspend2.net \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=torvalds@osdl.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