Network disconnected after resume from sleep and logging back

robertot5 · May 3, 2013, 2:46pm

Hi,
I have an issue with my network connection after applying the latest update yesterday:

After resuming from sleep my network connection is disconnected, same happens if I log out and then back in. I checked my NIC settings and nothing is changed, it just remains disconnected after a resume from sleep. It worked well until yesterday when I applied the latest update.
My NIC gets its IP from a router with DHCP. I have to reboot Suse in order to get network connection working.

Can you help me track down the issue ?

vazhavandan · May 3, 2013, 8:00pm

Just restart network service

 sudo systemctl restart network.service

zorbathezorb · May 4, 2013, 9:25am

I have the same problem since yesterday’s update.

what has been screwed up by the update and what action should one take to get network resume after sleep without needing to do a manual

service network restart

.

Thanks.

robertot5 · May 10, 2013, 11:41pm

Anyone found a fix yet ? I still have to manually restart network service every time a resume or log-in wich is very annoying.

nrickert · May 11, 2013, 12:48am

Is this WiFi, using NetworkManager?

If it is, then try “disable wireless” on the network applet. Then, a few seconds later, try “enable wireless”.

robertot5 · May 11, 2013, 12:54am

No, not wi-fi, wired ethernet.

Can updates be rolled back or reported ?

tsu2 · May 11, 2013, 6:14pm

If someone hasn’t already noticed,
Can go to http://bugzilla.novell.com
Search for anything recently reported, if nothing found create a bug.

Before doing that, gather some information (while experiencing your probblem)

systemctl status network.service

tail -n 50 /var/log/message

Be sure to include your version of openSUSE and Desktop(eg KDE or Gnome).

TSU

wolfi323 · May 11, 2013, 6:27pm

The earlier package versions are still available in the standard repo. You could rollback the offending package with YaST (click on “Versions” in the lower right to select which version of the package to install) or zypper (here you append the version to the package name, e.g. “my_package-3.1.5”). Then you should lock the package so that it doesn’t get updated again. (YaST: right-click on package and select “Taboo”, zypper: “zypper al packagename”)

Bugs (and buggy updates) can be reported at http://bugzilla.novell.com/.

To your original problem:
You could put a script in /etc/pm/sleep.d/ which restarts the network after a suspend.
See here for details: SDB:Pm-utils - openSUSE Wiki

tsu2 · May 12, 2013, 12:30am

I experienced this problem also shortly after my previous post.

I opened a bug at
https://bugzilla.novell.com/show_bug.cgi?id=819514

I encourage anyone else who experiences this to look at that bug and if you experienced something that is different than what is described in the bug report or this thread to add your experience to the bug report.

TSU

wolfi323 · May 12, 2013, 12:47am

Well, if you are using NetworkManager, you have to restart NetworkManger.service on 12.3…

sudo systemctl restart NetworkManager.service

robertot5 · May 12, 2013, 1:50am

tsu2:

If someone hasn’t already noticed,
Can go to http://bugzilla.novell.com
Search for anything recently reported, if nothing found create a bug.

Before doing that, gather some information (while experiencing your probblem)
systemctl status network.service
tail -n 50 /var/log/message
Be sure to include your version of openSUSE and Desktop(eg KDE or Gnome).

TSU

This is the console output while experiencing the issue ( just resumed from sleep )

linux-jspa:/home/robert # systemctl status network.service 
network.service - LSB: Configure the localfs depending network interfaces
          Loaded: loaded (/etc/init.d/network)
          Active: active (exited) since Sat, 11 May 2013 19:47:23 +0300; 6h ago
         Process: 542 ExecStart=/etc/init.d/network start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/network.service

May 11 19:47:23 linux-jspa network[542]: eth0      . . . is just beeing set up
May 11 19:47:23 linux-jspa network[542]: eth0      IP address: 192.168.1.67/24
May 11 19:47:23 linux-jspa network[542]: eth0      is up
May 11 19:47:23 linux-jspa network[542]: [1Awaiting
May 11 19:47:23 linux-jspa network[542]: Setting up service (localfs) network  .  .  .  .  .  .  .  .  .  ...done
May 11 19:47:26 linux-jspa ifup[5025]: vmnet1
May 11 19:47:26 linux-jspa ifup[5029]: No configuration found for vmnet1
May 12 02:45:17 linux-jspa dhcpcd[4613]: eth0: received SIGTERM, stopping
May 12 02:45:17 linux-jspa dhcpcd[4613]: eth0: removing default route via 192.168.1.254 metric 0
May 12 02:45:17 linux-jspa dhcpcd[4613]: eth0: removing IP address 192.168.1.67/24

linux-jspa:/home/robert # tail -n 50 /var/log/messages
May 12 02:45:31 linux-jspa kernel: [25152.523163] Extended CMOS year: 2000
May 12 02:45:31 linux-jspa kernel: [25152.523184] microcode: CPU0: new patch_level=0x010000c7
May 12 02:45:31 linux-jspa kernel: [25152.523186] Enabling non-boot CPUs ...
May 12 02:45:31 linux-jspa kernel: [25152.525453] Booting Node 0 Processor 1 APIC 0x1
May 12 02:45:31 linux-jspa kernel: [25152.536486] [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu
May 12 02:45:31 linux-jspa kernel: [25152.536488] perf: IBS APIC setup failed on cpu #1
May 12 02:45:31 linux-jspa kernel: [25152.538859] NMI watchdog: enabled, takes one hw-pmu counter.
May 12 02:45:31 linux-jspa kernel: [25152.539027] microcode: CPU1: new patch_level=0x010000c7
May 12 02:45:31 linux-jspa kernel: [25152.539979] CPU1 is up
May 12 02:45:31 linux-jspa kernel: [25152.540361] ACPI: Waking up from system sleep state S3
May 12 02:45:31 linux-jspa kernel: [25152.542206] ohci_hcd 0000:00:12.0: wake-up capability disabled by ACPI
May 12 02:45:31 linux-jspa kernel: [25152.542232] ohci_hcd 0000:00:12.1: wake-up capability disabled by ACPI
May 12 02:45:31 linux-jspa kernel: [25152.552922] ehci_hcd 0000:00:12.2: wake-up capability disabled by ACPI
May 12 02:45:31 linux-jspa kernel: [25152.552953] ohci_hcd 0000:00:13.0: wake-up capability disabled by ACPI
May 12 02:45:31 linux-jspa kernel: [25152.552977] ohci_hcd 0000:00:13.1: wake-up capability disabled by ACPI
May 12 02:45:31 linux-jspa kernel: [25152.563919] ehci_hcd 0000:00:13.2: wake-up capability disabled by ACPI
May 12 02:45:31 linux-jspa kernel: [25152.564070] ohci_hcd 0000:00:14.5: wake-up capability disabled by ACPI
May 12 02:45:31 linux-jspa kernel: [25152.564270] PM: noirq resume of devices complete after 22.202 msecs
May 12 02:45:31 linux-jspa kernel: [25152.564344] PM: early resume of devices complete after 0.049 msecs
May 12 02:45:31 linux-jspa kernel: [25152.565940] parport_pc 00:06: activated
May 12 02:45:31 linux-jspa kernel: [25152.565953] i8042 kbd 00:08: wake-up capability disabled by ACPI
May 12 02:45:31 linux-jspa kernel: [25152.566880] serial 00:09: activated
May 12 02:45:31 linux-jspa kernel: [25152.566941] pcieport 0000:00:0a.0: wake-up capability disabled by ACPI
May 12 02:45:31 linux-jspa kernel: [25152.878831] ata5: SATA link down (SStatus 0 SControl 300)
May 12 02:45:31 linux-jspa kernel: [25152.878865] ata2: SATA link down (SStatus 0 SControl 300)
May 12 02:45:31 linux-jspa kernel: [25152.878897] ata3: SATA link down (SStatus 0 SControl 300)
May 12 02:45:31 linux-jspa kernel: [25152.878928] ata6: SATA link down (SStatus 0 SControl 300)
May 12 02:45:31 linux-jspa kernel: [25152.878964] ata4: SATA link down (SStatus 0 SControl 300)
May 12 02:45:31 linux-jspa kernel: [25153.137746] /dev/vmmon[0]: HostIFReadUptimeWork: detected settimeofday: fixed uptimeBase old 18445375782864981865 new 18445375782860981869 attempts 1
May 12 02:45:31 linux-jspa kernel: [25153.382204] ata7.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out
May 12 02:45:31 linux-jspa kernel: [25153.382208] ata7.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
May 12 02:45:31 linux-jspa kernel: [25153.388142] ata7.00: configured for UDMA/66
May 12 02:45:31 linux-jspa kernel: [25156.450118] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 12 02:45:31 linux-jspa kernel: [25156.482300] ata1.00: configured for UDMA/133
May 12 02:45:31 linux-jspa kernel: [25156.493222] Extended CMOS year: 2000
May 12 02:45:31 linux-jspa kernel: [25156.493240] sd 0:0:0:0: [sda] Starting disk
May 12 02:45:31 linux-jspa kernel: [25156.502609] PM: resume of devices complete after 3939.041 msecs
May 12 02:45:31 linux-jspa kernel: [25156.502861] PM: Finishing wakeup.
May 12 02:45:31 linux-jspa kernel: [25156.502863] Restarting tasks ... done.
May 12 02:45:31 linux-jspa rtkit-daemon[5590]: The canary thread is apparently starving. Taking action.
May 12 02:45:31 linux-jspa rtkit-daemon[5590]: Demoting known real-time threads.
May 12 02:45:31 linux-jspa rtkit-daemon[5590]: Demoted 0 threads.
May 12 02:45:31 linux-jspa acpid: 1 client rule loaded
May 12 02:45:31 linux-jspa dbus[590]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
May 12 02:45:31 linux-jspa dbus[590]: [system] Successfully activated service 'org.freedesktop.PackageKit'
May 12 02:45:31 linux-jspa acpid: 1 client rule loaded
May 12 02:45:31 linux-jspa dbus-daemon[590]: dbus[590]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
May 12 02:45:31 linux-jspa dbus-daemon[590]: dbus[590]: [system] Successfully activated service 'org.freedesktop.PackageKit'
May 12 02:45:31 linux-jspa udevd[323]: RUN+="socket:..." support will be removed from a future udev release. Please remove it from: /etc/udev/rules.d/71-multipath.rules:7 and use libudev to subscribe to events.
May 12 02:45:53 linux-jspa su: (to root) roberto on /dev/pts/1

This is just after I restarted the networking service

linux-jspa:/home/roberto # systemctl status network.service 
network.service - LSB: Configure the localfs depending network interfaces
          Loaded: loaded (/etc/init.d/network)
          Active: active (running) since Sun, 12 May 2013 02:48:00 +0300; 3min 24s ago
         Process: 12332 ExecStop=/etc/init.d/network stop (code=exited, status=0/SUCCESS)
         Process: 13115 ExecStart=/etc/init.d/network start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/network.service
                  ├ 13961 /sbin/dhclient6 -6 -cf /var/lib/dhcp6/dhclient6.eth0.conf -lf /var/lib/dhcp6/dhclient6.eth0.lease -pf /var/run/dhclient6.eth0.pid...
                  └ 14654 /sbin/dhcpcd --netconfig -L -E -HHH -c /etc/sysconfig/network/scripts/dhcpcd-hook -t 0 -h linux-jspa eth0

May 12 02:48:00 linux-jspa network[13115]: eth0      DHCP6 continues in background
May 12 02:48:00 linux-jspa network[13115]: ..done    vmnet1
May 12 02:48:00 linux-jspa ifup[15552]: vmnet1
May 12 02:48:00 linux-jspa network[13115]: No configuration found for vmnet1
May 12 02:48:00 linux-jspa ifup[15556]: No configuration found for vmnet1
May 12 02:48:00 linux-jspa network[13115]: ..unused    vmnet8
May 12 02:48:00 linux-jspa ifup[15597]: vmnet8
May 12 02:48:00 linux-jspa network[13115]: No configuration found for vmnet8
May 12 02:48:00 linux-jspa ifup[15601]: No configuration found for vmnet8
May 12 02:48:00 linux-jspa network[13115]: ..unusedSetting up service network  .  .  .  .  .  .  .  .  .  ...done

zorbathezorb · May 12, 2013, 6:42am

You want to read this http://forums.opensuse.org/english/get-technical-help-here/laptop/485468-no-wireless-after-resume-suspend.html and modify “unload_modules” as suggested.

robertot5 · May 13, 2013, 8:13pm

Yes, that did the trick, it works now.

This should be mentioned on the bug page.

Thank You