Network card driver failure, stack trace

[Julian Edwards]

My headless server keeps getting this in its syslog after disappearing from the network. A hard reboot seems the only way to recover.

Apr 18 05:45:23 jeeves kernel: [67962.040020] ------------[ cut here ]------------
Apr 18 05:45:23 jeeves kernel: [67962.040043] WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x262/0x270(
)
Apr 18 05:45:23 jeeves kernel: [67962.040048] Hardware name:
Apr 18 05:45:23 jeeves kernel: [67962.040052] NETDEV WATCHDOG: eth0 (skge): transmit queue 0 timed out
Apr 18 05:45:23 jeeves kernel: [67962.040056] Modules linked in: xt_multiport nfsd exportfs nfs lockd nfs_acl auth_rpcgss sunrpc ipt_REJEC
T ipt_LOG xt_limit xt_tcpudp ipt_addrtype xt_state ip6table_filter ip6_tables xt_recent snd_via82xx nf_nat_irc nf_conntrack_irc gameport s
nd_ac97_codec ac97_bus nf_nat_ftp snd_pcm_oss nf_nat snd_mixer_oss nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp snd_pcm snd_page_allo
c snd_mpu401_uart snd_seq_dummy snd_seq_oss nf_conntrack snd_seq_midi iptable_filter snd_rawmidi ip_tables snd_seq_midi_event x_tables snd
_seq snd_timer snd_seq_device hwmon_vid fbcon tileblit font bitblit softcursor ppdev snd edac_core sbp2 psmouse serio_raw edac_mce_amd k8t
emp i2c_viapro soundcore nvidia(P) vga16fb vgastate lp parport_pc shpchp parport raid10 raid456 async_pq async_xor xor async_memcpy async_
raid6_recov raid6_pq async_tx ohci1394 usbhid hid raid1 raid0 via_rhine mii sata_sis pata_via sata_via floppy ieee1394 skge multipath line
ar
Apr 18 05:45:23 jeeves kernel: [67962.040176] Pid: 0, comm: swapper Tainted: P 2.6.32-30-server #59-Ubuntu
Apr 18 05:45:23 jeeves kernel: [67962.040180] Call Trace:
Apr 18 05:45:23 jeeves kernel: [67962.040185] <IRQ> [<ffffffff81067b9b>] warn_slowpath_common+0x7b/0xc0
Apr 18 05:45:23 jeeves kernel: [67962.040203] [<ffffffff81067c41>] warn_slowpath_fmt+0x41/0x50
Apr 18 05:45:23 jeeves kernel: [67962.040211] [<ffffffff81490362>] dev_watchdog+0x262/0x270
Apr 18 05:45:23 jeeves kernel: [67962.040218] [<ffffffff81078be7>] ? mod_timer+0x147/0x230
Apr 18 05:45:23 jeeves kernel: [67962.040226] [<ffffffff81490100>] ? dev_watchdog+0x0/0x270
Apr 18 05:45:23 jeeves kernel: [67962.040232] [<ffffffff810783cb>] run_timer_softirq+0x19b/0x340
Apr 18 05:45:23 jeeves kernel: [67962.040242] [<ffffffff81095720>] ? tick_sched_timer+0x0/0xc0
Apr 18 05:45:23 jeeves kernel: [67962.040249] [<ffffffff810902a3>] ? ktime_get+0x63/0xe0
Apr 18 05:45:23 jeeves kernel: [67962.040257] [<ffffffff8106f117>] __do_softirq+0xb7/0x1f0
Apr 18 05:45:23 jeeves kernel: [67962.040264] [<ffffffff8109530a>] ? tick_program_event+0x2a/0x30
Apr 18 05:45:23 jeeves kernel: [67962.040271] [<ffffffff810142ec>] call_softirq+0x1c/0x30
Apr 18 05:45:23 jeeves kernel: [67962.040277] [<ffffffff81015cb5>] do_softirq+0x65/0xa0
Apr 18 05:45:23 jeeves kernel: [67962.040283] [<ffffffff8106ef15>] irq_exit+0x85/0x90
Apr 18 05:45:23 jeeves kernel: [67962.040291] [<ffffffff815635f1>] smp_apic_timer_interrupt+0x71/0x9c
Apr 18 05:45:23 jeeves kernel: [67962.040298] [<ffffffff81013cb3>] apic_timer_interrupt+0x13/0x20
Apr 18 05:45:23 jeeves kernel: [67962.040301] <EOI> [<ffffffff81038b0b>] ? native_safe_halt+0xb/0x10
Apr 18 05:45:23 jeeves kernel: [67962.040316] [<ffffffff8101b78d>] ? default_idle+0x3d/0x90
Apr 18 05:45:23 jeeves kernel: [67962.040324] [<ffffffff81011e63>] ? cpu_idle+0xb3/0x110
Apr 18 05:45:23 jeeves kernel: [67962.040332] [<ffffffff81545d4b>] ? rest_init+0x6b/0x80
Apr 18 05:45:23 jeeves kernel: [67962.040342] [<ffffffff8188bdeb>] ? start_kernel+0x36d/0x376
Apr 18 05:45:23 jeeves kernel: [67962.040349] [<ffffffff8188b33a>] ? x86_64_start_reservations+0x125/0x129
Apr 18 05:45:23 jeeves kernel: [67962.040356] [<ffffffff8188b438>] ? x86_64_start_kernel+0xfa/0x109
Apr 18 05:45:23 jeeves kernel: [67962.040361] ---[ end trace f41003f3fc4ee7b8 ]---

uname -a:
Linux jeeves 2.6.32-30-server #59-Ubuntu SMP Tue Mar 1 22:46:09 UTC 2011 x86_64 GNU/Linux

version_signature:
Ubuntu 2.6.32-30.59-server 2.6.32.29+drm33.13

lsb_release -rd:
Description: Ubuntu 10.04.2 LTS
Release: 10.04

[Heiko (h-e-noordhof)]

We are seeing this issue on about 6 desktop-hosts. On average 2 out of the 6 hang each day. The problems suddenly appeared more or less on the same day.

We are seeing the same (or very similar) messages in kern.log, and that block of messages in preceded (right above the --[ cut here ]-- line) by a handful of messages like this:

Jun 24 23:05:12 mercury kernel: [33989.493835] 0000:00:19.0: eth0: Detected Tx Unit Hang:
Jun 24 23:05:12 mercury kernel: [33989.493837] TDH <8d>
Jun 24 23:05:12 mercury kernel: [33989.493839] TDT <9a>
Jun 24 23:05:12 mercury kernel: [33989.493840] next_to_use <9a>
Jun 24 23:05:12 mercury kernel: [33989.493841] next_to_clean <8c>
Jun 24 23:05:12 mercury kernel: [33989.493843] buffer_info[next_to_clean]:
Jun 24 23:05:12 mercury kernel: [33989.493844] time_stamp <100336329>
Jun 24 23:05:12 mercury kernel: [33989.493846] next_to_watch <8d>
Jun 24 23:05:12 mercury kernel: [33989.493847] jiffies <10033675e>
Jun 24 23:05:12 mercury kernel: [33989.493848] next_to_watch.status <0>

Sys-info:

root@mercury:/var/log# uname -a
Linux mercury 2.6.32-32-generic #62-Ubuntu SMP Wed Apr 20 21:52:38 UTC 2011 x86_64 GNU/Linux

root@mercury:/var/log# cat /proc/version_signature
Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16

root@mercury:/var/log# lsb_release -rd
Description: Ubuntu 10.04.2 LTS
Release: 10.04

Can I help by providing more information? If so, what kind of info?

Regards, Heiko

[penalvch (penalvch)]

Julian Edwards, thank you for reporting this bug and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Julian Edwards (julian-edwards)]

It appears to be working for me now, at least in Lucid.