Comment 25 for bug 1269412

We noticed this problem starting today on one of our older servers. It deprived the device of its internet connection (obviously), only a reboot could fix it. Here's the trace:

Sep 15 18:10:14 cam kernel: [175306.808016] ------------[ cut here ]------------
Sep 15 18:10:14 cam kernel: [175306.808036] WARNING: CPU: 1 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280()
Sep 15 18:10:14 cam kernel: [175306.808045] NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Sep 15 18:10:14 cam kernel: [175306.808051] Modules linked in: nfsv3 autofs4 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt snd_hda_codec_realtek snd_hda_intel snd_hda_codec ppdev snd_hwdep snd_pcm kvm_amd snd_page_alloc kvm snd_timer snd soundcore edac_core serio_raw k8temp edac_mce_amd i2c_viapro shpchp parport_pc mac_hid zram(C) 8021q garp stp mrp llc lp parport raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 pata_acpi via_rhine mii floppy pata_via sata_via
Sep 15 18:10:14 cam kernel: [175306.808096] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G C 3.13.0-35-generic #62-Ubuntu
Sep 15 18:10:14 cam kernel: [175306.808098] Hardware name: MICRO-STAR INTERNATIONAL CO., LTD MS-7253/MS-7253, BIOS V1.4 06/27/2007
Sep 15 18:10:14 cam kernel: [175306.808105] 0000000000000009 ffff880077d03d98 ffffffff8171e320 ffff880077d03de0
Sep 15 18:10:14 cam kernel: [175306.808110] ffff880077d03dd0 ffffffff8106775d 0000000000000000 ffff8800363f8000
Sep 15 18:10:14 cam kernel: [175306.808113] ffff8800362b5a80 0000000000000001 0000000000000001 ffff880077d03e30
Sep 15 18:10:14 cam kernel: [175306.808120] Call Trace:
Sep 15 18:10:14 cam kernel: [175306.808122] <IRQ> [<ffffffff8171e320>] dump_stack+0x45/0x56
Sep 15 18:10:14 cam kernel: [175306.808144] [<ffffffff8106775d>] warn_slowpath_common+0x7d/0xa0
Sep 15 18:10:14 cam kernel: [175306.808151] [<ffffffff810677cc>] warn_slowpath_fmt+0x4c/0x50
Sep 15 18:10:14 cam kernel: [175306.808156] [<ffffffff81643156>] dev_watchdog+0x276/0x280
Sep 15 18:10:14 cam kernel: [175306.808159] [<ffffffff81642ee0>] ? dev_graft_qdisc+0x80/0x80
Sep 15 18:10:14 cam kernel: [175306.808163] [<ffffffff81074306>] call_timer_fn+0x36/0x100
Sep 15 18:10:14 cam kernel: [175306.808171] [<ffffffff81642ee0>] ? dev_graft_qdisc+0x80/0x80
Sep 15 18:10:14 cam kernel: [175306.808175] [<ffffffff8107529f>] run_timer_softirq+0x1ef/0x2f0
Sep 15 18:10:14 cam kernel: [175306.808179] [<ffffffff8106cbac>] __do_softirq+0xec/0x2c0
Sep 15 18:10:14 cam kernel: [175306.808187] [<ffffffff8106d0f5>] irq_exit+0x105/0x110
Sep 15 18:10:14 cam kernel: [175306.808192] [<ffffffff81731145>] smp_apic_timer_interrupt+0x45/0x60
Sep 15 18:10:14 cam kernel: [175306.808198] [<ffffffff8172fadd>] apic_timer_interrupt+0x6d/0x80
Sep 15 18:10:14 cam kernel: [175306.808200] <EOI> [<ffffffff8104f596>] ? native_safe_halt+0x6/0x10
Sep 15 18:10:14 cam kernel: [175306.808215] [<ffffffff8101c5ff>] default_idle+0x1f/0xc0
Sep 15 18:10:14 cam kernel: [175306.808222] [<ffffffff8101c6df>] amd_e400_idle+0x3f/0x110
Sep 15 18:10:14 cam kernel: [175306.808226] [<ffffffff8101cec6>] arch_cpu_idle+0x26/0x30
Sep 15 18:10:14 cam kernel: [175306.808233] [<ffffffff810bed85>] cpu_startup_entry+0xc5/0x290
Sep 15 18:10:14 cam kernel: [175306.808240] [<ffffffff81040fe8>] start_secondary+0x218/0x2c0
Sep 15 18:10:14 cam kernel: [175306.808246] ---[ end trace 847728b2d59a4148 ]---

Followed by the via-rhine module complaining:
Sep 15 18:10:14 cam kernel: [175306.808417] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:10:18 cam kernel: [175310.808184] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:10:18 cam kernel: [175310.808279] via-rhine 0000:00:12.0 eth0: Reset not complete yet. Trying harder.
Sep 15 18:10:22 cam kernel: [175314.808182] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:10:26 cam kernel: [175318.808185] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:10:30 cam kernel: [175322.808180] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:10:34 cam kernel: [175326.808184] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:10:40 cam kernel: [175332.808184] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:10:46 cam kernel: [175338.808184] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:10:52 cam kernel: [175344.808185] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
Sep 15 18:10:56 cam kernel: [175348.808182] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:11:00 cam kernel: [175352.808179] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:11:00 cam kernel: [175352.808317] via-rhine 0000:00:12.0 eth0: Reset not complete yet. Trying harder.
Sep 15 18:11:04 cam kernel: [175356.808185] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:11:04 cam kernel: [175356.808273] via-rhine 0000:00:12.0 eth0: Reset not complete yet. Trying harder.
Sep 15 18:11:08 cam kernel: [175360.808180] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Sep 15 18:11:12 cam kernel: [175364.808182] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 0003, PHY status 786d, resetting...

If any more information is needed we will gladly supply it