Bug 783377 - bt: cannot resolve stack trace
Summary: bt: cannot resolve stack trace
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: crash
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Dave Anderson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-20 07:22 UTC by Cong Wang
Modified: 2013-09-30 02:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-11 01:48:21 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Cong Wang 2012-01-20 07:22:54 UTC
Description of problem:

http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/01/1814/181404/381778/4276923/crash.vmcore.log

On hp-bl460c-02.rhts.eng.bos.redhat.com, we got:

crash> foreach bt
PID: 0      TASK: c0a2e560  CPU: 0   COMMAND: "swapper"
 #0 [c0a07f0c] crash_nmi_callback at c0424fee
 #1 [c0a07f10] notifier_call_chain at c0833b52
 #2 [c0a07f2c] atomic_notifier_call_chain at c0833b95
 #3 [c0a07f38] notify_die at c047bb3b
 #4 [c0a07f50] do_nmi at c0831bc7
 #5 [c0a07f6c] nmi at c08315ef
    EAX: 00000000  EBX: 00000000  ECX: 00000000  EDX: 00000000  EBP: 00f64003 
    DS:  007b      ESI: 00000000  ES:  007b      EDI: c0a2b000  GS:  00e0
    CS:  0060      EIP: c04112e1  ERR: 00000000  EFLAGS: 00000246 
 #6 [c0a07fa0] mwait_idle at c04112e1
 #7 [c0a07fb8] cpu_idle at c040895e

PID: 0      TASK: f7083ab0  CPU: 1   COMMAND: "swapper"
bt: cannot resolve stack trace:
 #0 [f7097df0] crash_nmi_callback at c0424fee
 #1 [f7097df4] notifier_call_chain at c0833b52
 #2 [f7097e10] atomic_notifier_call_chain at c0833b95
 #3 [f7097e1c] notify_die at c047bb3b
 #4 [f7097e34] do_nmi at c0831bc7
 #5 [f7097e50] nmi at c08315ef
    EAX: 8005003b  EBX: f7083ab0  ECX: f624f900  EDX: f7083ab0  EBP: d2c45dc0 
    DS:  007b      ESI: f408f570  ES:  007b      EDI: f7083ab0  GS:  00e0
    CS:  0060      EIP: c04313f3  ERR: 8005003b  EFLAGS: 00000082 
 #6 [f7097e84] native_write_cr0 at c04313f3
bt: text symbols on stack:
    [f7097df4] notifier_call_chain at c0833b54
    [f7097e10] atomic_notifier_call_chain at c0833b9a
    [f7097e1c] notify_die at c047bb40
    [f7097e34] do_nmi at c0831bcc
    [f7097e50] nmi_stack_correct at c08315f4
    [f7097e78] update_wall_time at c04800d8
    [f7097e84] native_write_cr0 at c04313f3
    [f7097e90] __switch_to at c040835b
    [f7097eb4] schedule at c082e833
    [f7097ec0] tick_dev_program_event at c048504f
    [f7097ecc] clockevents_program_event at c0483d9c
    [f7097f0c] hrtimer_forward at c0479d23
    [f7097f44] hrtimer_start_range_ns at c047b010
    [f7097f58] tick_nohz_restart_sched_tick at c0486035
    [f7097f7c] cpu_idle at c0408995
    [f7097f98] start_secondary at c082a5f5
bt: possible exception frame:
  KERNEL-MODE EXCEPTION FRAME AT f7097e54:
    [exception EIP: native_write_cr0+3]
    EAX: 8005003b  EBX: f7083ab0  ECX: f624f900  EDX: f7083ab0  EBP: d2c45dc0 
    DS:  007b      ESI: f408f570  ES:  007b      EDI: f7083ab0  GS:  00e0
    CS:  0060      EIP: c04313f3  ERR: 8005003b  EFLAGS: 00000082 


Version-Release number of selected component (if applicable):
crash 5.1.8-1.el6

Additional info:
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/01/1814/181404/381778/4276923/crash.vmcore.log

https://beaker.engineering.redhat.com/recipes/381778

Comment 1 Cong Wang 2012-01-20 07:24:16 UTC
hp-bl460c-02.rhts.eng.bos.redhat.com is marked as broken in beaker now, we can get the vmcore after it is ready.

Comment 5 Dave Anderson 2012-07-10 15:13:43 UTC
Unless the vmcore can be provided, it is impossible to debug this
backtrace issue.

Comment 6 Dave Anderson 2012-07-10 15:16:29 UTC
Please either provide the vmcore or close this BZ.  If it can be reproduced,
and the vmcore provided, then a new BZ can be opened, or this one can be
re-opened.

Comment 7 Cong Wang 2012-07-11 01:48:21 UTC
That machine is still broken... let's close it now.


Note You need to log in before you can comment on or make changes to this bug.