From: Thomas Meyer <thomas@m3y3r.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Milan Broz <mbroz@redhat.com>,
linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: SwSusp to disk doesn't work - Try 2
Date: Sun, 11 Mar 2007 21:04:28 +0100 [thread overview]
Message-ID: <45F460CC.60001@m3y3r.de> (raw)
In-Reply-To: <200703112050.16284.rjw@sisk.pl>
Sorry the systems hangs here:
Mar 11 20:55:46 [kernel] CPU 1 is now offline
Mar 11 20:55:46 [kernel] SMP alternatives: switching to UP code
Mar 11 20:55:46 [kernel] PM: Removing info for No Bus:cpu1
Mar 11 20:55:46 [kernel] PM: Removing info for No Bus:msr1
Mar 11 20:55:46 [kernel] CPU1 is down
Mar 11 20:55:46 [kernel] swsusp debug: Waiting for 5 seconds.
Mar 11 20:55:46 [kernel] Enabling non-boot CPUs ...
Mar 11 20:55:46 [kernel] _cpu_up: before notifier CPU_UP_PREPARE.
Mar 11 20:55:46 [kernel] migration_call: Hi!
Mar 11 20:55:46 [kernel] rcu_cpu_notify: Hi!
Mar 11 20:55:46 [kernel] timer_cpu_notify: Hi!
Mar 11 20:55:46 [kernel] hrtimer_cpu_notify: Hi!
Mar 11 20:55:46 [kernel] cpu_callback: Hi!
Mar 11 20:55:46 [kernel] synchronize_rcu: Befor wait
---> System hangs here. After the first "Before wait" message.
- Last output repeated twice -
Mar 11 20:55:46 [kernel] synchronize_rcu: After wait
Mar 11 20:55:46 [kernel] workqueue_cpu_callback: Hi!
Mar 11 20:55:46 [kernel] topology_cpu_callback: Hi!
Mar 11 20:55:46 [kernel] _cpu_up: after notifier CPU_UP_PREPARE.
Mar 11 20:55:46 [kernel] SMP alternatives: switching to SMP code
Mar 11 20:55:46 [kernel] Booting processor 1/1 eip 3000
Mar 11 20:55:46 [kernel] CPU 1 irqstacks, hard=c0388000 soft=c0386000
Mar 11 20:55:46 [kernel] Initializing CPU#1
next prev parent reply other threads:[~2007-03-11 20:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 18:08 SwSusp to disk doesn't work - Try 2 Thomas Meyer
2007-03-11 18:26 ` Rafael J. Wysocki
2007-03-11 18:37 ` Thomas Meyer
2007-03-11 19:27 ` Rafael J. Wysocki
2007-03-11 19:04 ` Milan Broz
2007-03-11 19:16 ` Thomas Meyer
2007-03-11 19:50 ` Rafael J. Wysocki
2007-03-11 20:04 ` Thomas Meyer [this message]
2007-03-11 19:38 ` Rafael J. Wysocki
2007-03-11 20:23 ` Milan Broz
2007-03-11 20:32 ` Rafael J. Wysocki
2007-03-11 20:28 ` Thomas Meyer
2007-03-11 20:45 ` Rafael J. Wysocki
2007-03-11 20:49 ` Thomas Meyer
2007-03-11 20:57 ` Milan Broz
2007-03-11 21:02 ` Thomas Meyer
2007-03-11 21:09 ` Rafael J. Wysocki
2007-03-11 21:56 ` Thomas Gleixner
2007-03-11 21:57 ` Thomas Meyer
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=45F460CC.60001@m3y3r.de \
--to=thomas@m3y3r.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=pavel@ucw.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