1106:3106 [Asus P7H55-M/BR] via-rhine kernel module: PHY status 786d, resetting

[Felipe Rechia]

Using Ubuntu 14.04 with kernel 3.13.0-24-generic, we frequently see the following messages in dmesg

[ 3337.690516] via-rhine 0000:05:0a.0 eth3: Transmit timed out, status 0003, PHY status 786d, resetting...

This causes the ethernet adapter to go down and back up, and it discards packets. This problem has been observed while using
ubuntu 12.04 and now 14.04 as well. I've heard from my colleagues that this did not happen in ubuntu 10.04

All the symptoms collected by apport-bug should be attached.

lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D7p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Tue May 6 14:34:18 2014
HibernationDevice: RESUME=UUID=e2f02941-0250-40f9-ba63-51aaa0ec4f6a
InstallationDate: Installed on 2014-04-25 (10 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
Lsusb:
 Bus 002 Device 003: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: placeholder root=UUID=6b961bba-379e-4454-8846-224ffb47ac8a ro
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0406
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7H55-M BR
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd07/16/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MBR:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Felipe Rechia (feliperechia)]

just another remark: I was about to add this info as symptoms to bug 1269412, but the apport-collect tool advised to open a new bug instead.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc4-utopic/

[Felipe Rechia (feliperechia)]

I am not sure about when I will be able to test this, as the server is in use by several people (the affected interfaces are used only for traffic testing purposes, by using iperf or simple ping).

If I test it with another kernel, I will let you know as soon as possible.

For now I am marking it as unable to test upstream.

[Felipe Rechia (feliperechia)]

I found in several forums a few pieces of information about this message. It seems that the noapic kernel flag may minimize the problem occurrence.

https://lists.debian.org/debian-kernel/2012/01/msg01091.html

When I was testing with 12.04 I could not boot my system after using that flag. I haven't tried with ubuntu 14.04 though.

[Carlos Luna (caralu1974)]

Systemd 210.

I`m running Ubuntu 12.04 updated till today (20 Jun 2014 ) and aswell Debian Testing with KDE updated and I have the same trouble the network is not working after a 30 o 45 minutes; I can not restart the network so if I wanna have the network running well I must restart the machine.
May some one help me please?

Syslog:
May 9 16:44:10 pcdebian kernel: [ 2071.820186] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
May 9 16:44:20 pcdebian kernel: [ 2081.820185] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
May 9 17:00:16 pcdebian kernel: [ 3037.820197] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
Kern.log:
May 6 12:35:48 pcdebian kernel: [ 1383.808509] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
May 6 13:26:54 pcdebian kernel: [ 0.822714] via_rhine: v1.10-LK1.5.1 2010-10-09 Written by Donald Becker
May 6 13:26:54 pcdebian kernel: [ 0.823126] via-rhine 0000:00:12.0 eth0: VIA Rhine II at 0x1f200, 00:19:db:a0:d6:13, IRQ 23
May 6 13:26:54 pcdebian kernel: [ 0.823905] via-rhine 0000:00:12.0 eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1
May 6 13:37:07 pcdebian kernel: [ 625.820368] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
May 6 13:37:17 pcdebian kernel: [ 635.820197] via-rhine 0000:00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
Ubuntu kern.log
May 5 19:28:54 caralu74 kernel: [ 451.136479] device eth0 left promiscuous mode
May 5 19:29:01 caralu74 kernel: [ 458.572040] device eth0 entered promiscuous mode
May 5 19:36:50 caralu74 kernel: [ 926.820645] via-rhine 0000:00:12.0: eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
May 5 19:36:50 caralu74 kernel: [ 926.821393] via-rhine 0000:00:12.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
May 5 19:36:54 caralu74 kernel: [ 930.820180] via-rhine 0000:00:12.0: eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
May 9 16:00:02 caralu74 kernel: [ 5408.820181] via-rhine 0000:00:12.0: eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
####### ####### ####### #####
And this could be useful:
May 6 16:13:53 caralu74 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
May 6 16:13:58 caralu74 NetworkManager[ 1568]: <warn> (eth0): DHCPv4 request timed out.
May 6 16:13:58 caralu74 NetworkManager[ 1568]: <info> (eth0): canceled DHCP transaction, DHCP client pid 2876
May 6 16:13:58 caralu74 NetworkManager[ 1568]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
May 6 16:13:58 caralu74 NetworkManager[ 1568]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) started...
May 6 16:13:58 caralu74 NetworkManager[ 1568]: <info> (eth0): device state change: ip-config -> failed (reason 'ip-config- unavailable' ) [70 120 5]
May 6 16:13:58 caralu74 NetworkManager[ 1568]: <warn> Activation (eth0) failed.
May 6 16:13:58 caralu74 NetworkManager[ 1568]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) compl...

[penalvch (penalvch)]

Carlos Luna, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[penalvch (penalvch)]

Felipe Rechia, the next step would be to fully commit bisect the kernel in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Felipe Rechia (feliperechia)]

Hello Christopher,

Unfortunately I have left the company where I had this bug. I no longer have access to the hardware and I cannot test it further.

I am not sure if anyone else was following up the problem, our workaround was to use USB to Ethernet adapters instead of the via-rhine quad pci cards.

I will not be able to provide the required symptoms.

Thank you for your analysis!

[penalvch (penalvch)]

Felipe Rechia, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1316740/comments/11 regarding you no longer have access to the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Carlos Luna (caralu1974)]

I have testing and trying to solve or have some workaround, so I add noapic to the kernel line and this make the net work fine, but after several minutes the system freezes and disconect keyboard and mouse usb, as well I have tried with noacpi with the same results, the best result is around 1 hour and half working well but finally the system freezes.
Maybe to some persons could work add noapic or noacpi to the kernel line.

[penalvch (penalvch)]

Carlos Luna", thank you for your comment. Unfortunately, as this bug report is closed, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs"