r8101 unstable under 16.04.1 various kernels
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Hardware: Intel D945GCLF with onboard Realtek R8101 LAN controller.
OS: Ubuntu 16.04.1 LTS Server Edition - upgraded from 12.04 LTS
By default Ubuntu chooses the r8169 module for this controller, which does not work correctly. (This has been an issue for a number of releases).
Realtek provide a Linux driver at the below site:
http://
With previous Ubuntu releases, compiling and using this module has worked perfectly, however with Ubuntu 16.04.1 I have had limited success.
I have downloaded and compiled v1.030 and used it with a number of supported kernels but am getting similar issues with all.
Note that I have also disabled IPv6 on this machine having seen indications that this may be causing the problem - I have seen no change in behaviour since doing this.
Kernel 4.4.0-34-generic
> Immediately following boot (or depmod r8101) the interface works and I can successfully communicate over the interface I have seen consistent downloads of 6MB/s. At a seemingly random point later, connectivity will cease without warning. At this time the stats (RX/TX bytes/packets) in ifconfig cease to increase but the interface remains UP. A ping to the locally configured static IP returns successfully. "ifdown && ifup" does not fix the problem, but "rmmod && depmod" does. The point at which the connectivity ceases does not appear to be consistent in either time or amount of data transferred.
Will append further debugging information when I can get it off the server.
tags: | added: r8101 |
tags: | added: ethernet networking |
tags: | added: kernel-bug-exists-upstream |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1654559
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.