On Thu, Nov 02, 2006 at 05:08:35PM -0500, Dave Anderson wrote:
>
> - Tentatively scheduled as base version for RHEL4-U5.
>
> - The current 2.6.18 x86_64 kernel has changed the IRQ-stack-to-
> process-stack linkage, where until now the link value was a pointer
> to the exception frame on the process stack, but has been changed
> to point to a location on the process stack above the exception
> frame. Because of that, after displaying the trace data from the
> IRQ stack, "bt" would then display an invalid exception frame,
> which was reported as a "possibly bogus exception frame".
> (anderson@xxxxxxxxxx)
>
Hi Dave
With 4.0-3.8 and older versions of crash, I used to see this message
"possibly bogus exception frame" on starting crash. That seems to have
gone now with crash-4.0-3.9. However, I am still getting this message
when I do a bt on the latest crash(kdump generated vmcore).
4.0-3.8 and older versions:
WARNING: possibly bogus exception frame
WARNING: possibly bogus exception frame
KERNEL: /home/rachita/linux-2.6.18-panic-intcontext/vmlinux
DUMPFILE: /kdump/rachita/unwind/vmcore-panic-intcontext
CPUS: 2
DATE: Fri Oct 27 20:43:37 2006
UPTIME: 00:05:12
LOAD AVERAGE: 1.15, 0.81, 0.36
TASKS: 90
NODENAME: llm22
RELEASE: 2.6.18panic-intcontext
VERSION: #9 SMP Fri Oct 27 20:35:38 IST 2006
MACHINE: x86_64 (3600 Mhz)
MEMORY: 8.9 GB
PANIC: ""
PID: 0
COMMAND: "swapper"
TASK: ffffffff805564c0 (1 of 2) [THREAD_INFO: ffffffff806f6000]
CPU: 0
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 0 TASK: ffffffff805564c0 CPU: 0 COMMAND: "swapper"
#0 [ffffffff8064bce8] crash_kexec at ffffffff80152225
#1 [ffffffff8064bd30] machine_kexec at ffffffff8011a739
#2 [ffffffff8064bd70] crash_kexec at ffffffff80152241
#3 [ffffffff8064bdf8] crash_kexec at ffffffff80152225
#4 [ffffffff8064be20] bust_spinlocks at ffffffff8011fd6d
#5 [ffffffff8064be30] panic at ffffffff80131420
#6 [ffffffff8064bef8] hrtimer_run_queues at ffffffff80145f6e
#7 [ffffffff8064bf20] handle_IRQ_event at ffffffff80154432
#8 [ffffffff8064bf50] __do_IRQ at ffffffff8015451f
#9 [ffffffff8064bf58] __do_softirq at ffffffff80136ba3
#10 [ffffffff8064bf90] do_IRQ at ffffffff8010bda1
--- <IRQ stack> ---
#11 [ffffffff806f7f20] ret_from_intr at ffffffff80109b95
[exception RIP: cpu_idle+149]
RIP: ffffffff8010890f RSP: 000000000008e000 RFLAGS: ffffffff8070379c
RAX: ffffffffffffffff RBX: 0000000000000000 RCX: ffffffff80108968
RDX: 0000000000000010 RSI: 0000000000000246 RDI: ffffffff806f7fa0
RBP: ffffffff806f6000 R8: ffffffff80557db8 R9: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffffff803951dc R15: 000000000008e000
ORIG_RAX: 0000000000000018 CS: 20800 SS: 0000
bt: WARNING: possibly bogus exception frame
#12 [ffffffff806f7fd0] x86_64_start_kernel at ffffffff80703296
crash>
On crash-4.0-3.9
crash> bt
PID: 0 TASK: ffffffff805564c0 CPU: 0 COMMAND: "swapper"
#0 [ffffffff8064bce8] crash_kexec at ffffffff80152225
#1 [ffffffff8064bd30] machine_kexec at ffffffff8011a739
#2 [ffffffff8064bd70] crash_kexec at ffffffff80152241
#3 [ffffffff8064bdf8] crash_kexec at ffffffff80152225
#4 [ffffffff8064be20] bust_spinlocks at ffffffff8011fd6d
#5 [ffffffff8064be30] panic at ffffffff80131420
#6 [ffffffff8064bef8] hrtimer_run_queues at ffffffff80145f6e
#7 [ffffffff8064bf20] handle_IRQ_event at ffffffff80154432
#8 [ffffffff8064bf50] __do_IRQ at ffffffff8015451f
#9 [ffffffff8064bf58] __do_softirq at ffffffff80136ba3
#10 [ffffffff8064bf90] do_IRQ at ffffffff8010bda1
--- <IRQ stack> ---
#11 [ffffffff806f7f20] ret_from_intr at ffffffff80109b95
[exception RIP: cpu_idle+149]
RIP: ffffffff8010890f RSP: 000000000008e000 RFLAGS: ffffffff8070379c
RAX: ffffffffffffffff RBX: 0000000000000000 RCX: ffffffff80108968
RDX: 0000000000000010 RSI: 0000000000000246 RDI: ffffffff806f7fa0
RBP: ffffffff806f6000 R8: ffffffff80557db8 R9: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffffff803951dc R15: 000000000008e000
ORIG_RAX: 0000000000000018 CS: 20800 SS: 0000
bt: WARNING: possibly bogus exception frame
#12 [ffffffff806f7fd0] x86_64_start_kernel at ffffffff80703296
On doing a 'help -m' I find that irq_eframe_link is zero..is that ok?
Thanks
Rachita
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
