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
I had the same problem in ubuntu 14.04. The following thread shows a
workaround:
http://askubuntu.com/questions/230698/how-to-restart-the-networking-
service?lq=1
sudo ifdown --exclude=lo -a sudo ifup --exclude=lo -a
This worked for me, restarted all interfaces except loopback.
--
You
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
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
Public bug reported:
Using Ubuntu 14.04 with kernel 3.13.0-24-generic, we frequently see the
following messages in dmesg
[ 3337.690516] via-rhine :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
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316740
