2.6.36: kernel panic in cascade (Fatal exception in interrupt)

From: Thomas Meyer
Date: Wed Nov 03 2010 - 18:36:41 EST


Hello,

with 2.6.36 I'm starting to see a kernel panic and my system hangs completely.
This is what I could capture, i.e. write down, from the (KMS) text console:

[ 300.000697] Pid: 0, comm: kworker/0:0 Not tainted 2.6.36 #2 MS-7250/MS-7250
[ 300.000815] RIP: 0010:[<ffffffff8105faf4>] [<ffffffff8105faf4>] cascade+0x54/0x7a
[ 300.000953] ...
[ 300.008200] Call Trace:
[ 300.008200] <IRQ>
[ 300.008200] ? run_timer_softirq
[ 300.008200] ? ktime_get
[ 300.008200] ? __do_softirq
[ 300.008200] ? call_softirq
[ 300.008200] ? do_softirq
[ 300.008200] ? irq_exit
[ 300.008200] ? smp_apic_timer_interrupt
[ 300.008200] ? apic_timer_interrupt
[ 300.008200] <EOI>
[ 300.008200] ? _raw_spin_unlock_irq
[ 300.008200] ? finish_task_switch
[ 300.008200] ? schedule
[ 300.008200] ? sched_clock_local
[ 300.008200] ? cpu_idle
[ 300.008200] ? start_secondary
[ 300.008200] Code: 08 48...
[ 300.008200] RIP [<ffffffff8105faf4>] cascade+0x54/0x7a
[ 300.008200] RSP <ffff880002103e40>
[ 300.008200] ---[ end trace 9511a8b4f653d08 ]---
[ 300.008200] Kernel panic - not syncing: Fatal exception in interrupt
[ 300.000697] Pid: 0, comm: kworker/0:0 Tainted: G D 2.6.36 #2
[ 300.008200] Call Trace:
[ 300.008200] <IRQ> [<ffffffff816d6a2c>] ? panic+0xa1/0x1a3
[ 300.008200] ? _raw_spin_unlock_irqrestore
[ 300.008200] ? oops_end
[ 300.008200] ? do_invalid_op
[ 300.008200] ? cascade
[ 300.008200] ? invalid_op
[ 300.008200] ? run_timer_softirq
[ 300.008200] ? ktime_get
[ 300.008200] ? __do_softirq
[ 300.008200] ? call_softirq
[ 300.008200] ? do_softirq
[ 300.008200] ? irq_exit
[ 300.008200] ? smp_apic_timer_interrupt
[ 300.008200] ? apic_timer_interrupt
[ 300.008200] <EOI> ? _raw_spin_unlock_irq
[ 300.008200] ? finish_task_switch
[ 300.008200] ? schedule
[ 300.008200] ? sched_clock_local
[ 300.008200] ? cpu_idle
[ 300.008200] ? start_secondary
[ 300.008200] panic occurred, switching back to text console

Help most appreciated!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/