From: Andi Kleen <ak@suse•de>
To: "Martin J. Bligh" <mbligh@google•com>
Cc: Andrew Morton <akpm@osdl•org>,
linuxppc64-dev@ozlabs•org, linux-kernel@vger•kernel.org
Subject: Re: 2.6.17-rc2-mm1
Date: Mon, 1 May 2006 20:34:26 +0200 [thread overview]
Message-ID: <200605012034.26763.ak@suse.de> (raw)
In-Reply-To: <44561A1E.7000103@google.com>
On Monday 01 May 2006 16:24, Martin J. Bligh wrote:
> double fault: 0000 [1] SMP
> last sysfs file: /devices/pci0000:00/0000:00:06.0/resource
> CPU 0
> Modules linked in:
> Pid: 20519, comm: mtest01 Not tainted 2.6.17-rc3-mm1-autokern1 #1
> RIP: 0010:[<ffffffff8047c8b8>] <ffffffff8047c8b8>{__sched_text_start+1856}
> RSP: 0000:0000000000000000 EFLAGS: 00010082
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff805d9438
> RDX: ffff8100db12c0d0 RSI: ffffffff805d9438 RDI: ffff8100db12c0d0
> RBP: ffffffff805d9438 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
> R13: ffff8100e39bd440 R14: ffff810008003620 R15: 000002b02751726c
> FS: 0000000000000000(0000) GS:ffffffff805fa000(0063) knlGS:00000000f7dd0460
> CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
> CR2: fffffffffffffff8 CR3: 00000000da399000 CR4: 00000000000006e0
> Process mtest01 (pid: 20519, threadinfo ffff8100b1bb4000, task
> ffff8100db12c0d0)
> Stack: ffffffff80579e20 ffff8100db12c0d0 0000000000000001 ffffffff80579f58
> 0000000000000000 ffffffff80579e78 ffffffff8020b0b2 ffffffff80579f58
> 0000000000000000 ffffffff80485520
> Call Trace: <#DF> <ffffffff8020b0b2>{show_registers+140}
> <ffffffff8020b357>{__die+159} <ffffffff8020b3cc>{die+50}
> <ffffffff8020bba6>{do_double_fault+115}
> <ffffffff8020aa91>{double_fault+125}
> <ffffffff8047c8b8>{__sched_text_start+1856} <EOE>
That's really strange - i wonder why the backtracer can't find the original
stack. Should probably add some printk diagnosis here.
Can you send the output with this patch?
Index: linux/arch/x86_64/kernel/traps.c
===================================================================
--- linux.orig/arch/x86_64/kernel/traps.c
+++ linux/arch/x86_64/kernel/traps.c
@@ -238,6 +238,7 @@ void show_trace(unsigned long *stack)
HANDLE_STACK (stack < estack_end);
i += printk(" <EOE>");
stack = (unsigned long *) estack_end[-2];
+ printk("new stack %lx (%lx %lx %lx %lx %lx)\n", stack, estack_end[0], estack_end[-1], estack_end[-2], estack_end[-3], estack_end[-4]);
continue;
}
if (irqstack_end) {
next prev parent reply other threads:[~2006-05-01 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 16:47 2.6.17-rc2-mm1 Martin Bligh
2006-04-28 8:20 ` 2.6.17-rc2-mm1 Andrew Morton
2006-05-01 14:24 ` 2.6.17-rc2-mm1 Martin J. Bligh
2006-05-01 17:07 ` 2.6.17-rc2-mm1 Andrew Morton
2006-05-01 17:14 ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-01 17:19 ` 2.6.17-rc2-mm1 Badari Pulavarty
2006-05-01 17:26 ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-01 17:55 ` 2.6.17-rc2-mm1 Badari Pulavarty
2006-05-01 17:57 ` 2.6.17-rc2-mm1 Martin Bligh
2006-05-01 18:32 ` 2.6.17-rc2-mm1 Andy Whitcroft
2006-05-01 23:29 ` 2.6.17-rc2-mm1 Badari Pulavarty
2006-05-01 18:34 ` Andi Kleen [this message]
2006-05-02 13:20 ` 2.6.17-rc2-mm1 Andy Whitcroft
-- strict thread matches above, loose matches on Subject: below --
2006-04-27 16:50 2.6.17-rc2-mm1 Martin Bligh
2006-04-27 16:54 2.6.17-rc2-mm1 Martin Bligh
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=200605012034.26763.ak@suse.de \
--to=ak@suse$(echo .)de \
--cc=akpm@osdl$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc64-dev@ozlabs$(echo .)org \
--cc=mbligh@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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