Ethernet interface disappears after hibernation on DQ965COEKR running Feisty herd 3

[Marc Tardif]

I'm running Feisty herd 3 for i386 on a DQ965COEKR motherboard. When booting after hibernation, the ethernet interfaces disappears.

Reproduction steps:
1. Select System->Quit->Hibernation
2. Wait until the machine shutdowns
3. Turn on the machine
4. Run the command ifconfig

Expected result:
The eth0 interface should appear.

Actual result:
The eth0 interfaces does not appear in the output of ifconfig. Running dhclient restart doesn't enable the interface either.

[Ben Collins (ben-collins)]

ifconfig by itself will only show interfaces that are up. Do "ifconfig -a".

I am pretty sure this is a NetworkManager bug, if anything.

[Marc Tardif (cr3)]

ifconfig -a doesn't even show the eth0 interface after booting from hibernation.

[Ben Collins (ben-collins)]

Can you lsmod after hybernation and see if e1000 is still loaded? If not, try

    sudo modprobe e1000

If it is, then do

    sudo modprobe -r e1000
    sudo modprobe e1000

[Ampinder (ajaysingh99)]

Hi Ben,
           I redid the hibernation process.
These are the steps:
1. Select System->Quit->Hibernation
2. Wait until the machine shutdowns
3. Turn on the machine
4. Run the command ifconfig

Like the first time, the ethernet interface disappeared. I followed your instructions.
First, I did: lsmod |grep e1000 and it was there. So I did: sudo modprobe -r e1000 and sudo modprobe e1000 and my ethernet interface came back, I got an ip address assigned to my ethernet card.

Thanks

[Tollef Fog Heen (tfheen)]

Moving milestone forward.

[Kyle McMartin (kyle)]

This is fucked. Your syslog claims that the e1000 checksum is corrupted, so it fails to insert it, but you say that later the driver loads fine.

Can you add the e1000.eeprom_bad_csum_allow=1 to the kernel command line or add it for modprobe.d so that the bad checksum is ignored (I added this to 2.6.20-10) and see if that helps at all?

Cheers,
 Kyle

[Ben Collins (ben-collins)]

Well, I tested the two machines that I have with e1000 (one was a DG965SS), and both came back properly with e1000 still working.

We've seen this checksum problem before, so this bug is really a dupe. It's shown up less and less as the e1000 driver gets worked on.

Setting to needs info so Marc's scripts catch it and he can test the work around. Assigning back to Kyle till we get confirmation on whether the workaround helps.

[Marc Tardif (cr3)]

First, I upgraded the kernel to 2.6.20-12-generic:

$ uname -a
Linux ubuntu 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux

Second, I added the e1000.eeprom_bad_csum_allow=1 kernel option to the /boot/grub/menu.lst file and applied the changes with the update-grub command.

Third, I rebooted the machine and made sure the kernel option was in place in /proc/cmdline:

root=UUID=b074b7f0-c59e-4ef8-acd1-e52995dc491e ro e1000.eeprom_bad_csum_allow=1 quiet splash

Fourth, I hibernated and I still observed the same behavior as before where eth0 wouldn't come up, the e1000 module was listed and needed to be removed and added again to work.

[Ben Collins (ben-collins)]

Kyle is talking to the e1000 maintainer.

[Erik Andrén (erik-andren)]

Is this still an issue?

[pras (bugsy01)]

One way to avoid this is to stop the network before hibernating.. ifdown eth0 works... i have found that it resumes the eth on restart,,

[Albert Cardona (cardona)]

I have the same problem. I have noticed though, that when putting the laptop to sleep from:

- the System / Quit... the eth0 NEVER disappears
- closing the lid: the eth0 disappears sometimes, seems correlated to whether the network was up or not.

[Leann Ogasawara (leannogasawara)]

Hi Marc,

Can you confirm if this is still an issue in the latest Hardy Alpha release or close this report if this is no longer an issue? Thanks.

[Leann Ogasawara (leannogasawara)]

I just tested for this bug with Intrepid Beta on the system with the DQ965COEKR motherboard and it is no longer an issue. The system is able to Hibernate and resume successfully and the eth0 interface is up upon resuming. I'm marking this bug Fix Released for Intrepid. Against 2.6.20 this will be closed. Thanks.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.