I've got a backtrace at a text console:
-----------------------

Call Trace:
[<c01274dc>] run_timer_softirq+0x9c/0x1c0
[<c013a0a2>] tick_program_event+0x32/0x60
[<c0134c65>] hrtimer_interrupt+0x185/0x1c0
[<c013a260>] tick_sched_timer+0x0/0x190
[<c0123f42>] __do_softirq+0x52/0xa0
[<c0123fd5>] do_softirq+0x45/0x50
[<c011155e>] smp_apic_timer_interrupt+0x3e/0x80
[<c010a193>] sched_clock+0x13/0x40
[<c01051b8>] apic_timer_interrupt+0x28/0x30
[<c0116542>] native_safe_halt+0x2/0x10
[<c010261c>] cpu_idle+0x1c/0x70
[<c03fab05>] start_kernel+0x245/0x2d0
[<c03fa370>] unknown_bootoption+0x0/0x1e0
===============
Code: 34 24 74 10 eb 25 8b 43 14 89 da 83 e0 fe 39 f0 75 19 89 cb 89 f0 e8 74 
fe ff ff 39 fb 8b 0b 75 e5 83 c4 0c 89 e8 5b 5e 5f 5d c3 <0f> 0b eb fe 83 ec 0c 
89 74 24 04 89 c6 89 7c 24 08 89 d7 89 1c

EIP: [<c012737c>] cascade+0x6c/0x70 SS:ESP 0068:c03f9f20
Kernel panic - not syncing: Fatal exception in interrupt.

-----------------------------

There were also what appeared to be timestamps at the beginning of each
line.  However, I didn't include these, as they were different each
time, and it took me 3 attempts to get the full trace.  This was because
after a few minutes, the following started to scroll up the screen
(along with some other occasional things which I could not catch):

  zd1211rw 5-4:1.0: Could not allocate skb

Since I had to write down the backtrace on paper by hand, I had to try
again.  The 3rd time, I managed to get the 'Code' bit at the end.  This
time, the backtrace was identical to the above apart from it missed out
the line with 'sched_clock'.  I don't know if that makes a difference to
the interpretation of the 'Code' section or not.

Thanks.

-- 
[hardy] Kernel panic with Zydas wifi and kernel 2.6.24
https://bugs.launchpad.net/bugs/220013
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to