From: Andrew Morton <akpm@osdl.org>
To: pavel@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-rc4-mm1: something is wrong with swsusp powerdown
Date: Tue, 1 Mar 2005 02:21:16 -0800 [thread overview]
Message-ID: <20050301022116.2bbd55a0.akpm@osdl.org> (raw)
In-Reply-To: <20050301020722.6faffb69.akpm@osdl.org>
Resume on SMP locks up.
Relocating pagedir |
Reading image data (8157 pages): 100% 8157 done.
Stopping tasks: ====|
Freeing memory... done (0 pages freed)
Freezing CPUs (at 1)...Sleeping in:
[<c0103c1d>] dump_stack+0x19/0x20
[<c0133c7f>] smp_pause+0x1f/0x54
[<c010ee27>] smp_call_function_interrupt+0x3b/0x60
[<c01037d4>] call_function_interrupt+0x1c/0x24
[<c0101111>] cpu_idle+0x55/0x64
[<c05929ed>] start_secondary+0x71/0x78
[<00000000>] 0x0
[<cffa5fbc>] 0xcffa5fbc
ok
double fault, gdt at c1203260 [255 bytes]
NMI Watchdog detected LOCKUP on CPU1, eip c0133c96, registers:
Modules linked in: video thermal processor pcc_acpi fan button battery ac
CPU: 1
EIP: 0060:[<c0133c96>] Not tainted VLI
EFLAGS: 00000002 (2.6.11-rc5)
EIP is at smp_pause+0x36/0x54
eax: 00000001 ebx: cffa5f20 ecx: fffbe4e6 edx: cffa5f20
esi: cffa4000 edi: 00000080 ebp: cffa5f58 esp: cffa5f1c
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, threadinfo=cffa4000 task=c18ac540)
Stack: 00000000 0000007b 00680000 80050033 00000000 005d3000 000006f0 00ff0001
c120b260 07ff5f4c c0577000 00000088 cffa0080 c011eed4 cffa5f68 cffa5f68
c010ee27 00000000 00000001 cffa5fa4 c01037d4 00000001 c120b260 fffbe4e5
Call Trace:
[<c0103bf7>] show_stack+0x7b/0x88
[<c0103d36>] show_registers+0x112/0x188
[<c01046f1>] die_nmi+0x41/0x74
[<c010fcb4>] nmi_watchdog_tick+0x54/0xcc
[<c0104797>] default_do_nmi+0x73/0xfc
[<c0104865>] do_nmi+0x39/0x4c
[<c010395c>] nmi_stack_correct+0x1d/0x2a
[<c010ee27>] smp_call_function_interrupt+0x3b/0x60
[<c01037d4>] call_function_interrupt+0x1c/0x24
[<c0101111>] cpu_idle+0x55/0x64
[<c05929ed>] start_secondary+0x71/0x78
[<00000000>] 0x0
[<cffa5fbc>] 0xcffa5fbc
Code: e8 60 e0 24 00 68 0c 7a 40 c0 e8 c2 68 fe ff e8 85 ff fc ff 83 c4 08 f0 ff 05 4c 20 5e c0 a1 50 20 5e c0 89 da 85 c0 74 0b f3
console shuts up ...
next prev parent reply other threads:[~2005-03-01 10:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 23:17 2.6.11-rc4-mm1: something is wrong with swsusp powerdown Pavel Machek
2005-03-01 6:38 ` Laurent Riffard
2005-03-01 9:52 ` Andrew Morton
2005-03-01 10:54 ` Pavel Machek
2005-03-01 11:12 ` Eric W. Biederman
2005-03-01 12:02 ` Pavel Machek
2005-03-01 11:08 ` Eric W. Biederman
2005-03-01 12:08 ` Pavel Machek
2005-03-01 17:33 ` Eric W. Biederman
2005-03-01 10:07 ` Andrew Morton
2005-03-01 10:21 ` Andrew Morton [this message]
2005-03-01 10:56 ` Pavel Machek
2005-03-01 20:35 ` Andrew Morton
2005-03-01 23:39 ` Pavel Machek
2005-03-01 10:48 ` Pavel Machek
2005-03-01 13:10 ` Pavel Machek
2005-03-01 13:12 ` Pavel Machek
2005-03-01 20:38 ` Andrew Morton
2005-03-02 22:57 ` Jindrich Makovicka
2005-03-03 0:30 ` Andrew Morton
2005-03-03 12:38 ` Jindrich Makovicka
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=20050301022116.2bbd55a0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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