When I hibernate my laptop, the ethernet interface vanishes

Bug #148116 reported by Matt Lee
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-meta (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Baltix)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I have a Thinkpad x60s.

When I hibernate it and go to another building (home, office, etc) my ethernet device is not found by either Network Manager or on the system itself.

sudo dhclient eth0 reports 'No such device, eth0'

Tags: cft-2.6.27
Revision history for this message
jesper (jesper-linuxdocs) wrote :

I confirm that after suspend, my ethernet devices don't come up as well. The following commands are needed to restore them again:

sudo ifconfig -s eth1 up
sudo ifconfig -s eth0 up
sudo killall NetworkManager -KILL
sudo /etc/dbus-1/event.d/25NetworkManager start

Which gets boring after a while. NetworkManager seems to hang on the non-existing devices so needs to be killed hard.

Revision history for this message
Jurgis Pralgauskis (jurgis-pralgauskis) wrote :

similar problems for me (only with gutsy)

"sudo ifup eth0" doesn't help, as it doesn't see the interface

but sometimes it vanishes, sometimes - not, I couldn't find the rule
(I tried to hibernate with unpulgged cabel, and then wake up with plugged and vice versa - but sometimes it works, sometimes - no :?)
but if I unhibernate after a longer time (few hours) - it is always gone (as much as I remember)

If I was logged in with other console (Ctrl+Alt+F1), and hibernated from the main Gnome - the things always seemed to work OK (though I didn't try to wait long)

I noticed, that wireless interface wanishes also if it is used - so probably the one, which i
as I understood vanishes/disapears the one interface, which is/was currently used - very strange

Asus Z99H series
RTL8111/8168B PCI Express Gigabit Ethernet controller

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Hardy Heron Alpha2 release will be coming out soon. It will have an updated version of the kernel. It would be great if you could test with the LiveCD for this new release and verify if this issue still exists. However, note that you'll only be able to test Suspend from the LiveCD. Mattl, can you verify if this is only an issue for you when you Hibernate, or does it also occur when you Suspend? Thanks. I'll be sure to update this report when Alpha2 is available. Thanks!

Changed in linux:
status: New → Incomplete
Changed in linux-source-2.6.22:
status: New → Invalid
Changed in linux-meta:
status: New → Invalid
Revision history for this message
Oscar Manuel Gómez Senovilla (omgs) wrote :

I'm not sure if this is related or nobody ever reported. Anyway, here it goes.

When waking up after hibernating, the interface goes up, but at least the post-up script is not launched. I have to ifdown and ifup again to perform the necessary actions (firewall rules).

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. Note you will only be able to test Suspend from the LiveCD, not Hibernate. If you can, please verify if this bug still exists or not and report back your results. Thanks!

Revision history for this message
Oscar Manuel Gómez Senovilla (omgs) wrote :

Please correct if I'm wrong, but I think that it's a bug at application level, not at kernel level. Of course, if I'm wrong and the only way to fix that is updating the kernel, then there is no problem, at least as I don't have to wait for the next stable release.

There's another problem, as you already mention. The problem happens when hibernating, and if I can't hibernate, then I can't verify if it's fixed, so I think the proposed solution is invalid.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

A new task against the actively developed kernel is open so we're closing the task against linux-source-2.6.22. Thanks!

Changed in linux-source-2.6.22:
status: New → Won't Fix
Revision history for this message
Connor Imes (ckimes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Oscar Manuel Gómez Senovilla (omgs) wrote :

At least for me, as I comment in bug 153727, comment 25, this doesn't happen. Please review your udev configuration.

Revision history for this message
Connor Imes (ckimes) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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