kernel-packages team mailing list archive

[Bert Van de Poel <bert@xxxxxxxxx>]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269412

Title:
  via-rhine kernel module: PHY status 786d, resetting

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  kernel version: 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:16:27 UTC 2013 i686 athlon i686 GNU/Linux
  the mainboard is asus A8V-VM SE
  if i receive for half hour at 100Mbit full speed with partimage the network card hangs and this is the dmesg output:

  
      [ 2022.004060] WARNING: CPU: 0 PID: 3435 at /build/buildd/linux-3.11.0/net/sched/sch_generic.c:260 dev_watchdog+0x1ef/0x200()
      [ 2022.004066] NETDEV WATCHDOG: eth1 (via-rhine): transmit queue 0 timed out
      [ 2022.004069] Modules linked in: usblp pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables bridge stp llc snd_hda_codec_realtek snd_hda_intel ppdev snd_hda_codec rfcomm bnep bluetooth snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq nouveau nfsd binfmt_misc auth_rpcgss nfs_acl snd_seq_device nfs lockd sunrpc fscache mxm_wmi snd_timer wmi video snd serio_raw ttm k8temp soundcore drm_kms_helper drm i2c_viapro i2c_algo_bit parport_pc mac_hid asus_atk0110 shpchp lp parport hid_generic usbhid hid pata_acpi usb_storage via_rhine mii floppy pata_via sata_via
      [ 2022.004162] CPU: 0 PID: 3435 Comm: firefox Tainted: GF          O 3.11.0-15-generic #23-Ubuntu
      [ 2022.004167] Hardware name: System manufacturer System Product Name/A8V-VM SE, BIOS 0702    05/21/2007
      [ 2022.004171]  00000000 00000000 f580bec0 c1627228 f580bf00 f580bef0 c105267e c188f6cc
      [ 2022.004182]  f580bf1c 00000d6b c188f708 00000104 c1568a3f c1568a3f f68f0000 00000000
      [ 2022.004193]  000691a5 f580bf08 c10526d3 00000009 f580bf00 c188f6cc f580bf1c f580bf40
      [ 2022.004203] Call Trace:
      [ 2022.004213]  [<c1627228>] dump_stack+0x41/0x52
      [ 2022.004222]  [<c105267e>] warn_slowpath_common+0x7e/0xa0
      [ 2022.004229]  [<c1568a3f>] ? dev_watchdog+0x1ef/0x200
      [ 2022.004235]  [<c1568a3f>] ? dev_watchdog+0x1ef/0x200
      [ 2022.004242]  [<c10526d3>] warn_slowpath_fmt+0x33/0x40
      [ 2022.004248]  [<c1568a3f>] dev_watchdog+0x1ef/0x200
      [ 2022.004260]  [<c105d9ed>] call_timer_fn+0x2d/0xe0
      [ 2022.004268]  [<c14321fc>] ? scsi_finish_command+0xac/0x110
      [ 2022.004277]  [<c1437d10>] ? scsi_decide_disposition+0x180/0x1b0
      [ 2022.004284]  [<c10dd32c>] ? rcu_report_qs_rnp+0xac/0x110
      [ 2022.004291]  [<c1568850>] ? dev_deactivate_queue.constprop.35+0x50/0x50
      [ 2022.004298]  [<c105e8e9>] run_timer_softirq+0x179/0x220
      [ 2022.004305]  [<c1045128>] ? default_spin_lock_flags+0x8/0x10
      [ 2022.004312]  [<c1568850>] ? dev_deactivate_queue.constprop.35+0x50/0x50
      [ 2022.004321]  [<c10573f1>] __do_softirq+0xc1/0x1d0
      [ 2022.004329]  [<c1057330>] ? remote_softirq_receive+0xb0/0xb0
      [ 2022.004332]  <IRQ>  [<c1057665>] ? irq_exit+0x95/0xa0
      [ 2022.004344]  [<c1635198>] ? smp_apic_timer_interrupt+0x38/0x50
      [ 2022.004351]  [<c162dbbc>] ? apic_timer_interrupt+0x34/0x3c
      [ 2022.004356] ---[ end trace 031fe02290c75deb ]---
      [ 2022.004525] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2026.004199] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2032.004214] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2036.004191] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2042.004188] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2048.004205] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2058.004197] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2068.004202] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2076.004214] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2082.004220] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2092.004204] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2102.004204] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2112.004198] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2122.004198] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2130.004192] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2140.004202] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2150.004206] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
      [ 2160.004191] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...

  modprobe -r and modprobe the module don't solve the problem, i must
  reset the pc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269412/+subscriptions