NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out

[[e-mail]]

No comment.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nadasjozef 2185 F.... pulseaudio
 /dev/snd/pcmC1D0c: Slmodemd 1274 F...m slmodemd
 /dev/snd/pcmC1D0p: Slmodemd 1274 F...m slmodemd
 /dev/snd/controlC1: Slmodemd 1274 F.... slmodemd
CRDA: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár
Card0.Amixer.info:
 Card hw:0 'V8237'/'VIA 8237 with unknown codec at 0x1800, irq 11'
   Mixer name : 'VIA Technologies id 23'
   Components : 'AC97a:56494123'
   Controls : 28
   Simple ctrls : 17
Card1.Amixer.info:
 Card hw:1 'modem'/'VIA 82XX modem at 0x1c00, irq 11'
   Mixer name : '0x4d4f5466 MOT'
   Components : 'AC97m:4d4f5466'
   Controls : 2
   Simple ctrls : 2
Card1.Codecs.codec97.0.mc97.1.1:
 1-1/0: 0x4d4f5466 MOT

 Extended modem ID: codec=1 LIN1
 Modem status : GPIO MREF ADC1 DAC1 PRE(ADC2) PRF(DAC2) PRG(HADC) PRH(HDAC)
 Line1 rate : 8000Hz
Date: Sat Oct 17 12:14:42 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=4fd4e09e-bfa0-4194-9261-0e13531c55d5
MachineType: VIA VN800
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=fb9668ae-7ed4-44bd-aa41-bdf98a420ef1 ro noapic quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 09/27/2006
dmi.bios.vendor: Phoenix
dmi.bios.version: 2004 Q1
dmi.board.name: VN800
dmi.board.vendor: VIA
dmi.board.version: VT6297A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvr2004Q1:bd09/27/2006:svnVIA:pnVN800:pvrVT6297A:rvnVIA:rnVN800:rvrVT6297A:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VN800
dmi.product.version: VT6297A
dmi.sys.vendor: VIA

[Jack Nihil (jnihil)]

My Shuttle box also suffers from this problem after upgrading to 9.10 (9.04 was fine). Ethernet chip periodically locks up - about once a day with the following log:

Nov 3 19:24:39 cube kernel: [ 9782.746442] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Nov 3 19:24:39 cube kernel: [ 9782.747134] EXT3 FS on sdb1, internal journal
Nov 3 19:24:39 cube kernel: [ 9782.747140] EXT3-fs: mounted filesystem with writeback data mode.
Nov 3 19:34:05 cube kernel: [10349.127358] usb 1-2: USB disconnect, address 6
Nov 3 20:46:36 cube kernel: [14699.989023] ------------[ cut here ]------------
Nov 3 20:46:36 cube kernel: [14699.989045] WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog+0x1f6/0x210()
Nov 3 20:46:36 cube kernel: [14699.989052] Hardware name: SK22V10
Nov 3 20:46:36 cube kernel: [14699.989056] NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Nov 3 20:46:36 cube kernel: [14699.989061] Modules linked in: isofs udf crc_itu_t nls_iso8859_1 nls_cp437 vfat fat usb_storage binfmt_misc ppdev snd_usb_audio snd_usb_lib snd_hwdep gspca_stv06xx gspca_zc3xx gspca_main iptable_filter videodev v4l1_compat ip_tables x_tables snd_via82xx gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_mpu401_uart lp snd_seq_dummy psmouse keyspan_remote k8temp i2c_viapro shpchp nvidia(P) serio_raw parport snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore ohci1394 via_rhine mii ieee1394 sata_via amd64_agp agpgart
Nov 3 20:46:36 cube kernel: [14699.989153] Pid: 0, comm: swapper Tainted: P 2.6.31-14-generic #48-Ubuntu
Nov 3 20:46:36 cube kernel: [14699.989159] Call Trace:
Nov 3 20:46:36 cube kernel: [14699.989173] [<c014518d>] warn_slowpath_common+0x6d/0xa0
Nov 3 20:46:36 cube kernel: [14699.989182] [<c04b07c6>] ? dev_watchdog+0x1f6/0x210
Nov 3 20:46:36 cube kernel: [14699.989190] [<c04b07c6>] ? dev_watchdog+0x1f6/0x210
Nov 3 20:46:36 cube kernel: [14699.989198] [<c0145206>] warn_slowpath_fmt+0x26/0x30
Nov 3 20:46:36 cube kernel: [14699.989206] [<c04b07c6>] dev_watchdog+0x1f6/0x210
Nov 3 20:46:36 cube kernel: [14699.989215] [<c0120065>] ? __assign_irq_vector+0xc5/0x1c0
Nov 3 20:46:36 cube kernel: [14699.989223] [<c05707da>] ? _spin_lock_irqsave+0x2a/0x40
Nov 3 20:46:36 cube kernel: [14699.989230] [<c01508d0>] ? add_timer_on+0x70/0xc0
Nov 3 20:46:36 cube kernel: [14699.989237] [<c01501b7>] run_timer_softirq+0x117/0x200
Nov 3 20:46:36 cube kernel: [14699.989248] [<c016a125>] ? tick_dev_program_event+0x45/0xe0
Nov 3 20:46:36 cube kernel: [14699.989256] [<c04b05d0>] ? dev_watchdog+0x0/0x210
Nov 3 20:46:36 cube kernel: [14699.989264] [<c014b3b0>] __do_softirq+0x90/0x1a0
Nov 3 20:46:36 cube kernel: [14699.989274] [<c015ff63>] ? hrtimer_interrupt+0x183/0x210
Nov 3 20:46:36 cube kernel: [14699.989282] [<c014b4fd>] do_softirq+0x3d/0x40
Nov 3 20:46:36 cube kernel: [14699.989288] [<c014b63d>] irq_exit+0x5d/0x70
Nov 3 20:46:36 cube kernel: [14699.989295] [<c011dcf7>] smp_apic_timer_interrupt+0x57/0x90
Nov 3 20:46:36 cube kernel: [14699.989303] [<c0103d71>] apic_timer_interrupt+...

[Jack Nihil (jnihil)]

Loaded Ubuntu 9.10 from scratch and not via update-manager and 9.04. Problem has not returned.

Please ignore my comments for now.

[blueraccoon (blueraccoon)]

I'm seeing the same thing periodically on my Shuttle PC with a clean install of 9.10. This never happened with 9.04, but i've possibly seen it with pre-9.04 versions (i say possibly because the behavior was the same but i never checked the kernel log).

[besson3c (joe-netmusician)]

I'm getting this too after the upgrade to 9.10... It occurs enough to be a significant problem for me, I'm also on a Shuttle.

I'd really rather not wipe and reinstall, although I'm open to a dirty reinstall if this will help. Seems like a rather bogus sort of solution though...

[Jack Nihil (jnihil)]

I take my previous comment back. This occurs with a clean install on a Shuttle SK22V10 with 9.10.

Here my latest messages log:

Nov 15 16:37:07 cube kernel: [338855.220066] usb 4-1: USB disconnect, address 2
Nov 15 16:37:07 cube kernel: [338855.220246] gspca: disconnect complete
Nov 15 16:59:35 cube kernel: [340203.511700] usb 1-2: USB disconnect, address 2
Nov 15 17:22:10 cube kernel: [341558.673739] eth0: link down
Nov 15 17:22:23 cube kernel: [341572.047070] eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
Nov 15 18:40:07 cube kernel: [346235.989022] ------------[ cut here ]------------
Nov 15 18:40:07 cube kernel: [346235.989044] WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog+0x1f6/0x210()
Nov 15 18:40:07 cube kernel: [346235.989051] Hardware name: SK22V10
Nov 15 18:40:07 cube kernel: [346235.989056] NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Nov 15 18:40:07 cube kernel: [346235.989061] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat isofs udf crc_itu_t binfmt_misc ppdev snd_via82xx gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_usb_audio snd_mixer_oss snd_usb_lib snd_seq_dummy snd_pcm snd_page_alloc snd_mpu401_uart snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_timer snd_seq_device iptable_filter snd_hwdep ip_tables snd nvidia(P) soundcore x_tables gspca_stv06xx i2c_viapro psmouse k8temp shpchp serio_raw gspca_zc3xx gspca_main videodev v4l1_compat lp parport usb_storage via_rhine mii ohci1394 ieee1394 sata_via amd64_agp agpgart
Nov 15 18:40:07 cube kernel: [346235.989154] Pid: 0, comm: swapper Tainted: P 2.6.31-14-generic #48-Ubuntu
Nov 15 18:40:07 cube kernel: [346235.989159] Call Trace:
Nov 15 18:40:07 cube kernel: [346235.989173] [<c014518d>] warn_slowpath_common+0x6d/0xa0
Nov 15 18:40:07 cube kernel: [346235.989183] [<c04b07c6>] ? dev_watchdog+0x1f6/0x210
Nov 15 18:40:07 cube kernel: [346235.989191] [<c04b07c6>] ? dev_watchdog+0x1f6/0x210
Nov 15 18:40:07 cube kernel: [346235.989199] [<c0145206>] warn_slowpath_fmt+0x26/0x30
Nov 15 18:40:07 cube kernel: [346235.989208] [<c04b07c6>] dev_watchdog+0x1f6/0x210
Nov 15 18:40:07 cube kernel: [346235.989218] [<c0127c38>] ? default_spin_lock_flags+0x8/0x10
Nov 15 18:40:07 cube kernel: [346235.989227] [<c05707da>] ? _spin_lock_irqsave+0x2a/0x40
Nov 15 18:40:07 cube kernel: [346235.989237] [<c030719b>] ? blk_rq_timed_out_timer+0x10b/0x120
Nov 15 18:40:07 cube kernel: [346235.989245] [<c01501b7>] run_timer_softirq+0x117/0x200
Nov 15 18:40:07 cube kernel: [346235.989256] [<c016a125>] ? tick_dev_program_event+0x45/0xe0
Nov 15 18:40:07 cube kernel: [346235.989265] [<c04b05d0>] ? dev_watchdog+0x0/0x210
Nov 15 18:40:07 cube kernel: [346235.989274] [<c014b3b0>] __do_softirq+0x90/0x1a0
Nov 15 18:40:07 cube kernel: [346235.989283] [<c015ff63>] ? hrtimer_interrupt+0x183/0x210
Nov 15 18:40:07 cube kernel: [346235.989291] [<c014b4fd>] do_softirq+0x3d/0x40
Nov 15 18:40:07 cube kernel: [346235.989298] [<c014b63d>] irq_exit+0x5d/0x70
Nov 15 18:40:07 cube kernel: [346235.989306] [<c011dcf7>] smp_apic_timer_interrupt+0x57/0x90
Nov 15 18:40:07 cube kernel: [346235.989314] [<c0103d71>] apic_timer_interrupt+0x31...

[besson3c (joe-netmusician)]

I found some pretty old threads that dealt with this problem in other OSes and the recommendation was to add "noapic" to the kernel boot. Have you played around with any of these options? I've added noapic, and I will report back if I'm still able to reproduce this problem.

[besson3c (joe-netmusician)]

Since adding noapic I have had two complete freezes. I have no idea if this is related, but the last few lines in /var/log/messages before the crash were:

Nov 17 05:04:05 mymachine kernel: [89002.594109] ata4: soft resetting link
Nov 17 05:04:05 mymachine kernel: [89002.791732] ata4.00: configured for UDMA/133
Nov 17 05:04:05 mymachine kernel: [89002.791744] ata4: EH complete
Nov 17 05:04:10 mymachine kernel: [89007.490174] ata4: soft resetting link
Nov 17 05:04:10 mymachine kernel: [89007.710467] ata4.00: configured for UDMA/133
Nov 17 05:04:10 mymachine kernel: [89007.710489] ata4: EH complete

[besson3c (joe-netmusician)]

I think the noapic is actually a viable workaround for me. The two freezes I mentioned above seem unrelated, due to low memory conditions while running VMs. For now it looks like the noapic command has stabilized my ethernet.

[Jack Nihil (jnihil)]

I went back to 9.04 and loaded all updates. No further problems for a week. Even passed the ftp/smb tests that previously failed with consistantly 9.10.

I will stay with 9.04 until this problem is repaired.

[besson3c (joe-netmusician)]

So far I haven't been able to reproduce this problem with the new kernel version that I just installed via apt-get (w/o noapic in the kernel boot) FWIW...

[besson3c (joe-netmusician)]

Nope, this problem still persists with 2.6.31-15-generic

[besson3c (joe-netmusician)]

I spoke prematurely... noapic seems to change the symptoms, but the problem is still very apparent. Reproducing this is a little tricky, it seems to happen randomly, but there are times where it will crap out within seconds of starting some sort of download. It seems that heavy downloads trigger this moreso than just SSH or even rsync connections.

This is a *very* nasty bug, it seems that when this happens there is no choice but to reboot. Please let me know if there is anything I can do to help, it's no fun having to reboot into the older kernel when I want to download something :)

[Jack Nihil (jnihil)]

2.6.28-16-generic (9.04) has been stable for over 2 weeks.
I wonder which kernel version broke the VIA-Rhine support?

[cd311 (cd311)]

hi

same problem here with a
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)

computer is runing fine until i get the following in kern.log
Dec 8 13:01:33 gwa194l kernel: [86311.000031] ------------[ cut here ]------------
Dec 8 13:01:33 gwa194l kernel: [86311.000048] WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog+0x1f6/0x210()
Dec 8 13:01:33 gwa194l kernel: [86311.000054] Hardware name: System Product Name
Dec 8 13:01:33 gwa194l kernel: [86311.000058] NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Dec 8 13:01:33 gwa194l kernel: [86311.000062] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat usb_storage snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd iptable_filter soundcore lp psmouse serio_raw snd_page_alloc i2c_viapro ip_tables x_tables asus_atk0110 shpchp ppdev parport_pc k8temp parport dm_raid45 xor radeon ttm usbhid drm i2c_algo_bit floppy sata_via via_rhine mii amd64_agp agpgart
Dec 8 13:01:33 gwa194l kernel: [86311.000130] Pid: 0, comm: swapper Not tainted 2.6.31-15-generic #50-Ubuntu
Dec 8 13:01:33 gwa194l kernel: [86311.000135] Call Trace:
Dec 8 13:01:33 gwa194l kernel: [86311.000147] [<c014518d>] warn_slowpath_common+0x6d/0xa0
Dec 8 13:01:33 gwa194l kernel: [86311.000154] [<c04b0dd6>] ? dev_watchdog+0x1f6/0x210
Dec 8 13:01:33 gwa194l kernel: [86311.000160] [<c04b0dd6>] ? dev_watchdog+0x1f6/0x210
Dec 8 13:01:33 gwa194l kernel: [86311.000168] [<c0145206>] warn_slowpath_fmt+0x26/0x30
Dec 8 13:01:33 gwa194l kernel: [86311.000174] [<c04b0dd6>] dev_watchdog+0x1f6/0x210
Dec 8 13:01:33 gwa194l kernel: [86311.000183] [<c0127c38>] ? default_spin_lock_flags+0x8/0x10
Dec 8 13:01:33 gwa194l kernel: [86311.000191] [<c0570dca>] ? _spin_lock_irqsave+0x2a/0x40
Dec 8 13:01:33 gwa194l kernel: [86311.000200] [<c030765b>] ? blk_rq_timed_out_timer+0x10b/0x120
Dec 8 13:01:33 gwa194l kernel: [86311.000207] [<c01501b7>] run_timer_softirq+0x117/0x200
Dec 8 13:01:33 gwa194l kernel: [86311.000216] [<c01699f4>] ? tick_handle_oneshot_broadcast+0x124/0x130
Dec 8 13:01:33 gwa194l kernel: [86311.000223] [<c04b0be0>] ? dev_watchdog+0x0/0x210
Dec 8 13:01:33 gwa194l kernel: [86311.000230] [<c014b3b0>] __do_softirq+0x90/0x1a0
Dec 8 13:01:33 gwa194l kernel: [86311.000239] [<c018f8fc>] ? handle_IRQ_event+0x4c/0x140
Dec 8 13:01:33 gwa194l kernel: [86311.000246] [<c01925a4>] ? move_native_irq+0x14/0x50
Dec 8 13:01:33 gwa194l kernel: [86311.000253] [<c014b4fd>] do_softirq+0x3d/0x40
Dec 8 13:01:33 gwa194l kernel: [86311.000260] [<c014b63d>] irq_exit+0x5d/0x70
Dec 8 13:01:33 gwa194l kernel: [86311.000267] [<c0104f10>] do_IRQ+0x50/0xc0
Dec 8 13:01:33 gwa194l kernel: [86311.000273] [<c01039b0>] common_interrupt+0x30/0x40
Dec 8 13:01:33 gwa194l kernel: [86311.000281] [<c0369fc4>] ? acpi_idle_enter_simple+0xff/0x130
Dec 8 13:01:33 gwa194l kernel: [86311.000291] [<c04688c6>] cpuidle_idle_call+0x76/0xd0
Dec 8 13:01:33 gwa194l kernel: [86311.000297] [<c010202c>] cpu_idle+0x8c/0xd0
Dec 8 13:01:33 gwa19...

[besson3c (joe-netmusician)]

This problem also persists with 2.6.31-16.

[Jack Nihil (jnihil)]

Did some googling around and it seems Ubuntu is the only distro having this issue.
Rather tempted to throw in an old HDD into the Shuttle and try testing a new Fedora or openSUSE...

[besson3c (joe-netmusician)]

Okay, this is really interesting... I reproduced this error in 2.6.28 just now. The best way to do this is by downloading or rsyncing some large files so that there is a lot of heavy I/O (or at least, so it seems, this may not be relevant at all).

Is this Watchdog thing a component of Ubuntu 9.10 that affects 9.10 no matter which kernel it is booted into?

[besson3c (joe-netmusician)]

Dec 25 02:26:53 epistaxis kernel: [ 1021.816031] ------------[ cut here ]------------
Dec 25 02:26:53 epistaxis kernel: [ 1021.816038] WARNING: at /build/buildd/linux-2.6.28/net/sched/sch_generic.c:226 dev_\
watchdog+0x270/0x280()
Dec 25 02:26:53 epistaxis kernel: [ 1021.816043] NETDEV WATCHDOG: eth0 (via-rhine): transmit timed out
Dec 25 02:26:53 epistaxis kernel: [ 1021.816046] Modules linked in: binfmt_misc vboxnetflt vboxnetadp vboxdrv lirc_seria\
l cx8800 cx88xx videobuf_dvb dvb_core bttv ir_common videobuf_dma_sg videobuf_core btcx_risc lirc_i2c lirc_dev snd_usb_a\
udio tuner_simple tuner_types snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_usb_lib snd_hwdep snd_seq_dummy msp34\
00 snd_seq_oss snd_seq_midi snd_rawmidi saa7115 snd_seq_midi_event tuner k8temp snd_seq usblp nvidia(P) i2c_viapro shpch\
p snd_timer snd_seq_device ivtv compat_ioctl32 i2c_algo_bit cx2341x v4l2_common videodev v4l1_compat tveeprom ppdev ipta\
ble_filter parport_pc snd soundcore ip_tables x_tables lp parport usbhid via_rhine mii ohci1394 ieee1394 floppy
Dec 25 02:26:53 epistaxis kernel: [ 1021.816128] Pid: 0, comm: swapper Tainted: P 2.6.28-16-generic #55-Ubuntu
Dec 25 02:26:53 epistaxis kernel: [ 1021.816132] Call Trace:
Dec 25 02:26:53 epistaxis kernel: [ 1021.816136] <IRQ> [<ffffffff80250ae7>] warn_slowpath+0xb7/0xf0
Dec 25 02:26:53 epistaxis kernel: [ 1021.816152] [<ffffffff80417b7a>] ? __next_cpu+0x1a/0x30
Dec 25 02:26:53 epistaxis kernel: [ 1021.816158] [<ffffffff80417b7a>] ? __next_cpu+0x1a/0x30
Dec 25 02:26:53 epistaxis kernel: [ 1021.816166] [<ffffffff80242502>] ? enqueue_entity+0x122/0x2b0
Dec 25 02:26:53 epistaxis kernel: [ 1021.816173] [<ffffffff8024881d>] ? enqueue_task_fair+0x3d/0x80
Dec 25 02:26:53 epistaxis kernel: [ 1021.816185] [<ffffffff8024a6fd>] ? default_wake_function+0xd/0x10
Dec 25 02:26:53 epistaxis kernel: [ 1021.816193] [<ffffffff80268b01>] ? autoremove_wake_function+0x11/0x40
Dec 25 02:26:53 epistaxis kernel: [ 1021.816200] [<ffffffff80270bc9>] ? getnstimeofday+0x59/0xe0
Dec 25 02:26:53 epistaxis kernel: [ 1021.816207] [<ffffffff8041de6a>] ? strlcpy+0x4a/0x60
Dec 25 02:26:53 epistaxis kernel: [ 1021.816214] [<ffffffff805c85d0>] dev_watchdog+0x270/0x280
Dec 25 02:26:53 epistaxis kernel: [ 1021.816220] [<ffffffff8026e89c>] ? sched_clock_cpu+0xcc/0x160
Dec 25 02:26:53 epistaxis kernel: [ 1021.816226] [<ffffffff80264dec>] ? __queue_work+0x3c/0x50
Dec 25 02:26:53 epistaxis kernel: [ 1021.816232] [<ffffffff805c8360>] ? dev_watchdog+0x0/0x280
Dec 25 02:26:53 epistaxis kernel: [ 1021.816240] [<ffffffff8025bfe9>] run_timer_softirq+0x179/0x260
Dec 25 02:26:53 epistaxis kernel: [ 1021.816247] [<ffffffff802739bf>] ? clockevents_program_event+0x4f/0x90
Dec 25 02:26:53 epistaxis kernel: [ 1021.816253] [<ffffffff80256c4c>] __do_softirq+0x9c/0x170
Dec 25 02:26:53 epistaxis kernel: [ 1021.816260] [<ffffffff80213d8c>] call_softirq+0x1c/0x30
Dec 25 02:26:53 epistaxis kernel: [ 1021.816266] [<ffffffff80214ffd>] do_softirq+0x5d/0xa0
Dec 25 02:26:53 epistaxis kernel: [ 1021.816271] [<ffffffff802569cd>] irq_exit+0x8d/0xa0
Dec 25 02:26:53 epistaxis kernel: [ 1021.816279] [<ffffffff80227648>] smp_apic_timer_interrupt+0x88/...

[Jack Nihil (jnihil)]

That's interesting, because I've been running 9.04 with 2.6.28-16 for weeks now without this issue.

[besson3c (joe-netmusician)]

Yeah, I never once had this problem under 2.6.28 in 9.04 either. I guess this is a combination of 9.10 and any kernel?

The only possible explanation to this is whether any kernel modules might be causing this problem? I'm a little unclear as to how it is that you can select an older kernel module via the standard Grub menu without having to rebuild the modules necessary for the selected kernel. If kernel modules are completely irrelevant here, I guess this is irrelevant?

[Jack Nihil (jnihil)]

This isn't an isolated issue with Ubuntu 9.10. I just tested using a Fedora 12 Live CD, transferring 3x 8GB files simultaneously to a Windows XP share and after about 15 minutes, the same problem occurred.

The kernel for Fedora 12 is 2.6.31.5-127.fc12.i686.

So the good news is that this isn't happening just on Ubuntu. Below is the familiar stack trace from the failure on Fedora 12, running on the same Shuttle SK22V10.

Do we need to take this up with kernel.org?

------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:246 dev_watchdog+0xc6/0x12d() (Not tainted)
Hardware name: SK22V10
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Modules linked in: fuse ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 cpufreq_ondemand powernow_k8 dm_multipath uinput snd_via82xx gameport snd_ac97_codec ac97_bus snd_seq snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device firewire_ohci snd i2c_viapro firewire_core via_rhine mii k8temp soundcore crc_itu_t squashfs nls_utf8 ata_generic pata_acpi sata_via pata_via nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
Pid: 0, comm: swapper Not tainted 2.6.31.5-127.fc12.i686 #1
Call Trace:
 [<c0436d93>] warn_slowpath_common+0x70/0x87
 [<c06ee200>] ? dev_watchdog+0xc6/0x12d
 [<c0436de8>] warn_slowpath_fmt+0x29/0x2c
 [<c06ee200>] dev_watchdog+0xc6/0x12d
 [<c043fffc>] ? __mod_timer+0xd4/0xde
 [<c044004d>] ? mod_timer+0x20/0x27
 [<c06e554f>] ? neigh_periodic_timer+0x128/0x139
 [<c06ee13a>] ? dev_watchdog+0x0/0x12d
 [<c043fd21>] run_timer_softirq+0x14e/0x1af
 [<c043c042>] __do_softirq+0xb1/0x157
 [<c043c11e>] do_softirq+0x36/0x41
 [<c043c210>] irq_exit+0x2e/0x61
 [<c04173ab>] smp_apic_timer_interrupt+0x6d/0x7b
 [<c0403f95>] apic_timer_interrupt+0x31/0x38
 [<c041eba4>] ? native_safe_halt+0xa/0xc
 [<c0409596>] default_idle+0x45/0x6d
 [<c040969f>] c1e_idle+0xe1/0xe6
 [<c04026ff>] cpu_idle+0x96/0xaf
 [<c0753f98>] rest_init+0x58/0x5a
 [<c09898b2>] start_kernel+0x32b/0x330
 [<c0989070>] i386_start_kernel+0x70/0x77
---[ end trace a4e9777c5486a919 ]---
eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
via-rhine: Reset not complete yet. Trying harder.
eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1

[besson3c (joe-netmusician)]

If you point me at the bug thread I'll be happy to track it and provide whatever info is useful. I'm anxious to see this fixed, this is particularly annoying, and I would imagine that if it is at all widespread that it would be a nice one to have fixed.

Any theories as to why I was able to reproduce this with the 2.6.28 kernel, but never so when I ran Ubuntu 9.04? What is the watchdog/rhine thing anyway, is it some sort of kernel module?

[Jack Nihil (jnihil)]

Found this: http://bugzilla.kernel.org/show_bug.cgi?id=11663

[Jack Nihil (jnihil)]

I think the watchdog kicked-in because the via-rhine driver did not respond to a command (I think I read somewhere that it waits 10ms). So, assuming that the Ethernet controller has hung, the system attempts to reset the VT6102 chip, but looking at the log that isn't successful either, it just repeats the process forever.

I'm tempted to install an Intel Pro 1000 card I have hanging around until someone takes notice of this problem. Like you say, it's very troublesome.

[besson3c (joe-netmusician)]

I have an Intel Pro 1000, but I need both PCI slots for another cards, so... I'll add a link in that thread you posted above to this one just to sort of ping those guys on this.

Do you know of other PC vendors that use the VT chipsets for their ethernet controllers? Have you looked into whether this affects particular VT chipsets, as opposed to just ours? For the record, I have the VT6102 too:

VT6102 [Rhine-II] (rev 78)

Is anybody here experiencing this on a different controller? I'm not sure if this is controller specific, but this seems to be an interesting lead...

[Jack Nihil (jnihil)]

I hope this is related: http://patchwork.kernel.org/patch/69308/
Would love to see this fixed by the next Ubuntu LTS release.

[Thomas (menardorama)]

Hi

Has anyone tried with the latest kernel 2.6.32.2 ?

[JoSchu (joachim-schuth)]

Hello,
after I updated from Kubuntu 9.04 to 9.10 I have exactly the same issue with the ethernet controller.
The motherboard is a MSI K9VGMV with the VT6102 [Rhine-II] (rev 7c).

Yesterday I installed the newest updates and the kernel is now 2.6.31-16, but the situation is the same than before. When I try to copy some ISO-image via network after 10-15 minutes the network controller stops working and the logs say "WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog+0x1f6/0x210() ..."

I'm using Kubuntu since Version 7.10 and had never this situation. I hope there'll be a update for 9.10 soon!

[Jack Nihil (jnihil)]

I don't see any relevant changes in the 2.6.32.x changelogs so I don't think it's worthwhile going through testing 2.6.32.2.

[Thomas (menardorama)]

Yes you were right it changes nothing....

[Jack Nihil (jnihil)]

No mention of a driver fix for via-rhine in the 2.6.33 changelogs either. I think I'm gonna have to go ahead and install the Intel card since I don't want to stay with 9.04 for much longer. I'll let you guys know if changing the card helps the Shuttle or not.

[Balazs Oveges (ovegesb)]

I believe this bug affects me as well. My network adapter ceases to work after some time, restarting the network services doesn't help. I tried disabling ACPI, but it resulted in sound issues.

Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000211] [<c0150107>] run_timer_softirq+0x117/0x200
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000221] [<c016a025>] ? tick_dev_program_event+0x45/0xe0
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000227] [<c04b0ab0>] ? dev_watchdog+0x0/0x210
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000236] [<c014b300>] __do_softirq+0x90/0x1a0
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000245] [<c015fe53>] ? hrtimer_interrupt+0x183/0x210
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000252] [<c014b44d>] do_softirq+0x3d/0x40
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000259] [<c014b58d>] irq_exit+0x5d/0x70
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000270] [<c011dc77>] smp_apic_timer_interrupt+0x57/0x90
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000278] [<c0103d71>] apic_timer_interrupt+0x31/0x40
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000286] [<c0126f45>] ? native_safe_halt+0x5/0x10
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000293] [<c010a486>] default_idle+0x46/0xd0
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000299] [<c010a55d>] c1e_idle+0x4d/0x100
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000306] [<c010202c>] cpu_idle+0x8c/0xd0
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000315] [<c055eda5>] rest_init+0x55/0x60
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000326] [<c078e8cd>] start_kernel+0x2e6/0x2ec
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000334] [<c078e406>] ? unknown_bootoption+0x0/0x1ab
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000347] [<c078e07c>] i386_start_kernel+0x7c/0x83
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000352] ---[ end trace 51f78f0eb97cb0b3 ]---
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000538] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.001232] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Jan 10 22:40:29 oveges-desktop kernel: [ 6713.000185] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
Jan 10 22:40:29 oveges-desktop kernel: [ 6713.000870] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Jan 10 22:40:33 oveges-desktop kernel: [ 6717.000173] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
Jan 10 22:40:33 oveges-desktop kernel: [ 6717.000886] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Jan 10 22:40:37 oveges-desktop kernel: [ 6721.000195] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
Jan 10 22:40:37 oveges-desktop kernel: [ 6721.000903] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

[Jack Nihil (jnihil)]

I've been running for about 3 weeks with a Realtek RTL-8169 PCI card (turns out that the Intel card I mentioned earlier was PCI-e and I was already using that slot) with no problems with large file transfers.

I also would like to mention that Ubuntu 9.04 with no kernel updates will also display this problem, though much more infrequent than later kernel versions. In other words, all kernel versions out there are affected by this bug. Disabling the onboard LAN on the Shuttle and adding an Ethernet card looks to be a workaround.

I found this in the 2.6.33-rc3 changelog:
(http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.33-rc3)

    net/via-rhine: Fix scheduling while atomic bugs

    There are BUGs "scheduling while atomic" triggered by the timer
    rhine_tx_timeout(). They are caused by calling napi_disable() (with
    msleep()). This patch fixes it by moving most of the timer content to
    the workqueue function (similarly to other drivers, like tg3), with
    spin_lock() changed to BH version.

    Additionally, there is spin_lock_irq() moved in rhine_close() to
    exclude napi_disable() etc., also tg3's way.

I hope this is related and gets merged into Ubuntu 10.4.

[markofealing (mark-ferns16)]

Running Kubuntu 9.10 with latest updates, same problem here on a ASUS A8V-XE, running same VT6102 Rhine II controller. Under heavy network load (file copying it crashes out. Adding acpi=off in Grub makes the PC really slow (Athlon 64 x2 4200) and ther is not networking hat so ever!

Changing ACPI Support in BIOS (can't disable on this M/B) to S1 rather than S1 & S3 may help. Testing....

[markofealing (mark-ferns16)]

The S1 didn't work, network dropped out AGAIN and got: :

Kubuntu64 kernel [ 7321.040164] eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
Kubuntu64 kernel [ 7321.040334] via-rhine: Reset not complete yet. Trying harder.
Kubuntu64 kernel [ 7321.040912] eth1: link up, 100Mbps, half-duplex, lpa 0x40A1

Now trying S3 only (after reboot).

Googling the problem it appears that this has been happening since 2002 across most distros, must be one of the oldest Linux bugs out there!

[markofealing (mark-ferns16)]

S3 dropped out quicker than I expected, same old problem.

Disabled on-board LAN, stuck in a old 3COM 3C905B PCI NIC. Can't disable ACPI still in the BIOS.

[markofealing (mark-ferns16)]

Disabling the on-board Via-Rhine NIC and using the 3COM 3C905B PCI NIC has resolved the problem. No timeouts and solid performance. Disabling ACPI in the BIOS seems to be a red herring.

Therefore, to me suggests a driver bug which needs an urgent fix especially as this chip-set is quite common.

I'm running Kubuntu 9.10, kernel 2.6.31-17.

[Jack Nihil (jnihil)]

Looks as though Lucid is going to be based on kernel 2.6.32, in which case the above mentioned (#34) bug fix will not be included. Guess the onboard LAN will remain disabled for a lot longer than I had hoped.

[Balazs Oveges (ovegesb)]

Ubuntu kernel 2.6.33 rc8 is already released, so I guess we will soon see a stable 2.6.33.

You can install the latest kernel via .deb files from the Ubuntu PPA:
http://kernel.ubuntu.com/~kernel-ppa/mainline/

I'm currently writing from 2.6.33 rc7. It lacks Radeon support in my setup, so Firefox lags when scrolling. I couldn't test it for a long while yet, but I hope the via rhine bug is really solved.

[Balazs Oveges (ovegesb)]

Stable Linux kernel 2.6.33 was released yesterday. Will try it soon hopefully.

So far, I had no network issue with rc8, but my tests were not very extensive. Still, 4 hours of continous torrent dowload is something I couldn't manage before.

[Jeremy Foshee (jeremyfoshee)]

Hi <email address hidden>,

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 (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 454747

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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[besson3c (joe-netmusician)]

I'm still experiencing this problem and would very much like this fixed, and am assuming that this command can be run at any time, and not just after the crash? It obviously won't work without network connectivity...

I'll add this report to this report and will start testing the newer kernel versions starting with .33.

Thanks!

[besson3c (joe-netmusician)]

AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SoundSticks [SoundSticks], device 0: USB Audio [USB Audio]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices: **** List of CAPTURE Hardware Devices ****
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: epistaxis 1945 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SoundSticks'/'harman/kardon SoundSticks at usb-0000:00:10.3-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB05fc:7849'
   Controls : 6
   Simple ctrls : 5
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=7d80f60e-2f76-4a55-b724-22d627150fd4
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Shuttle Inc SK22V10
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: root=UUID=e52ba8d8-de50-40c6-9c1c-104739dd30dc ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-20-generic N/A
 linux-firmware 1.26
RfKill:

Uname: Linux 2.6.31-20-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare
WpaSupplicantLog:

XsessionErrors:
 (gnome-settings-daemon:2396): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2814): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2718): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 07/10/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: FX22V10
dmi.board.vendor: Shuttle Inc
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/10/2007:svnShuttleInc:pnSK22V10:pvr:rvnShuttleInc:rnFX22V10:rvr:cvn:ct3:cvr:
dmi.product.name: SK22V10
dmi.sys.vendor: Shuttle Inc

[besson3c (joe-netmusician)]

I haven't spent a whole lot of time in .33 yet, but after upgrading to Ubuntu 10.04 and kernel 2.6.32-21-generic I'm still having this problem, so no love for me.

If there is anyway to get sound and 3D Nvidia video working in the .33 kernels please let me know (if you know off the top of your head, I know this is off topic) and I will test the .33 kernels full time.

[besson3c (joe-netmusician)]

Unfortunately I'm still able to reproduce this problem in 2.6.33. However, when my ethernet interface crapped out nothing was logged to /var/log/messages. Doing an ifdown and then ifup did not restore the interface, it was unable to get a lease from the DHCP server (all other machines on the network were fine). So, same end result, although I don't have the evidence to suggest that the symptoms are the same....

[besson3c (joe-netmusician)]

Sorry, 2.6.33-02063303-generic to be exact...

[Balazs Oveges (ovegesb)]

I use Ubuntu 9.04 most of the time, which is not affected by this bug. I experienced the same bug on 10.04 on the rare occasions I tried to use it. I use the 2.6.33-02063303-generic kernel as well.

[Oleg Yaroshevych (brainunit)]

Same problem with Ubuntu Desktop x64 (kernel 2.6.32-23). Drops connection every hour or so.

Asus UL30A

[Jack Nihil (jnihil)]

On Lucid, they've broken my workaround, RTL-8169, so now I have NO OPTIONS
but to go back to 9.10 and use the RTL-8169 since the VIA is still utterly
broken with all versions.

Someone please fix this damn bug...

[besson3c (joe-netmusician)]

Do we know for absolute certain that 9.04 was not affected by this bug? I don't remember having it when I used 9.04, but it seems weird that it has been reproduced in other Linux OSes, the latest 2.6.33 kernels, other versions of Ubuntu, but not 9.04. The symptoms where different, but I even had some Ethernet related problems testing ESXi on this same machine...

If this was a general Linux kernel problem, what was so special about Ubuntu 9.04 that exempted it from this problem?

[Balazs Oveges (ovegesb)]

I'm back on Ubuntu 9.04 without any issue since months.

[Jack Nihil (jnihil)]

9.04 also has the same issue, just more infrequent than other versions.
I feel that the VIA chipset support in the kernel isn't up to scratch.
Hate to say this, but it's probably time to move to an Intel platform and be
rid of this long-lasting headache.

On Mon, Jul 5, 2010 at 2:55 AM, besson3c <email address hidden> wrote:

> Do we know for absolute certain that 9.04 was not affected by this bug?
> I don't remember having it when I used 9.04, but it seems weird that it
> has been reproduced in other Linux OSes, the latest 2.6.33 kernels,
> other versions of Ubuntu, but not 9.04. The symptoms where different,
> but I even had some Ethernet related problems testing ESXi on this same
> machine...
>
> If this was a general Linux kernel problem, what was so special about
> Ubuntu 9.04 that exempted it from this problem?
>
> --
> NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
> https://bugs.launchpad.net/bugs/454747
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Balazs Oveges (ovegesb)]

I'm using kernel 2.6.28-11-generic on Ubuntu 9.04 everytime. I don't experience any issues. Which kernel version did you use on Jaunty?

[Jack Nihil (jnihil)]

You have to create a fair amount of traffic with 9.04. Bittorrent alone will not cause the problem. Try FTPing a couple of DVD ISOs from a local node on the LAN simultaneously and see what happens.

[besson3c (joe-netmusician)]

Anybody try to reproduce this under kernel 2.6.35? I'll give this a go once the release kernel is available in Ubuntu mainline for Lucid.

[Rudi Daemen (fludizz)]

Hmm, I have the same issue, however I do not have the option of adding additional LAN cards. However the bug is not 'fatal' for my server (Ubuntu 10.04LTS), it recovers without issues after the nic reset occurs. Can't even detect packet loss when it happens! I did notice this bug happening to the idle interface as well (the system has two onboard Via Rhine interfaces (Via LT15000AG)) and seems to be unrelated to network load as my server hardly has any. By the way this bug seems to have been present since at least 8.04LTS (2.6.24) and even before that on Debian Etch (2.6.20), I also had the same issue on their kernels.

Bit strange that this bug (Which I can trace back to about 2002 using google) still has not been fixed...

[Jack Nihil (jnihil)]

I'm so tired of chasing bugs on this VIA board that I think I'll be
switching to a purely Intel board.
No one takes any notice when we add information to this bug, so I'm moving
on.
Good luck, guys.

[Stefan Becker (zorak1103)]

Since I upgraded to Lucid 2 days ago I'm struck by this error, too. Never had any problems with karmic, though.
Symptoms are the same: Network gets unresponsive under heavy load.

Aug 29 16:42:50 COMPAKT kernel: [ 404.000051] ------------[ cut here ]------------
Aug 29 16:42:50 COMPAKT kernel: [ 404.000078] WARNING: at /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 dev_watchdog+0x1fe/0x210()
Aug 29 16:42:50 COMPAKT kernel: [ 404.000087] Hardware name: Evo N620c (DC824AV)
Aug 29 16:42:50 COMPAKT kernel: [ 404.000095] NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out
Aug 29 16:42:50 COMPAKT kernel: [ 404.000102] Modules linked in: binfmt_misc ppdev nfsd exportfs snd_intel8x0 nfs lockd snd_ac97_codec ac97_bus nfs_acl fbcon tileblit font snd_pcm_oss bitblit softcursor snd_mixer_oss snd_pcm auth_rpcgss vga16fb snd_seq_dummy sunrpc snd_seq_oss vgastate snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device joydev snd radeon soundcore ttm drm_kms_helper pcmcia snd_page_alloc drm i2c_algo_bit yenta_socket rsrc_nonstatic pcmcia_core psmouse video serio_raw intel_agp agpgart shpchp output usbhid hid lp parport tg3
Aug 29 16:42:50 COMPAKT kernel: [ 404.000239] Pid: 0, comm: swapper Not tainted 2.6.32-24-generic #41-Ubuntu
Aug 29 16:42:50 COMPAKT kernel: [ 404.000247] Call Trace:
Aug 29 16:42:50 COMPAKT kernel: [ 404.000263] [<c014c4a2>] warn_slowpath_common+0x72/0xa0
Aug 29 16:42:50 COMPAKT kernel: [ 404.000276] [<c04d996e>] ? dev_watchdog+0x1fe/0x210
Aug 29 16:42:50 COMPAKT kernel: [ 404.000286] [<c04d996e>] ? dev_watchdog+0x1fe/0x210
Aug 29 16:42:50 COMPAKT kernel: [ 404.000298] [<c014c51b>] warn_slowpath_fmt+0x2b/0x30
Aug 29 16:42:50 COMPAKT kernel: [ 404.000309] [<c04d996e>] dev_watchdog+0x1fe/0x210
Aug 29 16:42:50 COMPAKT kernel: [ 404.000325] [<c0163a50>] ? insert_work+0x60/0xb0
Aug 29 16:42:50 COMPAKT kernel: [ 404.000340] [<c012a498>] ? default_spin_lock_flags+0x8/0x10
Aug 29 16:42:50 COMPAKT kernel: [ 404.000353] [<c058cdcf>] ? _spin_lock_irqsave+0x2f/0x50
Aug 29 16:42:50 COMPAKT kernel: [ 404.000365] [<c0163d16>] ? __queue_work+0x36/0x50
Aug 29 16:42:50 COMPAKT kernel: [ 404.000376] [<c015b70e>] run_timer_softirq+0x13e/0x2c0
Aug 29 16:42:50 COMPAKT kernel: [ 404.000388] [<c04d9770>] ? dev_watchdog+0x0/0x210
Aug 29 16:42:50 COMPAKT kernel: [ 404.000400] [<c0153138>] __do_softirq+0x98/0x1b0
Aug 29 16:42:50 COMPAKT kernel: [ 404.000411] [<c012a498>] ? default_spin_lock_flags+0x8/0x10
Aug 29 16:42:50 COMPAKT kernel: [ 404.000423] [<c058cdcf>] ? _spin_lock_irqsave+0x2f/0x50
Aug 29 16:42:50 COMPAKT kernel: [ 404.000437] [<c0106c87>] ? enable_8259A_irq+0x47/0x70
Aug 29 16:42:50 COMPAKT kernel: [ 404.000448] [<c0153295>] do_softirq+0x45/0x50
Aug 29 16:42:50 COMPAKT kernel: [ 404.000458] [<c01533e5>] irq_exit+0x65/0x70
Aug 29 16:42:50 COMPAKT kernel: [ 404.000469] [<c0591245>] do_IRQ+0x55/0xc0
Aug 29 16:42:50 COMPAKT kernel: [ 404.000481] [<c016d5c5>] ? sched_clock_local+0xa5/0x180
Aug 29 16:42:50 COMPAKT kernel: [ 404.000493] [<c0103a30>] common_interrupt+0x30/0x40
Aug 29 16:42:50 COMPAKT kernel: [ 404.000504] [<c016007b>] ? sys_getrusage+0x2b/0x30
Aug 2...

[Balazs Oveges (ovegesb)]

I made a clean install of Lucid. I can live with this bug, my network load became less for the last months. Still, recently under 2.26.32-24 it became more frequent, so I use 2.26.32-23 daily. I haven't tried 2.6.35 yet, I had fglrx issues with the Ubuntu PPA latest stable kernel last time.

I guess Rudi Daemen has got another problem. In my case the network becomes unresponsive, and only a total reset will work. If a nic reset works, what command do you use?

[Rudi Daemen (fludizz)]

I don't manually reset the device. This is done automatically, after the reset it renegotiaties the NIC speed too 100 full duplex and resumes operation. It might be that I also experience loss but my network load is so low it isn't noticeable.

I've bypassed the problem as well now by removing the RAID card I had to free the only PCI slot in the machine and placed a Intel dualport GBit nic. Then I proceded to blacklist the via_rhine module (for some reason the BIOS does not allow me to hard-disable the two onboard nics) and I have had no more issues since then. I will keep my subscription to this bug open because I might start testing multicasting and vlan's and intend to use seperate nics for seperate purposes.

I do believe I'm affected by the same bug (Same sequence of events followed by a hard reset and the netdev watchdog dump in the logs) but perhaps due to configuration differences (or even different firmware/build revisions of the NIC) it was not fatal in my system.

[besson3c (joe-netmusician)]

I've been trying to work around this problem for quite some time now, and it seems that doing stuff like adding a bwlimit=200 to my rsync script consistently keeps the machine on the network for months now.

There does seem to be something about heavy network traffic that is relevant here.

[lpuser (lpuser)]

It seems that this bug also affects Ubuntu 10.10.

$ uname -a
Linux ubuntu 2.6.35-22-generic #34-Ubuntu SMP Sun Oct 10 09:24:00 UTC 2010 i686 GNU/Linux

This is the output from /var/log/messages :

Oct 14 18:07:14 ubuntu kernel: [ 77.054544] lo: Disabled Privacy Extensions
Oct 14 18:13:49 ubuntu kernel: [ 471.919115] lo: Disabled Privacy Extensions
Oct 14 18:19:40 ubuntu kernel: [ 823.004036] ------------[ cut here ]------------
Oct 14 18:19:40 ubuntu kernel: [ 823.004058] WARNING: at /build/buildd/linux-2.6.35/net/sched/sch_generic.c:258 dev_watchdog+0x1fd/0x210()
Oct 14 18:19:40 ubuntu kernel: [ 823.004063] Hardware name: KT600-8237
Oct 14 18:19:40 ubuntu kernel: [ 823.004065] NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Oct 14 18:19:40 ubuntu kernel: [ 823.004068] Modules linked in: binfmt_misc snd_via82xx gameport snd_ac97_codec radeon ac97_bus xfs snd_pcm snd_page_alloc snd_mpu401_uart snd_seq_midi snd_rawmidi ttm snd_seq_midi_event exportfs snd_seq drm_kms_helper snd_timer snd_seq_device uvcvideo ppdev drm snd videodev psmouse v4l1_compat via_agp i2c_viapro soundcore serio_raw i2c_algo_bit parport_pc shpchp agpgart lp parport via_rhine floppy pata_via sata_via mii
Oct 14 18:19:40 ubuntu kernel: [ 823.004116] Pid: 0, comm: swapper Not tainted 2.6.35-22-generic #34-Ubuntu
Oct 14 18:19:40 ubuntu kernel: [ 823.004119] Call Trace:
Oct 14 18:19:40 ubuntu kernel: [ 823.004134] [<c014ac52>] warn_slowpath_common+0x72/0xa0
Oct 14 18:19:40 ubuntu kernel: [ 823.004140] [<c050e61d>] ? dev_watchdog+0x1fd/0x210
Oct 14 18:19:40 ubuntu kernel: [ 823.004145] [<c050e61d>] ? dev_watchdog+0x1fd/0x210
Oct 14 18:19:40 ubuntu kernel: [ 823.004151] [<c014ad23>] warn_slowpath_fmt+0x33/0x40
Oct 14 18:19:40 ubuntu kernel: [ 823.004156] [<c050e61d>] dev_watchdog+0x1fd/0x210
Oct 14 18:19:40 ubuntu kernel: [ 823.004163] [<c017597e>] ? tick_program_event+0x2e/0x40
Oct 14 18:19:40 ubuntu kernel: [ 823.004169] [<c0169fde>] ? hrtimer_interrupt+0x1ae/0x2a0
Oct 14 18:19:40 ubuntu kernel: [ 823.004174] [<c050e420>] ? dev_watchdog+0x0/0x210
Oct 14 18:19:40 ubuntu kernel: [ 823.004180] [<c0157e1f>] call_timer_fn+0x2f/0xf0
Oct 14 18:19:40 ubuntu kernel: [ 823.004185] [<c0159064>] run_timer_softirq+0x104/0x210
Oct 14 18:19:40 ubuntu kernel: [ 823.004191] [<c017509c>] ? tick_handle_oneshot_broadcast+0x12c/0x140
Oct 14 18:19:40 ubuntu kernel: [ 823.004196] [<c050e420>] ? dev_watchdog+0x0/0x210
Oct 14 18:19:40 ubuntu kernel: [ 823.004204] [<c015127c>] __do_softirq+0x9c/0x1b0
Oct 14 18:19:40 ubuntu kernel: [ 823.004212] [<c01a7df4>] ? handle_IRQ_event+0x44/0x150
Oct 14 18:19:40 ubuntu kernel: [ 823.004217] [<c01a7f64>] ? irq_to_desc+0x14/0x20
Oct 14 18:19:40 ubuntu kernel: [ 823.004223] [<c01ab4e9>] ? move_native_irq+0x19/0x50
Oct 14 18:19:40 ubuntu kernel: [ 823.004228] [<c01513d5>] do_softirq+0x45/0x50
Oct 14 18:19:40 ubuntu kernel: [ 823.004233] [<c0151545>] irq_exit+0x65/0x70
Oct 14 18:19:40 ubuntu kernel: [ 823.004239] [<c05cf6d5>] do_IRQ+0x55/0xc0
Oct 14 18:19:40 ubuntu kernel: [ 823.004245] [<c016bf14>] ? sched_clock_local+0xa4/0x180
Oct 14 18:19:40 ubuntu kernel: [ 823.004251] [<c0103630>] common_interrupt...

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.