[Bug 985531] New: After suspend/resume, network doesnt have ip address(es) at all any more, needs NetworkManager.service restart
http://bugzilla.opensuse.org/show_bug.cgi?id=985531 Bug ID: 985531 Summary: After suspend/resume, network doesnt have ip address(es) at all any more, needs NetworkManager.service restart Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: abittner@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Leap 42.1, x64, (with KOTD head though, currently at 4.7.0-rc3-1.g59af2d0-default) Putting a simple leap 42.1 installation (kde) to suspend via kde start menu, and waking it up after a longer time (multiple hours or almost a day timespan?) the single wired network interface (pcie some realtek simple device) does not have or retrieve any ip address(es) any more. The gigabit ethernet switch I have here shows a gigabit link after the resume/wakeup of the leap machine but ifconfig shows no ip address(es) on that ethernet device any more and waiting a little while doesnt help either. ifconfig after wakeup/resume: ifconfig eth1 Link encap:Ethernet HWaddr E0:CB:4E:BA:5C:32 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21634598 errors:0 dropped:0 overruns:0 frame:0 TX packets:20922711 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12430067154 (11854.2 Mb) TX bytes:10076199568 (9609.4 Mb) 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:65536 Metric:1 RX packets:201761 errors:0 dropped:0 overruns:0 frame:0 TX packets:201761 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:510656583 (487.0 Mb) TX bytes:510656583 (487.0 Mb) I checked via systemctl the status of the NetworkManager.service at that moment: Jun 17 23:16:17 linux-box0 NetworkManager[5062]: <info> NetworkManager state is now ASLEEP Jun 17 23:16:17 linux-box0 NetworkManager[5062]: <info> (eth1): link disconnected Jun 18 12:41:13 linux-box0 NetworkManager[5062]: <info> wake requested (sleeping: yes enabled: yes) Jun 18 12:41:13 linux-box0 NetworkManager[5062]: <info> waking up... Jun 18 12:41:13 linux-box0 NetworkManager[5062]: <info> (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jun 18 12:41:13 linux-box0 NetworkManager[5062]: <info> NetworkManager state is now DISCONNECTED Jun 18 12:41:16 linux-box0 NetworkManager[5062]: <info> (eth1): link connected Jun 18 12:41:16 linux-box0 NetworkManager[5062]: <info> (eth1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] When I suspend the system for maybe only a few hours or so I have not noticed these problems. It mostly happens when the system is suspended for a longer time. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=985531
http://bugzilla.opensuse.org/show_bug.cgi?id=985531#c1
Wei GUO
http://bugzilla.opensuse.org/show_bug.cgi?id=985531
http://bugzilla.opensuse.org/show_bug.cgi?id=985531#c2
--- Comment #2 from andreas bittner
participants (1)
-
bugzilla_noreply@novell.com