Ifconfig not in RUNNING state after suspend, kernel upgrade issue ?

raphix · 2011-03-04 15:37:25

I have a problem with the wired connection on my laptop: after a suspend-to-disk, I cannot get it back (it is ok when I start the computer).
I have a Dell e4200, with an Intel card, and it worked perfectly before some updates last month (among which a kernel upgrade to 2.6.37 from 36).

ifconfig, after a suspend, reads :

eth0    Link encap:Ethernet  HWaddr 00:24:E8:D7:18:60  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1  // the "RUNNING" flag is missing here!
          RX packets:123 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:21634 (21.1 Kb)  TX bytes:5007 (4.8 Kb)
          Interrupt:22 Memory:f6ae0000-f6b00000

and dmesg :

e1000e: Intel(R) PRO/1000 Network Driver - 1.2.7-k2
e1000e: Copyright (c) 1999 - 2010 Intel Corporation.
e1000e 0000:00:19.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
e1000e 0000:00:19.0: setting latency timer to 64
e1000e 0000:00:19.0: irq 41 for MSI/MSI-X
e1000e 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:24:e8:d7:18:60
e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
e1000e 0000:00:19.0: eth0: MAC: 7, PHY: 8, PBA No: 7002ff-0ff
e1000e 0000:00:19.0: PME# enabled
e1000e 0000:00:19.0: BAR 0: set to [mem 0xf6ae0000-0xf6afffff] (PCI address [0xf6ae0000-0xf6afffff])
e1000e 0000:00:19.0: BAR 1: set to [mem 0xf6adb000-0xf6adbfff] (PCI address [0xf6adb000-0xf6adbfff])
e1000e 0000:00:19.0: BAR 2: set to [io  0xefe0-0xefff] (PCI address [0xefe0-0xefff])
e1000e 0000:00:19.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
e1000e 0000:00:19.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100107)
e1000e 0000:00:19.0: PME# disabled
e1000e 0000:00:19.0: irq 41 for MSI/MSI-X
e1000e 0000:00:19.0: irq 41 for MSI/MSI-X
ADDRCONF(NETDEV_UP): eth0: link is not ready
e1000e 0000:00:19.0: PME# enabled
e1000e 0000:00:19.0: BAR 0: set to [mem 0xf6ae0000-0xf6afffff] (PCI address [0xf6ae0000-0xf6afffff])
e1000e 0000:00:19.0: BAR 1: set to [mem 0xf6adb000-0xf6adbfff] (PCI address [0xf6adb000-0xf6adbfff])
e1000e 0000:00:19.0: BAR 2: set to [io  0xefe0-0xefff] (PCI address [0xefe0-0xefff])
e1000e 0000:00:19.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
e1000e 0000:00:19.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100107)
e1000e 0000:00:19.0: PME# disabled
e1000e 0000:00:19.0: irq 41 for MSI/MSI-X
e1000e 0000:00:19.0: eth0: MAC Wakeup cause - Link Status Change
e1000e 0000:00:19.0: PME# enabled

I tried to "rmmod e1000e, modprobe e1000e", to upgrade my kernel (I think now I should downgrade it to the kernel26-lts).

Indeed, dhcpcd times out when trying to find a carrier, and netcfg says "Fail - no connection". And, for information, I have a perfectly functional wifi connection aside.

If anyone has an idea, or a a thread with a solution, he/she is more than welcome !

raphix · 2011-03-08 19:22:25

up?
This is really annoying and I don't know how to fix it at all.

abruptadieu · 2011-03-14 14:14:36

I'm having the same problem. No closer to figuring it out. I can easily replicate the problem, and my wireless is also unaffected.

raphix · 2011-03-21 12:31:52

And are you using the same laptop ?

Maybe we could file a bug, if only I knew where I could do it - since I don't exactly know which package is concerned (kernel ? networking ?) ...

ahuillet · 2011-04-02 18:25:33

I am encountering the same problem with my Dell Latitude E6400 with Intel 82567LM (e1000e).

the sad clown · 2011-04-02 19:33:03

I had a similar problem that I solved by suspending my wireless module (ath5k in my case) when going into suspend to ram. Follow these directions from the pm-utils wiki and see if it doesn't help you:

Put your config file into /etc/pm/config.d/ instead. You can just put a simple text file with
SUSPEND_MODULES="button uhci_hcd"
named "modules" or "config" into /etc/pm/config.d and it will override the settings in the system wide configuration file.

Just change the module in the example to whatever you are using for your NIC.

Last edited by the sad clown (2011-04-02 19:34:14)

abruptadieu · 2011-04-30 03:58:00

I finally got this fixed with the help of a bug report I found:
https://bugs.archlinux.org/task/22957

This step fixed it for me:

Disabling runtime-pm in conf.d will solve the (e1000e) problem.

Arch Linux

#1 2011-03-04 15:37:25

Ifconfig not in RUNNING state after suspend, kernel upgrade issue ?

#2 2011-03-08 19:22:25

Re: Ifconfig not in RUNNING state after suspend, kernel upgrade issue ?

#3 2011-03-14 14:14:36

Re: Ifconfig not in RUNNING state after suspend, kernel upgrade issue ?

#4 2011-03-21 12:31:52

Re: Ifconfig not in RUNNING state after suspend, kernel upgrade issue ?

#5 2011-04-02 18:25:33

Re: Ifconfig not in RUNNING state after suspend, kernel upgrade issue ?

#6 2011-04-02 19:33:03

Re: Ifconfig not in RUNNING state after suspend, kernel upgrade issue ?

#7 2011-04-30 03:58:00

Re: Ifconfig not in RUNNING state after suspend, kernel upgrade issue ?

Board footer