Ubuntu

10ec:8168 Network stop working and soft reboot is not sufficient

Reported by Rik on 2011-03-31
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

Press power on button on the computer.
Ubuntu starts.
The network starts. All is up.
I start browsing the internet and after few minutes the network stop working.

==== Some important indications:

sudo reboot is not sufficient: there are only 2 ways to make network work again:
sudo halt + power on
or
sudo reboot + recovery + reboot. Entering the recovery console awake the network. A simple normal reboot DOESN'T.

Executing a ping toward the router, say:
From 192.168.0.1 icmp_seq=16 Destination Host Unreachable

that is different from a disconnected cable:
ping: sendmsg: Network is unreachable

useless commands:
sudo /etc/init.d/networking restart
sudo service networking restart
sudo ifconfig eth0 down + sudo ifconfig eth0 down
sudo ifdown -a + sudo ifup -a
Start and stop network from gnome icon (say ok but doesn't help

VirtualBox OSE can work on the network from host to guest, but obviously is not able to go beyond the NIC.

It sounds like the nic stop working and in a way that soft reboot is not sufficient, despite soft reboot in recovery mode solve the problem.

So question is: what is that normal soft reboot is not able to reset the nic while recovery is able to?

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-30-generic 2.6.32-30.59
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-30.59-generic 2.6.32.29+drm33.13
Uname: Linux 2.6.32-30-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rik 2268 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbff8000 irq 22'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,1458a002,00100001'
   Controls : 40
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfaffc000 irq 16'
   Mixer name : 'Nvidia ID a'
   Components : 'HDA:10de000a,10de0101,00100100'
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

CheckboxSubmission: 05e970936ed7907d0f132b713ba550dc
CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
Date: Thu Mar 31 18:29:30 2011
Frequency: Once a week.
HibernationDevice: RESUME=UUID=216ce44f-a994-4a63-a23d-5ab1c335d23f
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P55-UD3
ProcCmdLine: root=/dev/mapper/isw_dcaccbjjdd_Volume01 ro quiet splash
RelatedPackageVersions: linux-firmware 1.34.4
RfKill:

SourcePackage: linux
dmi.bios.date: 07/31/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: P55-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd07/31/2009:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P55-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Rik (riksoft) wrote :
kris van der Merwe (krisvdm) wrote :

I have the same problem. eth0 works fine on my laptop after bootup.
After the laptop suspends, I no longer have network access.
- "/etc/init.d/networking restart" has no effect.
- I still have an ip address (ifconfig).
- I cant ping the gateway ("Host Unreachable").

I have ubuntu 10.04
Network "card": Realtek RTL8111/8168B
So, laptop disconnects from network after a suspend,

Rik (riksoft) wrote :

I think I got it!
It seems to be correlated to the use of the nic too soon from login.
E.g., I start the computer, login appears, enter user/pass, as soon as the desktop appears I start Thunderbird: Ubuntu network stops working.
Shut down the system (or reboot in recovery to make the NIC reset as explained in the first post), test again this sequence and it behaves the same way: network freezed.
Shut down the system (or reboot in recovery to make the NIC reset as explained in the first post), login, and this time I wait few seconds befor opening Thunderbird: A-OK! All engine runnings! We have a lift off! :-)

Try this on your machines and see if the problem is for all or only for some hardware.

Brad Figg (brad-figg) on 2011-05-04
Changed in linux (Ubuntu):
status: New → Confirmed

Rik, 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 CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, 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 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 and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

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.

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

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

Please let us know your results. Thank you for your understanding.

summary: - Network stop working and soft reboot is not sufficient
+ 10ec:8168 Network stop working and soft reboot is not sufficient
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.