Bugzilla – Bug 151892
ethernet partly broken after suspend/resume (8139cp)
Last modified: 2006-03-14 09:12:52 UTC
After I suspend and resume my laptop, the 8139 ethernet onboard gets a link local 169.254 address only from NetworkManager. It does not detect cable plug/unplug any longer, and if I configure the network interface by hand, it is still unable to ping anything. Removing and reinserting the 8139cp module does not help either, I have to reboot the machine fully to get a working ethernet interface again. This worked in 10.0.
Since this bug does not appear to be Xen related I am reassigning this to the screening team.
It's no XEN problem allright. Will: Can you attach about 200 lines of the syslog here?
Created attachment 69838 [details] /var/log/messages around suspend/resume cycle - resume at 16:20 I never said it was XEN based. Note from the original report that the problem does not seem to be NetworkManager related, i cannot get the network interface to work by hand configuration of a static IP or by calling dhclient manually.
Some others are having this problem too: see http://mail.gnome.org/archives/networkmanager-list/2006-February/msg00090.html http://mail.gnome.org/archives/networkmanager-list/2006-February/msg00215.html My /sys/class/net/eth0/carrier is 1 before suspend and 1 after resume. ifconfig shows that eth0 is UP in both cases. Unplugging and replugging the ethernet cable after resume does not create any output in the system log.
Mobile team: Can you provide a comment here?
With even manual configuration not producing a working connection I would say it's either a driver problem or an IRQ-problem. I'd say it's something for the kernel-guys. Will, can you tell us the pci-ids of the network card, please, so I can see if we have anothe rmachine with that card.
Will, try booting with pci=noacpi or pci=routeirq - maby this helps.
02:01.0 Class 0200:10ec:8139 (rev 20). I have the machine here if you want to borrow it. On suspend I get the message "Disabling IRQ #10", testing as michaelg suggests.
Stefan, when I am not using NM, I can hand configure the network, after it resumes borken. " Suspend Resume rcnetwork stop ifconfig eth0 10.10.103.190 netmask 255.255.0.0 ping 10.10.0.8 " works. With NM involved, even after rcnetwork stop, this doesn't help.
Ah, then I misunderstood the first comment. Seife, can you please take care of that? We have a few machines with that type of NIC, and if necessary Will has offered his machine.
pci=noacpi or pci=routeirq don't help - with noacpi the driver can't initialize eth0 at all.
Does apic boot param help?
apic didn't help either.
Works now in beta7