← Back to team overview

kernel-packages team mailing list archive

[Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18


Regarding the MTU workaround, I've experimented and with Ubuntu 16.04
and kernel 4.4.0-21, it is not necessary to set the MTU nearly as high
as 8192. It still fails for me with MTU set to auto or 1500 or 2000, but
with MTU = 2100, it seems to work OK with no overruns. I haven't tried
to narrow it further, but I suspect 2048 is a magic number.

MTU = 2100 seems to avoid the SSH issues I was sometimes seeing with a
much larger MTU.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to

Status in linux package in Ubuntu:

Bug description:
  Partial lshw output:

         description: Ethernet interface
         product: AR8161 Gigabit Ethernet
         vendor: Qualcomm Atheros
         physical id: 0
         bus info: pci@0000:04:00.0
         logical name: eth0
         version: 08
         serial: 70:54:d2:97:05:11
         size: 1Gbit/s
         capacity: 1Gbit/s
         width: 64 bits
         clock: 33MHz
         capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
         configuration: autonegotiation=on broadcast=yes driver=alx duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
         resources: irq:30 memory:f7100000-f713ffff ioport:d000(size=128)

  Partial ifconfig output:
  eth0      Link encap:Ethernet  HWaddr 70:54:d2:97:05:11
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:1276 errors:609 dropped:0 overruns:609 frame:0
            TX packets:1215 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:230131 (230.1 KB)  TX bytes:142978 (142.9 KB)

  The ethernet adapter stopped working on upgrade from linux
  3.19.0-16-generic to 3.19.0-18-generic. Upon inital system start, I
  can successfully ping a remote server, but once I try any TCP
  connection, even ping fails.

  If I fallback to 3.19.0-16, everything is working OK.

  WORKAROUND: In Network manager, set the ethernet connection's MTU
  value from automatic to 8192.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
   /dev/snd/controlC2:  mark       2611 F.... pulseaudio
   /dev/snd/controlC1:  mark       2611 F.... pulseaudio
   /dev/snd/controlC0:  mark       2611 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Sat May 23 10:21:44 2015
  HibernationDevice: RESUME=UUID=b4733b71-2c28-4a85-8450-6f330135cfe4
  InstallationDate: Installed on 2013-04-24 (758 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
  MachineType: Hewlett-Packard h8-1360t
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=578349d7-ca6f-4750-b977-7674ad95c763 ro quiet splash vt.handoff=7
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware                             1.143.1
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-20 (3 days ago)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.15
  dmi.board.name: 2AD5
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: 2MD3140FD9
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi:bvnAMI:bvr7.15:bd07/02/2012:svnHewlett-Packard:pnh8-1360t:pvr1.00:rvnPEGATRONCORPORATION:rn2AD5:rvr1.03:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: h8-1360t
  dmi.product.version: 1.00
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to: