From: Jay Lan <jlan@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 Kexec-Kdump kernel patch
Date: Tue, 15 Aug 2006 01:56:27 +0000 [thread overview]
Message-ID: <44E129CB.5060709@sgi.com> (raw)
In-Reply-To: <1155538073.2585.44.camel@linux-znh>
Bob Montgomery wrote:
> On Mon, 2006-08-14 at 14:47 +0800, Zou Nan hai wrote:
>
>>This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
>
>
> Contrary to expectations, my experience with this patch on a 2.6.18-rc4
> kernel is that kexec -l, kexec -e is now working without my adding any
> delays to mptscsih, and the kexec -p, echo c >/proc/sysrq-trigger case
> hangs.
>
> My "got here" printk's on the console indicate:
>
> SysRq : Trigger a crashdump
> machine_crash_shutdown
> device_shootdown
> machine_kexec type: 1
>
> And then it hangs.
Hi,
I got it further down.
>
> My test system: hp A6870A server rx2600
>>From /proc/iomem:
> 04a1f000-3f5e3fff : System RAM
> 10000000-17ffffff : Crash kernel
>
My test system is a zx6000.
Here is from /proc/iomem:
04aaf000-3e417fff : System RAM
10000000-17ffffff : Crash kernel
I used 'make tiger_defconfig', then set on CONFIG_KEXEC,
CONFIG_CRASH_DUMP, and CONFIG_PROC_VMCOR.
Here are shown on console:
SysRq : Trigger a crashdump
kernel BUG at kernel/irq/migration.c:39!
bash[4846]: bugcheck! 0 [1]
Modules linked in: radeon drm agpgart nfs lockd sunrpc binfmt_misc
dm_mirror dmi
Pid: 4846, CPU 0, comm: bash
psr : 00001010085a2010 ifs : 800000000000038b ip : [<a0000001000e2520>]
Notdip is at move_native_irq+0x1a0/0x360
unat: 0000000000000000 pfs : 000000000000038b rsc : 0000000000000003
rnat: 0000000000000000 bsps: 0000000000000000 pr : 000000000059a999
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70033f
csd : 0000000000000000 ssd : 0000000000000000
b0 : a0000001000e2520 b6 : a0000001000bc7c0 b7 : a00000010004ec60
f6 : 1003e00000000000000a0 f7 : 1003e20c49ba5e353f7cf
f8 : 1003e00000000000004e2 f9 : 1003e000000000fa00000
f10 : 1003e000000003b9aca00 f11 : 1003e431bde82d7b634db
r1 : a000000100b663c0 r2 : 0000000000001000 r3 : a000000100910e88
r8 : 000000000000002c r9 : 00000000000000fd r10 : a00000010097c750
r11 : 0000000000000000 r12 : e00000001c157c60 r13 : e00000001c150000
r14 : 0000000000004000 r15 : a000000100910e88 r16 : a000000100910e90
r17 : 0000000000004000 r18 : 0000000000000000 r19 : 0000000000000001
r20 : a000000100985f98 r21 : a000000100985f98 r22 : 0000000000000004
r23 : 0000000000000000 r24 : e00000003f3e0f64 r25 : 0000000000000000
r26 : e00000003f3e0f6c r27 : e00000003f3e0f50 r28 : e00000003f3e0008
r29 : 0000000000000000 r30 : 0000000000000000 r31 : 0000000000000000
Call Trace:
[<a0000001000138e0>] show_stack+0x40/0xa0
spà0000001c1577f0 bspà0000001c1514a8
[<a000000100014540>] show_regs+0x840/0x880
spà0000001c1579c0 bspà0000001c151450
[<a000000100036400>] die+0x1c0/0x2c0
spà0000001c1579c0 bspà0000001c151408
[<a000000100036550>] die_if_kernel+0x50/0x80
spà0000001c1579e0 bspà0000001c1513d0
[<a000000100037c50>] ia64_bad_break+0x270/0x4a0
spà0000001c1579e0 bspà0000001c1513a8
[<a00000010000c320>] ia64_leave_kernel+0x0/0x280
spà0000001c157a90 bspà0000001c1513a8
[<a0000001000e2520>] move_native_irq+0x1a0/0x360
spà0000001c157c60
bspà0000001c151350
[<a00000010004ec90>] iosapic_end_level_irq+0x30/0xe0
spà0000001c157c60
bspà0000001c151330
[<a00000010005d4e0>] machine_crash_shutdown+0x120/0x220
spà0000001c157c60
bspà0000001c151300
[<a0000001000d5890>] crash_kexec+0x70/0xc0
spà0000001c157c60
bspà0000001c1512e0
[<a00000010045ee00>] sysrq_handle_crashdump+0x20/0x40
spà0000001c157e20
bspà0000001c1512b8
[<a00000010045efe0>] __handle_sysrq+0x160/0x300
spà0000001c157e20
bspà0000001c151268
[<a0000001001ba0b0>] write_sysrq_trigger+0xb0/0xe0
spà0000001c157e20
bspà0000001c151238
[<a00000010012fad0>] vfs_write+0x1b0/0x340
spà0000001c157e20
bspà0000001c1511e0
[<a000000100130750>] sys_write+0x70/0xe0
spà0000001c157e20
bspà0000001c151168
[<a00000010000c180>] ia64_ret_from_syscall+0x0/0x20
spà0000001c157e30
bspà0000001c151168
[<a000000000010620>] __kernel_syscall_via_break+0x0/0x20
spà0000001c158000
bspà0000001c151168
<4>hda: lost interrupt
mptscsih: ioc0: attempting task abort! (scà0000003e42ba00)
sd 0:0:0:0:
command: cdb[0]=0x4d: 4d 00 6f 00 00 00 00 00 04 00
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: task abort: SUCCESS (scà0000003e42ba00)
mptscsih: ioc0: attempting task abort! (scà0000003e42ba00)
sd 0:0:0:0:
command: cdb[0]=0x0: 00 00 00 00 00 00
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: task abort: SUCCESS (scà0000003e42ba00)
mptscsih: ioc0: attempting task abort! (scà0000003e429c00)
sd 0:0:0:0:
command: cdb[0]=0x0: 00 00 00 00 00 00
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: task abort: SUCCESS (scà0000003e429c00)
mptscsih: ioc0: attempting task abort! (scà0000003e42bd00)
sd 0:0:0:0:
command: cdb[0]=0x0: 00 00 00 00 00 00
ide-cd: cmd 0x3 timed out
hda: lost interrupt
...
next prev parent reply other threads:[~2006-08-15 1:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 6:47 IA64 Kexec-Kdump kernel patch Zou Nan hai
2006-08-14 21:24 ` Bob Montgomery
2006-08-15 0:47 ` Zou Nan hai
2006-08-15 1:56 ` Jay Lan [this message]
2006-08-15 17:39 ` Bob Montgomery
2006-08-15 19:15 ` Jay Lan
2006-08-15 19:31 ` Bob Montgomery
2006-08-15 19:46 ` Keshavamurthy Anil S
2006-08-15 22:36 ` Zou Nan hai
2006-08-15 22:40 ` Zou Nan hai
2006-08-16 18:25 ` Bob Montgomery
2006-08-16 22:34 ` Jay Lan
2006-08-16 22:46 ` Jay Lan
2006-08-17 0:34 ` Jay Lan
2006-08-17 0:38 ` Jack Steiner
2006-08-17 2:57 ` Horms
2006-08-17 3:56 ` Zou Nan hai
2006-08-17 18:53 ` Jay Lan
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=44E129CB.5060709@sgi.com \
--to=jlan@sgi.com \
--cc=linux-ia64@vger.kernel.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