Ubuntu
linux package

Realtek RTL8111/8168B NIC not working - regression from 9.10

Bug #597995 reported by Eneko Lacunza on 2010-06-24

This bug affects 7 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: linux-image-2.6.32-22-generic

Kernel identifies NIC as eth0, but it doesn't work. If I try a manual dhclient on it, the following appears:

elacunza@elacunza-laptop:~$ sudo dhclient eth0
[sudo] password for elacunza:
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

SIOCSIFFLAGS: Cannot allocate memory
SIOCSIFFLAGS: Cannot allocate memory
Listening on LPF/eth0/00:1e:33:25:9c:a5
Sending on LPF/eth0/00:1e:33:25:9c:a5
Sending on Socket/fallback
receive_packet failed on eth0: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.36
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: elacunza 2464 F.... pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe4500000 irq 22'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,10250283,00100004'
   Controls : 18
   Simple ctrls : 10
Date: Thu Jun 24 09:48:16 2010
HibernationDevice: RESUME=UUID=23122aa1-07fe-46ba-bd56-7827031f68e9
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Acer TravelMate 8371
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=9f6e42db-d282-4c36-83ff-84c0139f176b ro quiet splash
ProcEnviron:
LANG=es_ES.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 10/29/2009
dmi.bios.vendor: Acer
dmi.bios.version: V1.18
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: TravelMate 8371
dmi.board.vendor: Acer
dmi.board.version: PSMBOU-1234567
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: None
dmi.modalias: dmi:bvnAcer:bvrV1.18:bd10/29/2009:svnAcer:pnTravelMate8371:pvrV1.18:rvnAcer:rnTravelMate8371:rvrPSMBOU-1234567:cvnAcer:ct10:cvrNone:
dmi.product.name: TravelMate 8371
dmi.product.version: V1.18
dmi.sys.vendor: Acer

Tags:

Revision history for this message

Eneko Lacunza (elacunza) wrote on 2010-06-24:

AlsaDevices.txt Edit (461 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (273 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (45.8 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (8.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (48.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (556 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (12.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (704 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (605 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.5 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (124 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (122.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (262.9 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (87.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Eneko Lacunza (elacunza) wrote on 2010-06-25:

Ok, this is a little embarrassing/strange.

I left yesterday the laptop turned off and recharging battery.

Today I turned it on, and voilà, cabled NIC works perfectly.

It is very strange, as yesterday's init (thursday) was the 2nd time Ubuntu 10.04 was loaded after install. I updated from 9.10 on wednesday afternoon, and loaded 10.04 after the installation was complete (didn't have cabled network that day).

I tried some command-line commands I found on internet, but apparently they didn't succeed, at least not yesterday:

sudo mii-tool --reset
sudo ethtool -s eth0 wol g
sudo ethtool -s eth0 wol d
sudo ethtool -s eth0 wol g

Revision history for this message

Eneko Lacunza (elacunza) wrote on 2010-07-13: Re: [Bug 597995] Re: Realtek RTL8111/8168B NIC not working - regression from 9.10

Today the problem has appeared again. Seems that it happened because I
turned on the laptop without cabled network, and connected the cable
after loging in. Network didn't work, and NetworkManager reported cabled
network as not connected.

Same errors about memory appeared in the command line.

This time I was able to fix the problem unloading the kernel module
r8169 and loading it again (rmmod + modprobe).

I didn't try this aproach the first time the problem happened.

Cheers
Eneko

--
Zuzendari Teknikoa / Director Técnico
Binovo IT Human Project, S.L.
Telf. 943493611
Astigarraga bidea 2, planta 2, Derecha, Oficina 6; 20180 Oiartzun
www.binovo.es

Revision history for this message

apavlov (apavlov) wrote on 2010-08-05:

I have the same model of NIC, and this problem has been reproducible for me ~80% after a suspend to RAM/resume cycle for the past couple of months (it seems to have come up after some kernel update, as everything used to work fine just after a fresh Lucid Lynx install). The network stays down, and after I issue
# ifconfig eth0 up
the "SIOCSIFFLAGS: Cannot allocate memory" shows up, which makes me reboot (everything works fine after then, most often until the next STR-Resume).

Would be great if this issue was considered...

Revision history for this message

beric (ericbouer) wrote on 2010-09-16:

I have the same problem. when it happens it always after suspend to RAM/DISK.
Killing NetworkManager does not help.
rmmod/insmod 8169 does not help.

=====================
ifconfig eth0 up
SIOCSIFFLAGS: Cannot allocate memory
=====================
I tried closing some applications to free some memory and it sometimes work...

Revision history for this message

Kojo Gambrah (kgambrah) wrote on 2010-11-15:

Freeing up some memory and running

sudo ifconfig eth0 down
sudo ifconfig eth0 up

worked for me. Before freeing up memory, I had about 1GB of free memory though.
Yes, that is strange but I prefer the workaround to rebooting.

Brad Figg (brad-figg) on 2011-04-06

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2012-06-09:

Eneko Lacunza, 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? Can you try 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 run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

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

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

tags:	removed: networking
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Eneko Lacunza (elacunza) wrote on 2012-06-11:

It has been a while that I haven't noticed problems with the NIC. I do not resume/suspend, and don't have a way to reproduce the problem to check newer kernels.

I think it would be better to check whether apavlov or beric continue to have suspend/resume problems.

penalvch (penalvch) on 2012-06-11

Changed in linux (Ubuntu):
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

Realtek RTL8111/8168B NIC not working - regression from 9.10

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package