Bug#549606: VIA-Rhine II network interface lost connectivity

["Jens-Michael Hoffmann" <jensmh@gmx.de>]

Looks like the bug still is there in 2.6.32-13-amd64, however frequency is greatly reduced.
It today happened again after months. The system is an uptodate squeeze with only kernel from sid.

May 27 14:31:29 histor2 kernel: [724199.816021] ------------[ cut here ]------------
May 27 14:31:29 histor2 kernel: [724199.816061] WARNING: at /build/mattems-linux-2.6_2.6.32-13-amd64-ybUaaU/linux-2.6-2.6.32-13/debian/build/source_amd64_none/net/sched/sch_generic.c:261 dev_watchdog+0xe2/0x194()
May 27 14:31:29 histor2 kernel: [724199.816123] Hardware name: SK22V10
May 27 14:31:29 histor2 kernel: [724199.816143] NETDEV WATCHDOG: eth2 (via-rhine): transmit queue 0 timed out
May 27 14:31:29 histor2 kernel: [724199.816169] Modules linked in: iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables tcp_diag inet_diag ppdev lp parport cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc powernow_k8 loop snd_pcsp snd_pcm snd_timer snd i2c_viapro soundcore shpchp edac_core tpm_tis i2c_core edac_mce_amd evdev snd_page_alloc pci_hotplug k8temp tpm button processor tpm_bios ext3 jbd mbcache sha256_generic aes_x86_64 aes_generic cbc dm_crypt dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod sg sr_mod cdrom sd_mod crc_t10dif 8139too ata_generic uhci_hcd fan sata_via thermal thermal_sys 8139cp via_rhine mii ehci_hcd pata_via libata usbcore scsi_mod nls_base firewire_ohci firewire_core crc_itu_t [last unloaded: scsi_wait_scan]
May 27 14:31:29 histor2 kernel: [724199.816589] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1
May 27 14:31:29 histor2 kernel: [724199.816614] Call Trace:
May 27 14:31:29 histor2 kernel: [724199.816633]  <IRQ>  [<ffffffff81260bf6>] ? dev_watchdog+0xe2/0x194
May 27 14:31:29 histor2 kernel: [724199.816668]  [<ffffffff81260bf6>] ? dev_watchdog+0xe2/0x194
May 27 14:31:29 histor2 kernel: [724199.816696]  [<ffffffff8104dc58>] ? warn_slowpath_common+0x77/0xa3
May 27 14:31:29 histor2 kernel: [724199.816724]  [<ffffffff81260b14>] ? dev_watchdog+0x0/0x194
May 27 14:31:29 histor2 kernel: [724199.816750]  [<ffffffff8104dce0>] ? warn_slowpath_fmt+0x51/0x59
May 27 14:31:29 histor2 kernel: [724199.816779]  [<ffffffff8101f2b4>] ? mce_setup+0xb0/0xbe
May 27 14:31:29 histor2 kernel: [724199.816806]  [<ffffffff81260ae8>] ? netif_tx_lock+0x3d/0x69
May 27 14:31:29 histor2 kernel: [724199.816834]  [<ffffffff8124b9b8>] ? netdev_drivername+0x3b/0x40
May 27 14:31:29 histor2 kernel: [724199.816861]  [<ffffffff81260bf6>] ? dev_watchdog+0xe2/0x194
May 27 14:31:29 histor2 kernel: [724199.816888]  [<ffffffff8101fbcc>] ? mcheck_timer+0x0/0xf2
May 27 14:31:29 histor2 kernel: [724199.816917]  [<ffffffff8105a26b>] ? run_timer_softirq+0x1c9/0x268
May 27 14:31:29 histor2 kernel: [724199.816947]  [<ffffffff810539e6>] ? __do_softirq+0xdd/0x19f
May 27 14:31:29 histor2 kernel: [724199.816975]  [<ffffffff81024d62>] ? lapic_next_event+0x18/0x1d
May 27 14:31:29 histor2 kernel: [724199.817003]  [<ffffffff81011cac>] ? call_softirq+0x1c/0x30
May 27 14:31:29 histor2 kernel: [724199.817030]  [<ffffffff81013903>] ? do_softirq+0x3f/0x7c
May 27 14:31:29 histor2 kernel: [724199.817057]  [<ffffffff81053855>] ? irq_exit+0x36/0x76
May 27 14:31:29 histor2 kernel: [724199.817083]  [<ffffffff81025827>] ? smp_apic_timer_interrupt+0x87/0x95
May 27 14:31:29 histor2 kernel: [724199.821114]  [<ffffffff81011673>] ? apic_timer_interrupt+0x13/0x20
May 27 14:31:29 histor2 kernel: [724199.821139]  <EOI>  [<ffffffff8102c574>] ? native_safe_halt+0x2/0x3
May 27 14:31:29 histor2 kernel: [724199.821176]  [<ffffffff81017cc1>] ? default_idle+0x34/0x51
May 27 14:31:29 histor2 kernel: [724199.821203]  [<ffffffff8101804d>] ? c1e_idle+0xf5/0xfb
May 27 14:31:29 histor2 kernel: [724199.821231]  [<ffffffff8100feb1>] ? cpu_idle+0xa2/0xda
May 27 14:31:29 histor2 kernel: [724199.821260]  [<ffffffff814ec140>] ? early_idt_handler+0x0/0x71
May 27 14:31:29 histor2 kernel: [724199.821288]  [<ffffffff814eccd1>] ? start_kernel+0x3dc/0x3e8
May 27 14:31:29 histor2 kernel: [724199.821315]  [<ffffffff814ec3b7>] ? x86_64_start_kernel+0xf9/0x106
May 27 14:31:29 histor2 kernel: [724199.821341] ---[ end trace da285d2d0aca2156 ]---
May 27 14:31:29 histor2 kernel: [724199.821508] eth2: Transmit timed out, status 1003, PHY status 786d, resetting...
May 27 14:31:29 histor2 kernel: [724199.823146] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:31:41 histor2 kernel: [724211.816164] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:31:41 histor2 kernel: [724211.817112] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:31:51 histor2 kernel: [724221.816161] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:31:51 histor2 kernel: [724221.817088] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:32:01 histor2 kernel: [724231.816164] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:32:01 histor2 kernel: [724231.817100] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:32:17 histor2 kernel: [724247.816168] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:32:17 histor2 kernel: [724247.817118] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:32:27 histor2 kernel: [724257.816171] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:32:27 histor2 kernel: [724257.818631] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:32:39 histor2 kernel: [724269.816175] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:32:39 histor2 kernel: [724269.817120] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1
May 27 14:32:49 histor2 kernel: [724279.816167] eth2: Transmit timed out, status 0003, PHY status 786d, resetting...
May 27 14:32:49 histor2 kernel: [724279.817106] eth2: link up, 100Mbps, full-duplex, lpa 0x41E1


Kind regards,
Jens-Michael