OK, after four days, this finally crashed again. It gave this message
at the same time as giving the following error:
Feb 1 08:50:45 kirby kernel: [213351.856962] NETDEV WATCHDOG: eth0: transmit
timed out
Feb 1 08:50:45 kirby kernel: [213351.856973] BUG: scheduling while atomic:
swapper/0/0x00000100
...then a million messages:
Feb 1 08:50:45 kirby kernel: [213351.857062] bad: scheduling from the idle
thread!
Feb 1 08:50:45 kirby kernel: [213351.857080] Pid: 0, comm: swapper Not tainted
2.6.24-5-generic #1
Feb 1 08:50:45 kirby kernel: [213351.857084] [dequeue_task_idle+40/64]
dequeue_task_idle+0x28/0x40
Feb 1 08:50:45 kirby kernel: [213351.857088] [dequeue_task+18/48]
dequeue_task+0x12/0x30
Feb 1 08:50:45 kirby kernel: [213351.857094] [deactivate_task+37/64]
deactivate_task+0x25/0x40
Feb 1 08:50:45 kirby kernel: [213351.857097] [schedule+588/1536]
schedule+0x24c/0x600
Feb 1 08:50:45 kirby kernel: [213351.857104] [__wake_up_common+75/128]
__wake_up_common+0x4b/0x80
Feb 1 08:50:45 kirby kernel: [213351.857110] [__mod_timer+157/176]
__mod_timer+0x9d/0xb0
Feb 1 08:50:45 kirby kernel: [213351.857116] [schedule_timeout+74/208]
schedule_timeout+0x4a/0xd0
Feb 1 08:50:45 kirby kernel: [213351.857120] [process_timeout+0/16]
process_timeout+0x0/0x10
Feb 1 08:50:45 kirby kernel: [213351.857125] [schedule_timeout+69/208]
schedule_timeout+0x45/0xd0
Feb 1 08:50:45 kirby kernel: [213351.857130] [msleep+21/32] msleep+0x15/0x20
Feb 1 08:50:45 kirby kernel: [213351.857134] [<f89d4147>]
sis190_soft_reset+0x17/0x30 [sis190]
Feb 1 08:50:45 kirby kernel: [213351.857142] [<f89d43df>]
sis190_hw_start+0x1f/0xa0 [sis190]
Feb 1 08:50:45 kirby kernel: [213351.857147] [<f89d4c82>]
sis190_tx_timeout+0x62/0xc0 [sis190]
Feb 1 08:50:45 kirby kernel: [213351.857152] [printk+27/32] printk+0x1b/0x20
Feb 1 08:50:45 kirby kernel: [213351.857157] [dev_watchdog+196/208]
dev_watchdog+0xc4/0xd0
Feb 1 08:50:45 kirby kernel: [213351.857164] [run_timer_softirq+361/480]
run_timer_softirq+0x169/0x1e0
Feb 1 08:50:45 kirby kernel: [213351.857166] [dev_watchdog+0/208]
dev_watchdog+0x0/0xd0
Feb 1 08:50:45 kirby kernel: [213351.857171] [dev_watchdog+0/208]
dev_watchdog+0x0/0xd0
Feb 1 08:50:45 kirby kernel: [213351.857176] [__do_softirq+130/272]
__do_softirq+0x82/0x110
Feb 1 08:50:45 kirby kernel: [213351.857182] [do_softirq+85/96]
do_softirq+0x55/0x60
Feb 1 08:50:45 kirby kernel: [213351.857186] [irq_exit+109/128]
irq_exit+0x6d/0x80
Feb 1 08:50:45 kirby kernel: [213351.857189]
[smp_apic_timer_interrupt+85/128] smp_apic_timer_interrupt+0x55/0x80
Feb 1 08:50:45 kirby kernel: [213351.857195] [apic_timer_interrupt+40/48]
apic_timer_interrupt+0x28/0x30
Feb 1 08:50:45 kirby kernel: [213351.857203] [mwait_idle_with_hints+70/96]
mwait_idle_with_hints+0x46/0x60
Feb 1 08:50:45 kirby kernel: [213351.857208] [cpu_idle+69/208]
cpu_idle+0x45/0xd0
...I'm hoping that this is the error fixed in 2.6.24.5-9, as per the
changelog.
Francois Romieu (8):
ipg: balance locking in irq handler
ipg: plug Tx completion leak
ipg: fix queue stop condition in the xmit handler
ipg: fix Tx completion irq request
sis190: add cmos ram access code for the SiS19x/968 chipset pair
sis190: remove duplicate INIT_WORK
sis190: mdio operation failure is not correctly detected
sis190: scheduling while atomic error
For the full changelog, see:
http://kerneltrap.org/mailarchive/linux-kernel/2008/1/24/603479
Hardy has only released the 2.6.24.5-8 kernel. I'm gonna hang out
another week or two and see if they release a 5-9, and I'll try that
one. With luck, that's the same problem.
--
[3c900B] NETDEV WATCHDOG: transmit timed out/ Resetting the Tx ring pointer
https://bugs.launchpad.net/bugs/107807
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
