From: Bernhard Walle <bwalle@suse.de>
To: Tony Luck <tony.luck@intel.com>, jlan@sgi.com
Cc: kexec@lists.infradead.org, linux-ia64@vger.kernel.org
Subject: kdump broken on Altix 350
Date: Fri, 29 Aug 2008 18:03:02 +0200 [thread overview]
Message-ID: <20080829180302.6e67c26e@halley.suse.de> (raw)
Hi Tony,
your commit
commit 10617bbe84628eb18ab5f723d3ba35005adde143
Author: Tony Luck <tony.luck@intel.com>
Date: Tue Aug 12 10:34:20 2008 -0700
[IA64] Ensure cpu0 can access per-cpu variables in early boot code
broke kdump on our Altix 350. I get following early crash in kdump
kernel:
------------------------------------- 8< ------------------------------
Pid: 1, CPU 0, comm: swapper
psr : 00001010085a6010 ifs : 800000000000038a ip :
[<a0000001004faaf0>] Not tainted (2.6.27-rc2-default)
ip is at __rtnl_register+0x150/0x1a0
unat: 0000000000000000 pfs : 000000000000038b rsc : 0000000000000003
rnat: 0000000000000014 bsps: 000000000001003e pr : 0000000000006581
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
csd : 0000000000000000 ssd : 0000000000000000
b0 : a0000001004fab70 b6 : a0000001002a8de0 b7 : a000000100434340
f6 : 1003e0000000000000000 f7 : 1003e8888888888888889
f8 : 1003e0000000000000000 f9 : 1003e0000000000000001
f10 : 1003e0000000000000f00 f11 : 1003e00000000000000a0
r1 : a000000100c27bf0 r2 : a000000100a3db68 r3 : a000000100a32be0
r8 : 0000005200000051 r9 : a000000100a0ca40 r10 : 000000019873d109
r11 : fffffffe602b9dae r12 : e0000030192cfdf0 r13 : e0000030192c8000
r14 : 0000005200000071 r15 : 0000000000000000 r16 : 0000000000000000
r17 : a000000100a0be40 r18 : a000000100a3acb0 r19 : a000000100a3acb8
r20 : a000000100a32208 r21 : a000000100a321e8 r22 : 0000000000000000
r23 : e000003037449454 r24 : 0000000000000001 r25 : 0000000000000000
r26 : 0000000000000001 r27 : 00000010085a6010 r28 : e000003019298040
r29 : e000003019298030 r30 : 0000000000000000 r31 : a000000100a0ca38
Call Trace:
[<a000000100016320>] show_stack+0x40/0xa0
sp=e0000030192cf9c0 bsp=e0000030192c90b0
[<a000000100016c30>] show_regs+0x850/0x8a0
sp=e0000030192cfb90 bsp=e0000030192c9058
[<a000000100039d90>] die+0x1b0/0x2c0
sp=e0000030192cfb90 bsp=e0000030192c9010
[<a000000100609a00>] ia64_do_page_fault+0x9a0/0xb00
sp=e0000030192cfb90 bsp=e0000030192c8fb0
[<a00000010000c720>] ia64_native_leave_kernel+0x0/0x270
sp=e0000030192cfc20 bsp=e0000030192c8fb0
[<a0000001004faaf0>] __rtnl_register+0x150/0x1a0
sp=e0000030192cfdf0 bsp=e0000030192c8f60
[<a0000001004fab70>] rtnl_register+0x30/0x80
sp=e0000030192cfdf0 bsp=e0000030192c8f28
[<a000000100808a00>] rtnetlink_init+0x180/0x2a0
sp=e0000030192cfdf0 bsp=e0000030192c8f08
[<a000000100809a40>] netlink_proto_init+0x380/0x3e0
sp=e0000030192cfdf0 bsp=e0000030192c8ec8
[<a00000010000a960>] do_one_initcall+0xa0/0x2e0
sp=e0000030192cfdf0 bsp=e0000030192c8e88
[<a0000001007c4700>] kernel_init+0x4c0/0x580
sp=e0000030192cfe30 bsp=e0000030192c8e68
[<a000000100014870>] kernel_thread_helper+0xd0/0x100
sp=e0000030192cfe30 bsp=e0000030192c8e40
[<a00000010000a4c0>] start_kernel_thread+0x20/0x40
sp=e0000030192cfe30 bsp=e0000030192c8e40
Kernel panic - not syncing: Attempted to kill init!
------------------------------------- >8 ------------------------------
Since the code is very IA64-specific and I don't have the time now to
read all data sheets, I need your help to resolve that issue. :)
Bernhard
--
Bernhard Walle, SUSE Linux Products GmbH, Architecture Development
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Bernhard Walle <bwalle@suse.de>
To: Tony Luck <tony.luck@intel.com>, jlan@sgi.com
Cc: kexec@lists.infradead.org, linux-ia64@vger.kernel.org
Subject: kdump broken on Altix 350
Date: Fri, 29 Aug 2008 16:03:02 +0000 [thread overview]
Message-ID: <20080829180302.6e67c26e@halley.suse.de> (raw)
Hi Tony,
your commit
commit 10617bbe84628eb18ab5f723d3ba35005adde143
Author: Tony Luck <tony.luck@intel.com>
Date: Tue Aug 12 10:34:20 2008 -0700
[IA64] Ensure cpu0 can access per-cpu variables in early boot code
broke kdump on our Altix 350. I get following early crash in kdump
kernel:
------------------------------------- 8< ------------------------------
Pid: 1, CPU 0, comm: swapper
psr : 00001010085a6010 ifs : 800000000000038a ip :
[<a0000001004faaf0>] Not tainted (2.6.27-rc2-default)
ip is at __rtnl_register+0x150/0x1a0
unat: 0000000000000000 pfs : 000000000000038b rsc : 0000000000000003
rnat: 0000000000000014 bsps: 000000000001003e pr : 0000000000006581
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
csd : 0000000000000000 ssd : 0000000000000000
b0 : a0000001004fab70 b6 : a0000001002a8de0 b7 : a000000100434340
f6 : 1003e0000000000000000 f7 : 1003e8888888888888889
f8 : 1003e0000000000000000 f9 : 1003e0000000000000001
f10 : 1003e0000000000000f00 f11 : 1003e00000000000000a0
r1 : a000000100c27bf0 r2 : a000000100a3db68 r3 : a000000100a32be0
r8 : 0000005200000051 r9 : a000000100a0ca40 r10 : 000000019873d109
r11 : fffffffe602b9dae r12 : e0000030192cfdf0 r13 : e0000030192c8000
r14 : 0000005200000071 r15 : 0000000000000000 r16 : 0000000000000000
r17 : a000000100a0be40 r18 : a000000100a3acb0 r19 : a000000100a3acb8
r20 : a000000100a32208 r21 : a000000100a321e8 r22 : 0000000000000000
r23 : e000003037449454 r24 : 0000000000000001 r25 : 0000000000000000
r26 : 0000000000000001 r27 : 00000010085a6010 r28 : e000003019298040
r29 : e000003019298030 r30 : 0000000000000000 r31 : a000000100a0ca38
Call Trace:
[<a000000100016320>] show_stack+0x40/0xa0
spà000030192cf9c0 bspà000030192c90b0
[<a000000100016c30>] show_regs+0x850/0x8a0
spà000030192cfb90 bspà000030192c9058
[<a000000100039d90>] die+0x1b0/0x2c0
spà000030192cfb90 bspà000030192c9010
[<a000000100609a00>] ia64_do_page_fault+0x9a0/0xb00
spà000030192cfb90 bspà000030192c8fb0
[<a00000010000c720>] ia64_native_leave_kernel+0x0/0x270
spà000030192cfc20 bspà000030192c8fb0
[<a0000001004faaf0>] __rtnl_register+0x150/0x1a0
spà000030192cfdf0 bspà000030192c8f60
[<a0000001004fab70>] rtnl_register+0x30/0x80
spà000030192cfdf0 bspà000030192c8f28
[<a000000100808a00>] rtnetlink_init+0x180/0x2a0
spà000030192cfdf0 bspà000030192c8f08
[<a000000100809a40>] netlink_proto_init+0x380/0x3e0
spà000030192cfdf0 bspà000030192c8ec8
[<a00000010000a960>] do_one_initcall+0xa0/0x2e0
spà000030192cfdf0 bspà000030192c8e88
[<a0000001007c4700>] kernel_init+0x4c0/0x580
spà000030192cfe30 bspà000030192c8e68
[<a000000100014870>] kernel_thread_helper+0xd0/0x100
spà000030192cfe30 bspà000030192c8e40
[<a00000010000a4c0>] start_kernel_thread+0x20/0x40
spà000030192cfe30 bspà000030192c8e40
Kernel panic - not syncing: Attempted to kill init!
------------------------------------- >8 ------------------------------
Since the code is very IA64-specific and I don't have the time now to
read all data sheets, I need your help to resolve that issue. :)
Bernhard
--
Bernhard Walle, SUSE Linux Products GmbH, Architecture Development
next reply other threads:[~2008-08-29 16:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 16:03 Bernhard Walle [this message]
2008-08-29 16:03 ` kdump broken on Altix 350 Bernhard Walle
2008-08-29 16:05 ` Bernhard Walle
2008-08-29 16:05 ` Bernhard Walle
2008-08-29 20:42 ` Luck, Tony
2008-08-29 20:42 ` Luck, Tony
2008-08-29 20:48 ` Bernhard Walle
2008-08-29 20:48 ` Bernhard Walle
2008-09-10 11:48 ` Bernhard Walle
2008-09-10 11:48 ` Bernhard Walle
2008-09-10 20:21 ` Jay Lan
2008-09-10 20:21 ` Jay Lan
2008-09-27 1:00 ` Jay Lan
2008-09-27 1:00 ` Jay Lan
2008-09-29 20:55 ` Luck, Tony
2008-09-29 20:55 ` Luck, Tony
2008-09-29 23:42 ` Luck, Tony
2008-09-29 23:42 ` Luck, Tony
2008-09-30 0:30 ` Jay Lan
2008-09-30 0:30 ` Jay Lan
2008-10-02 5:13 ` Simon Horman
2008-10-02 5:13 ` Simon Horman
2008-10-02 17:04 ` Jay Lan
2008-10-02 17:04 ` Jay Lan
2008-09-10 12:19 ` Bernhard Walle
2008-09-10 12:19 ` Bernhard Walle
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=20080829180302.6e67c26e@halley.suse.de \
--to=bwalle@suse.de \
--cc=jlan@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.