1969:1091 Ethernet connection lost after a while

[infopox]

Ethernet network connection lost after a while.

WORKAROUND: Temporarily via:
ifconfig eth0 mtu 9000

or permanently in network manager.

---
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: eric 2349 F.... pulseaudio
 /dev/snd/controlC0: eric 2349 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=8b4bc51b-4c9c-4e1e-823d-7daca442aab6
InstallationDate: Installed on 2014-06-08 (344 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard h8-1340ef
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=3a75e1e0-7666-4142-a826-9eedc88f7f5d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-16-generic N/A
 linux-backports-modules-3.19.0-16-generic N/A
 linux-firmware 1.143
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
Tags: vivid
Uname: Linux 3.19.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
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: CZC2316CR9
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAMI:bvr7.15:bd07/02/2012:svnHewlett-Packard:pnh8-1340ef:pvr1.00:rvnPEGATRONCORPORATION:rn2AD5:rvr1.03:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: h8-1340ef
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard
---
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: eric 2617 F.... pulseaudio
 /dev/snd/controlC0: eric 2617 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=8b4bc51b-4c9c-4e1e-823d-7daca442aab6
InstallationDate: Installed on 2014-06-08 (348 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=3a75e1e0-7666-4142-a826-9eedc88f7f5d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-18-generic N/A
 linux-backports-modules-3.19.0-18-generic N/A
 linux-firmware 1.143
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: vivid
Uname: Linux 3.19.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 10/20/2014
dmi.bios.vendor: AMI
dmi.bios.version: 8.21
dmi.board.name: 2AD5
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.03
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAMI:bvr8.21:bd10/20/2014:svnHewlett-Packard:pn:pvr1.00:rvnPEGATRONCORPORATION:rn2AD5:rvr1.03:cvnHewlett-Packard:ct3:cvr:
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard

[infopox (eric-poquillon)]

Not sure my initial post was logged so I repeat bug description :

With kernel 3.19.0-17-generic , network connection is lost after a while (seconds) after starting using internet connection (downloading a page in Firefox). Ping to a server in the local network returns "Destination Host Unreachable" while ping on loopback 127.0.0.1 is OK.

When starting with 3.19.0-16 this does not happen.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1455940

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.

[infopox (eric-poquillon)]

Sorry,

No longer able to revert to the bug configuration (configuration reverted to stable kernel version)

[penalvch (penalvch)]

infopox, please execute the apport-collect while in the default kernel configuration.

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

I have updated my bios according to previous message.

Bug remains identical and same problem occurs with the new kernel 3.19.0-18.
This seems to be a compatibility issue with my ethernet adaptor as WIFI seems to work correctly.

I will issue an apport-collect command following this update

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[infopox (eric-poquillon)]

apport information

[penalvch (penalvch)]

infopox, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[infopox (eric-poquillon)]

After testing with the last upstream kernel :
uname -a
Linux whitcomb 4.1.0-040100rc4-generic #201505181436 SMP Mon May 18 18:38:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

The issue is still present : acces to ethernet is lost, WIFI is oK

(I had to remove virtualbox and nvidia modules to test).

Also tested with 4.1.0-040100rc3-generic with the same result.

last working (no issue) version is
uname -a
Linux whitcomb 3.19.0-16-generic #16-Ubuntu SMP Thu Apr 30 16:09:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Hope this help

Eric

[penalvch (penalvch)]

infopox, the next step is to fully commit bisect from kernel 3.19.0-16 to 3.19.0-18.18 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

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

[infopox (eric-poquillon)]

Hi,
I have eventually performed the commit bisect (sorry it took me so long time) between 3.19.0-16 and 3.19.0-17 as the last was the one where I first had the problem.

here is git message after last git bisect command :
-----------------
5cfb2705fc0c05b182f523b2aee5143c4b402536 is the first bad commit
commit 5cfb2705fc0c05b182f523b2aee5143c4b402536
Author: Matthew Garrett <email address hidden>
Date: Fri Apr 24 14:59:01 2015 +0800

    PCI: Don't clear ASPM bits when the FADT declares it's unsupported

    Communications with a hardware vendor confirm that the expected behaviour
    on systems that set the FADT ASPM disable bit but which still grant full
    PCIe control is for the OS to leave any BIOS configuration intact and
    refuse to touch the ASPM bits. This mimics the behaviour of Windows.

    BugLink: http://bugs.launchpad.net/bugs/1441335

    Signed-off-by: Matthew Garrett <email address hidden>
    Signed-off-by: Bjorn Helgaas <email address hidden>
    (cherry picked from commit 387d37577fdd05e9472c20885464c2a53b3c945f)
    Signed-off-by: Alex Hung <email address hidden>
    Acked-by: Colin King <email address hidden>
    Acked-by: Tim Gardner <email address hidden>
    (backported from commit 387d37577fdd05e9472c20885464c2a53b3c945f upstream)
    Signed-off-by: Brad Figg <email address hidden>

:040000 040000 9c1764a2e96361d082806c42b03e848facf4914e a77df148e590328d4a76f775f95a6353bfebb563 M drivers
:040000 040000 069a2e3a077ee8342264ef9da0df5e3d97f94eaf e22c053cb941d5409e27a39590bf8413f2bb2fac M include
--------------------------------------------------------

and here is the output of git bisect log :

-------------------------------------------------------
git bisect log
# bad: [0a19ec4f3046a2c5955578ba54cc3067876fe408] UBUNTU: Ubuntu-3.19.0-17.17
# good: [ab7ec15d305950bf911023d72eb7d225593bf688] UBUNTU: Ubuntu-3.19.0-16.16
git bisect start 'Ubuntu-3.19.0-17.17' 'Ubuntu-3.19.0-16.16'
# good: [205c4ddd68190c2433a7636224f6882fa312fd83] radeon: Do not directly dereference pointers to BIOS area.
git bisect good 205c4ddd68190c2433a7636224f6882fa312fd83
# bad: [d359cc6fa8c33b397ae4dc881aad494d185d58ee] drm/atomic-helper: add connector->dpms() implementation
git bisect bad d359cc6fa8c33b397ae4dc881aad494d185d58ee
# good: [77194b8d152b4e8e32bffe81b6f7574ce78f9cde] drivers/of: Add empty ranges quirk for PA-Semi
git bisect good 77194b8d152b4e8e32bffe81b6f7574ce78f9cde
# good: [057521712bbe7b7d05fc27753242edefbf704063] clk: divider: fix calculation of maximal parent rate for a given divider
git bisect good 057521712bbe7b7d05fc27753242edefbf704063
# good: [b5e9721ffc043b02d9dbf5cec47ad38803a3a4f6] UBUNTU: SAUCE: vesafb: Set mtrr:3 (write-combining) as default
git bisect good b5e9721ffc043b02d9dbf5cec47ad38803a3a4f6
# bad: [4547f0a3499ac87aae348bd06fb48abfecd81287] i915_bpo: Update to 4.1rc1
git bisect bad 4547f0a3499ac87aae348bd06fb48abfecd81287
# bad: [ae516dc61ed82132df1bca378a9b971770b4a242] regmap: Skip read-only registers in regcache_sync()
git bisect bad ae516dc61ed82132df1bca378a9b971770b4a242
# bad: [5cfb2705fc0c05b182f523b2aee5143c4b402536] PCI: Don't clear ASPM bits when the FADT declares it's unsuppor...

[penalvch (penalvch)]

infopox, and finally could you please test the latest mainline kernel (4.1-rc6) and advise to the results?

[infopox (eric-poquillon)]

Hi,

Having tested linux-image-4.1.0-040100rc6-generic_4.1.0-040100rc6.201506010235_amd64, result is BAD

Same loss of access to wired network.

[infopox (eric-poquillon)]

Hi,

This bug seems linked to the ARL driver used for the eth0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 08).

It is identified in BugZilla : https://bugzilla.kernel.org/show_bug.cgi?id=70761 as
"Bug 70761 - AR8161 wir alx driver: Randomly stops to receive packets with small MTU"

A palliative solution is to increase MTU size above 8192.

This can be down temporarily with
ifconfig eth0 mtu 9000

Or permanently in network manager.

This palliative solution is effective in my case with kernel 3.19.0-21-generic and I tested it satisfactorily with 4.1.0-040100rc8.

[penalvch (penalvch)]

infopox, just to advise, bugzilla is legacy, and not the ideal venue for this problem.

Despite this, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (netdev CC Matthew Garrett, Jay Cliburn, and Chris Snook) by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger-lists.html . It can take a day for the new e-mail to show up in the respective archive.

Thank you for your understanding.

[Dan Andreșan (danyer)]

I was one of the people affected by this bug, I still have the same computer, but I haven't seen the issue anymore (since a long time, 4 years?!).
So I guess this bug can be closed?

Thank you,
Dan.

[penalvch (penalvch)]

infopox:

1) Could you please advise to the upstream URL requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455940/comments/33 ?

2) Is this reproducible in a supported release?