Wired network fails after suspend

Questions about cabled networking
Forum rules
Before you post please read this

Wired network fails after suspend

Postby JoeInMN on Mon Nov 14, 2011 4:00 pm

Not sure that any of the other somewhat similar posts here addressed this issue; please point me to the relevant post if I missed it... Thanks.

Anyway:

My MSI Wind U100 netbook's internet connection is through my friend's ethernet cable. At system startup, everything works fine, and Network Manager shows a connection through "Auto Ethernet." If I let the screensaver (blank screen with screenlock) come on, the network is still connected as normal when I unlock the screen again. If I log out and log back in again, network is still good. However, if I close the lid and put the computer into suspension, then when I start back up again, the network icon shows its busy animation for a couple of minutes, and I eventually get this notification:

Disconnected
The network connection has been
disconnected.


After that, nothing I can think of to do will bring the network back online. "Auto Ethernet" still appears in the Network Manager, but clicking it only repeats the trying-and-failing routine. Turning the modem off and on does nothing. Logging out and in again doesn't help. The only way I can get back online is to go to Quit/Restart and completely reboot the computer. I am running Update Pack 3 as per the instructions here:

http://blog.linuxmint.com/?p=1836

The same issue occurs if I boot into the 2.6.39-2-486 kernel from GRUB.

At the moment, with the connection working, I get this from the terminal:

Code: Select all
jpl@jpl-u100-mint-debian ~ $ sudo ifconfig
[sudo] password for jpl:
eth1      Link encap:Ethernet  HWaddr aa:00:04:00:0a:04 
          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::a800:4ff:fe00:a04/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8901 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8250 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9246802 (8.8 MiB)  TX bytes:1593138 (1.5 MiB)
          Interrupt:42 Base address:0x4000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:92 errors:0 dropped:0 overruns:0 frame:0
          TX packets:92 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7808 (7.6 KiB)  TX bytes:7808 (7.6 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:24:21:8a:4d:7d 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:17 Memory:f8348000-f8348100


"Auto Ethernet" is the only connection shown by the Network Manager menu or its "Edit Connections" dialog. I have no way of testing a wireless connection at the moment.

Thanks for any help anyone can give me to fix this.
User avatar
JoeInMN
Level 3
Level 3
 
Posts: 102
Joined: Wed Nov 17, 2010 5:52 pm

Linux Mint is funded by ads and donations.
 

Re: Wired network fails after suspend

Postby Vermind on Thu Dec 01, 2011 9:29 pm

Hi,
I have a similar issue, but perhaps different symptoms.
Can you get the output of dmesg and ifconfig when the network is broken, save it to a file, and put that here or on pastebin.com?

I am running Linux 3.1.0-1.
I am also running Update Pack 3, 64-bit, ASUS UL30VT. The wired card is an ath9k card:
Code: Select all
$ lspci
...
04:00.0 Ethernet controller: Atheros Communications AR8131 Gigabit Ethernet (rev c0)

My symptoms are that I cannot bring the wired network online after a suspend and resume. It does not matter whether the wired or wireless or both were on or off before suspend.
dmesg and ifconfig look like this:

Code: Select all
$ dmesg
...
[127223.700502] cfg80211: Calling CRDA to update world regulatory domain
[127223.844584] ath9k 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[127223.844601] ath9k 0000:03:00.0: setting latency timer to 64
[127223.895814] ath: EEPROM regdomain: 0x60
[127223.895817] ath: EEPROM indicates we should expect a direct regpair map
[127223.895821] ath: Country alpha2 being used: 00
[127223.895823] ath: Regpair used: 0x60
[127223.898068] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[127223.899695] Registered led device: ath9k-phy0
[127223.899705] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc900110a0000, irq=17
[127223.953653] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[127223.963817] atl1c 0000:04:00.0: irq 47 for MSI/MSI-X
[127224.180313] atl1c 0000:04:00.0: Error get phy ID
[127224.181447] ADDRCONF(NETDEV_UP): eth1: link is not ready

$ ifconfig
eth1      Link encap:Ethernet  HWaddr 48:5b:39:39:33:1d 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:16621523431650 errors:99729140589900 dropped:33243046863300 overruns:16621523431650 frame:83107617158250
          TX packets:16621523431650 errors:66486093726600 dropped:0 overruns:16621523431650 carrier:33243046863300
          collisions:83107617158250 txqueuelen:1000
          RX bytes:16621523431650 (15.1 TiB)  TX bytes:16621523431650 (15.1 TiB)
          Interrupt:47

...


The amounts of errors, dropped, and overruns look unhealthy. I have no idea how to fix this. I have tried to find a way to properly "reset" the connection. My current try is this:

Code: Select all
sudo service network-manager stop; sudo service networking stop; sudo ifconfig wlan0 down;  sudo ifconfig eth1 down; sudo modprobe -r ath9k;sudo modprobe -r ath9k_common;sudo modprobe -r ath9k_hw; sudo modprobe -r ath; sudo modprobe ath9k; sudo ifconfig wlan0 up; sudo ifconfig eth1 up; sudo service networking start; sudo service network-manager start


However, it seems to make no difference. A reboot fixes this, so some sort of "reset" of the network modules should do it as well...

Any ideas?
Vermind
Level 1
Level 1
 
Posts: 8
Joined: Fri Aug 26, 2011 1:04 am

Re: Wired network fails after suspend

Postby JoeInMN on Mon Dec 26, 2011 3:24 am

Vermind wrote:Hi,
I have a similar issue, but perhaps different symptoms.
Can you get the output of dmesg and ifconfig when the network is broken, save it to a file, and put that here or on pastebin.com?


Sorry for the long delay here; I broke my netbook and replaced it with a different model, and the new one doesn't seem to have the same problem, so far at least.
User avatar
JoeInMN
Level 3
Level 3
 
Posts: 102
Joined: Wed Nov 17, 2010 5:52 pm

Re: Wired network fails after suspend

Postby gryphon on Sat Nov 02, 2013 5:50 am

I had this problem both with Debian sid and LMDE. I wanted to share a solution in case others have the same issue.

1. Fire up the terminal and become root (su)
2. lshw -C network
3. take note of the modules required for your ethernet and/or wireless cards (for each card, under "configuration" you'll see "driver = module name", in my case it was atl1c for ethernet and iwlwifi for wireless)
4. gedit /etc/pm/config.d/unload_modules
5. enter the following line and save:
SUSPEND_MODULES="$SUSPEND_MODULES atl1c iwlwifi"
(remember to replace atl1c and iwlwifi with the modules you've found before!)

That's it. Hope that helps.
User avatar
gryphon
Level 1
Level 1
 
Posts: 31
Joined: Fri Nov 01, 2013 12:05 pm


Return to Ethernet

Who is online

Users browsing this forum: No registered users and 0 guests