[Crash-utility] if it's normal to get into kdb shell when run crash

Hi Experts: Sorry for disturbing you again. When I run crash to debug vmcore, if kernel enable kgdb, it will get into kdb shell directly not crash shell, althrough I can get into crash via execute two go command in kdb shell, not sure if it's normal, do you have some comments on it? When I disnable kgdb in kernel, there will not be this kind of issue, if there is some compatibility problem between kgdb and crash tool? Thanks for your time and happen new year!! /****************************************/ root@localhost:~/coredump>sh testcoredump.sh; sh startcoredump.sh segment[0].mem:0x2000000 memsz:9183232 segment[1].mem:0x28c2000 memsz:65536 segment[2].mem:0x28d2000 memsz:4096 segment[3].mem:0x28d3000 memsz:28672 segment[4].mem:0x2ff5000 memsz:45056 SysRq : Trigger a crash Entering kdb (current=0xdb17f900, pid 822) on processor 1 Oops: (null) due to oops @ 0xc0348f64 NIP: c0348f64 LR: c034974c CTR: c0348f50 REGS: db18ddc0 TRAP: 0300 Not tainted (2.6.34.15-grsec-WR4.3.0.0_cgl) MSR: 00021202 <ME,CE,DE> CR: 20242444 XER: 00000000 DEAR: 00000000, ESR: 00800000 TASK = db17f900[822] 'sh' THREAD: db18c000 CPU: 1 GPR00: 00000001 db18de70 db17f900 00000063 00000000 ffffffff c035e930 00000000 GPR08: 00008000 00000000 00000054 118c6000 20242444 100b84b8 100b0828 100b0904 GPR16: 00000000 00000000 00000000 1006d2d0 00000000 100cc220 1006b530 00000000 GPR24: 00000001 c0780d24 00029202 c0780e08 c0770000 00000000 c08578a4 00000063 NIP [c0348f64] sysrq_handle_crash+0x14/0x20 LR [c034974c] __handle_sysrq+0xcc/0x1d0 Call Trace: [db18de70] [c0349734] __handle_sysrq+0xb4/0x1d0 (unreliable) [db18dea0] [c03498ac] write_sysrq_trigger+0x5c/0x70 [db18deb0] [c01662f0] proc_reg_write+0x80/0xc0 [db18dee0] [c010ec50] vfs_write+0xc0/0x170 [db18df00] [c010ee80] sys_write+0x50/0x110 [db18df40] [c0011d58] ret_from_syscall+0x0/0x4 --- Exception: c01 at 0xff16ba4 LR = 0xfebad5c Instruction dump: [1]more> 39600003 7d605f9e 556b103a 7c005b78 98090003 4e800020 60000000 38000001 3d20c07a 90092170 7c0004ac 39200000 <98090000> 4e800020 60000000 3803ffd0 [1]kdb> [1]kdb> go Catastrophic error detected kdb_continue_catastrophic=0, type go a second time if you really want to continue [1]kdb> go Catastrophic error detected kdb_continue_catastrophic=0, attempting to continue Oops: Kernel access of bad area, sig: 11 [#1] PREEMPT SMP NR_CPUS=4 LTT NESTING LEVEL : 0 P2041 RDB last sysfs file: /sys/devices/system/cpu/cpu3/crash_notes Modules linked in: NIP: c0348f64 LR: c034974c CTR: c0348f50 REGS: db18ddc0 TRAP: 0300 Not tainted (2.6.34.15-grsec-WR4.3.0.0_cgl) MSR: 00021202 <ME,CE,DE> CR: 20242444 XER: 00000000 DEAR: 00000000, ESR: 00800000 TASK = db17f900[822] 'sh' THREAD: db18c000 CPU: 1 GPR00: 00000001 db18de70 db17f900 00000063 00000000 ffffffff c035e930 00000000 GPR08: 00008000 00000000 00000054 118c6000 20242444 100b84b8 100b0828 100b0904 GPR16: 00000000 00000000 00000000 1006d2d0 00000000 100cc220 1006b530 00000000 GPR24: 00000001 c0780d24 00029202 c0780e08 c0770000 00000000 c08578a4 00000063 NIP [c0348f64] sysrq_handle_crash+0x14/0x20 LR [c034974c] __handle_sysrq+0xcc/0x1d0 Call Trace: [db18de70] [c0349734] __handle_sysrq+0xb4/0x1d0 (unreliable) [db18dea0] [c03498ac] write_sysrq_trigger+0x5c/0x70 [db18deb0] [c01662f0] proc_reg_write+0x80/0xc0 [db18dee0] [c010ec50] vfs_write+0xc0/0x170 [db18df00] [c010ee80] sys_write+0x50/0x110 [db18df40] [c0011d58] ret_from_syscall+0x0/0x4 --- Exception: c01 at 0xff16ba4 LR = 0xfebad5c Instruction dump: 39600003 7d605f9e 556b103a 7c005b78 98090003 4e800020 60000000 38000001 3d20c07a 90092170 7c0004ac 39200000 <98090000> 4e800020 60000000 3803ffd0 Sending IPI to other cpus... Bye! Using P2041 RDB machine description ...... /**********************/ Best Regards, James Liu Jianbo | WIND RIVER | Senior Engineer - Technical Support Tel 86 28 65318098 | Cell 86 13558641588 | Fax 86 28 65319983 Manage your support account: https://support.windriver.com Ask a Technical Question https://ask.windriver.com Submit a Service Request https://windriver.force.com/support