Red Hat Bugzilla – Bug 676408
bt: WARNING: possibly bogus exception frame
Last modified: 2016-02-09 20:33:15 EST
crash> bt 19157 PID: 19157 TASK: ffff8102074080c0 CPU: 7 COMMAND: "dbench" #0 [ffff81023fcd1f20] crash_nmi_callback at ffffffff8007bce5 #1 [ffff81023fcd1f40] do_nmi at ffffffff800658c5 #2 [ffff81023fcd1f50] nmi at ffffffff80064eaf [exception RIP: ia32_sysenter_target] RIP: ffffffff80061408 RSP: 0000000000000000 RFLAGS: 00000046 RAX: 0000000000000006 RBX: 0000000000000009 RCX: 0000000000000000 RDX: 0000000000000005 RSI: 00000000ffdd0f29 RDI: 000000000804a9d5 RBP: 00000000ffdd0e4c R8: 0000000000000000 R9: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 bt: WARNING: possibly bogus exception frame --- <NMI exception stack> --- #3 [ 0] ia32_sysenter_target at ffffffff80061408 bt: cannot transition from exception stack to current process stack: exception stack pointer: ffff81023fcd1f20 process stack pointer: 0 current stack base: ffff8101fc918000 I have verified the same behavior on the upstream crash program. The vmcore and vmlinux files exhibiting this problem are on megatron.gsslab.rdu.redhat.com in /cores/20110207033026/work
Right, and as we discussed, there's no conceivable reason that the RSP should be zero. So, given that it actually *is* a "possibly bogus exception frame", I'm thinking that the crash behavior is more correct as it is than it would be to artificially end the trace.
Created attachment 480234 [details] proposed (upstream) patch for crash-5.1.3 FWIW, this is what I'm going with for the next upstream release. With the patch, the bt output looks like this: crash> bt PID: 19157 TASK: ffff8102074080c0 CPU: 7 COMMAND: "dbench" #0 [ffff81023fcd1f20] crash_nmi_callback at ffffffff8007bce5 #1 [ffff81023fcd1f40] do_nmi at ffffffff800658c5 #2 [ffff81023fcd1f50] nmi at ffffffff80064eaf [exception RIP: ia32_sysenter_target] RIP: ffffffff80061408 RSP: 0000000000000000 RFLAGS: 00000046 RAX: 0000000000000006 RBX: 0000000000000009 RCX: 0000000000000000 RDX: 0000000000000005 RSI: 00000000ffdd0f29 RDI: 000000000804a9d5 RBP: 00000000ffdd0e4c R8: 0000000000000000 R9: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 --- <NMI exception stack> --- #3 [ 0] ia32_sysenter_target at ffffffff80061408 crash> At this point it's unlikely that the crash utility will get approval for a RHEL-5.7 errata release, especially since this is such an extremely unlikely occurrance. Plus it's really quite harmless.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Han, I have the vmcore/vmlinux -- can you set qa_ack+?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0203.html