1969:2062 ethernet disconnect after some minutes

[mighur]

Ethernet connection is unstable. After a couple of minutes, it disconnects without any message in log files

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-27-generic 3.8.0-27.40
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: miguel 1985 F.... pulseaudio
 /dev/snd/controlC0: miguel 1985 F.... pulseaudio
Date: Wed Jul 24 20:10:11 2013
HibernationDevice: RESUME=UUID=986fa042-1b35-4403-808a-c3792b119a72
InstallationDate: Installed on 2013-04-28 (86 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: ASUSTeK Computer INC. 1215B
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=c5f5504a-461c-43b8-b9f5-a4545150a06d ro quiet splash radeon.audio=1 radeon.modeset=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-27-generic N/A
 linux-backports-modules-3.8.0-27-generic N/A
 linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0503
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 1215B
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd11/30/2011:svnASUSTeKComputerINC.:pn1215B:pvrx.x:rvnASUSTeKComputerINC.:rn1215B:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1215B
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

mighur, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[mighur (mighur)]

Tested upstream kernel, but didn't fix the error. Ethernet continues disconnecting and also lost wifi module.

[penalvch (penalvch)]

mighur, thank you for testing the newest mainline kernel. Did this problem not occur in a release prior to Raring?

[mighur (mighur)]

The problem only occurs in Raring.
In Quantal, ethernet worked fine. I did the upgrade from Quantal and found the problem.
Later, I did a clean install of Quantal. The install process was made using ethernet connection, but it stopped working with the first boot. I don't remember the kernel release used for installer.

Thank you.

[penalvch (penalvch)]

mighur, the next step is to perform a bisect from Quantal to Raring, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[mighur (mighur)]

I tried to follow the bisection wiki, but I was unable. System became unusable and had to do a fresh install from zero. The problem persists.

The information I can add:
Last good kernel release (no bug) precise: linux 3.2.0-52.78
First bad kernel release (bug) quantal: linux 3.5.0-17.28

I'm unable to go further without breaking my system.

[penalvch (penalvch)]

mighur, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please just make a comment to this?

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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.

[mighur (mighur)]

Hello.

I was unable to perform bisection, so I waited a couple of months and upgraded to 13.10.
In this release, it seems to be solved.

Thank you.

[penalvch (penalvch)]

mighur, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204613/comments/10 regarding this being fixed with an update. 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.