You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2017-06-23 09:58:10
- Hering
- Member
- Registered: 2016-05-26
- Posts: 23
Wakeup after suspend fails for PCI and USB
Hello,
I just set up Archlinux on my new hardware and I remarked that when I use the suspend to disk function not everything will wake up properly again. In my case this is the graphics card (Nvidia GTX1050 Ti) and my WiFi-USB stick (CSL - 300 Mbit/s USB 2.0 WLAN Stick). After a reboot everything works again.
Checking the logs after the wakeup I see:
- journalctl
Freezing user space processes ... (elapsed 0.001 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
PM: Suspending system (mem)
Suspending console(s) (use no_console_suspend to debug)
serial 00:02: disabled
parport_pc 00:01: disabled
r8712u 3-2:1.0 wlp4s0u2: Suspending...
r8712u 3-2:1.0 wlp4s0u2: Unable to suspend
sd 1:0:0:0: [sdb] Synchronizing SCSI cache
sd 1:0:0:0: [sdb] Stopping disk
sd 0:0:0:0: [sda] Synchronizing SCSI cache
e1000e: EEE TX LPI TIMER: 00000011
sd 0:0:0:0: [sda] Stopping disk
dvb-usb: TechnoTrend TT-connect S2-4600 successfully deinitialized and disconnected.
snd_hda_intel 0000:01:00.1: spurious response 0x40:0x0, last cmd=0x5f2f26
snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x5f2f26
snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x5f2f26
snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x5f2f26
snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x5f2f26
snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x5f2f26
snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x5f2f26
snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x5f2f26
snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x5f2f26
snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x5f2f26
snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 38
PM: suspend of devices complete after 1623.826 msecs
PM: late suspend of devices complete after 1.025 msecs
xhci_hcd 0000:04:00.0: System wakeup enabled by ACPI
e1000e 0000:00:1f.6: System wakeup enabled by ACPI
xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
PM: noirq suspend of devices complete after 36.263 msecs
ACPI: Preparing to enter system sleep state S3
PM: Saving platform NVS memory
Disabling non-boot CPUs ...
smpboot: CPU 1 is now offline
smpboot: CPU 2 is now offline
smpboot: CPU 3 is now offline
ACPI: Low-level resume complete
PM: Restoring platform NVS memory
Suspended for 2398.960 seconds
Enabling non-boot CPUs ...
x86: Booting SMP configuration:
smpboot: Booting Node 0 Processor 1 APIC 0x2
cache: parent cpu1 should not be sleeping
CPU1 is up
smpboot: Booting Node 0 Processor 2 APIC 0x4
cache: parent cpu2 should not be sleeping
CPU2 is up
smpboot: Booting Node 0 Processor 3 APIC 0x6
cache: parent cpu3 should not be sleeping
CPU3 is up
ACPI: Waking up from system sleep state S3
acpi LNXPOWER:16: Turning OFF
acpi LNXPOWER:15: Turning OFF
acpi LNXPOWER:14: Turning OFF
acpi LNXPOWER:13: Turning OFF
acpi LNXPOWER:12: Turning OFF
acpi LNXPOWER:11: Turning OFF
acpi LNXPOWER:10: Turning OFF
acpi LNXPOWER:0f: Turning OFF
acpi LNXPOWER:0e: Turning OFF
acpi LNXPOWER:0d: Turning OFF
acpi LNXPOWER:0c: Turning OFF
acpi LNXPOWER:0b: Turning OFF
acpi LNXPOWER:0a: Turning OFF
acpi LNXPOWER:09: Turning OFF
acpi LNXPOWER:08: Turning OFF
acpi LNXPOWER:07: Turning OFF
acpi LNXPOWER:06: Turning OFF
acpi LNXPOWER:05: Turning OFF
acpi LNXPOWER:04: Turning OFF
acpi LNXPOWER:03: Turning OFF
acpi LNXPOWER:00: Turning OFF
xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
xhci_hcd 0000:04:00.0: System wakeup disabled by ACPI
PM: noirq resume of devices complete after 36.651 msecs
PM: early resume of devices complete after 50.402 msecs
e1000e 0000:00:1f.6: System wakeup disabled by ACPI
usb usb3: root hub lost power or was reset
usb usb4: root hub lost power or was reset
parport_pc 00:01: activated
serial 00:02: activated
rtc_cmos 00:05: System wakeup disabled by ACPI
rtc_cmos 00:05: Alarms can be up to one month in the future
sd 0:0:0:0: [sda] Starting disk
sd 1:0:0:0: [sdb] Starting disk
usb 3-2: reset high-speed USB device number 2 using xhci_hcd
ata4: SATA link down (SStatus 4 SControl 300)
ata5: SATA link down (SStatus 4 SControl 300)
ata6: SATA link down (SStatus 4 SControl 300)
ata3: SATA link down (SStatus 4 SControl 300)
ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata1.00: supports DRM functions and may not be fully accessible
ata1.00: disabling queued TRIM support
ata1.00: supports DRM functions and may not be fully accessible
ata1.00: disabling queued TRIM support
ata1.00: configured for UDMA/133
PM: resume of devices complete after 775.648 msecs
usb 1-9:1.0: rebind failed: -517
PM: Finishing wakeup.
Restarting tasks ...
dw2102: su3000_identify_state
dvb-usb: found a 'TechnoTrend TT-connect S2-4600' in warm state.
dw2102: su3000_power_ctrl: 1, initialized 0
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvbdev: DVB: registering new adapter (TechnoTrend TT-connect S2-4600)
pci_bus 0000:06: Allocating resources
pci 0000:05:00.0: bridge window [io 0x1000-0x0fff] to [bus 06] add_size 1000
pci 0000:05:00.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 06] add_size 200000 add_align 100000
pci 0000:05:00.0: bridge window [mem 0x00100000-0x000fffff] to [bus 06] add_size 200000 add_align 100000
pci 0000:05:00.0: BAR 14: no space for [mem size 0x00200000]
pci 0000:05:00.0: BAR 14: failed to assign [mem size 0x00200000]
pci 0000:05:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
pci 0000:05:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
pci 0000:05:00.0: BAR 13: no space for [io size 0x1000]
pci 0000:05:00.0: BAR 13: failed to assign [io size 0x1000]
pci 0000:05:00.0: BAR 14: no space for [mem size 0x00200000]
pci 0000:05:00.0: BAR 14: failed to assign [mem size 0x00200000]
pci 0000:05:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
pci 0000:05:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
pci 0000:05:00.0: BAR 13: no space for [io size 0x1000]
pci 0000:05:00.0: BAR 13: failed to assign [io size 0x1000]
pci 0000:05:00.0: PCI bridge to [bus 06]
done.
Time has been changed
client 737[0:0] has disconnected
Time has been changed
client 737[0:0] has disconnected
Starting system activity accounting tool...
input device has been disconnected, fd 10
dvb-usb: MAC address: bc:ea:2b:46:09:d3
[UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=65 TOS=0x00 PREC=0x00 TTL=64 ID=9229 DF PROTO=UDP SPT=51513 DPT=53 LEN=45
[UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=65 TOS=0x00 PREC=0x00 TTL=64 ID=9230 DF PROTO=UDP SPT=51513 DPT=53 LEN=45
[UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=65 TOS=0x00 PREC=0x00 TTL=64 ID=9231 DF PROTO=UDP SPT=37267 DPT=53 LEN=45
[UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=65 TOS=0x00 PREC=0x00 TTL=64 ID=9232 DF PROTO=UDP SPT=37267 DPT=53 LEN=45
[UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=65 TOS=0x00 PREC=0x00 TTL=64 ID=9233 DF PROTO=UDP SPT=48434 DPT=53 LEN=45
[UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=65 TOS=0x00 PREC=0x00 TTL=64 ID=9234 DF PROTO=UDP SPT=48434 DPT=53 LEN=45
[UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=65 TOS=0x00 PREC=0x00 TTL=64 ID=9235 DF PROTO=UDP SPT=33956 DPT=53 LEN=45
[UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=65 TOS=0x00 PREC=0x00 TTL=64 ID=9236 DF PROTO=UDP SPT=33956 DPT=53 LEN=45
[UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=65 TOS=0x00 PREC=0x00 TTL=64 ID=9237 DF PROTO=UDP SPT=42983 DPT=53 LEN=45
[UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=65 TOS=0x00 PREC=0x00 TTL=64 ID=9238 DF PROTO=UDP SPT=42983 DPT=53 LEN=45
Started system activity accounting tool.
System resumed.
Started Suspend.
sleep.target: Unit not needed anymore. Stopping.
Stopped target Sleep.
Reached target Suspend.
suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too.
Stopped target Suspend.
Operation 'sleep' finished.
<info> [1498209596.9312] manager: wake requested (sleeping: yes enabled: yes)
<info> [1498209596.9312] manager: waking up...
<info> [1498209596.9312] device (enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
client connected from 737[0:0]
1 client rule loaded
<info> [1498209597.0405] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
e1000e: enp0s31f6 NIC Link is Down
IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
client connected from 737[0:0]
1 client rule loaded
i2c i2c-4: Added multiplexed i2c bus 5
<info> [1498209597.2519] device (wlp4s0u2): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
ts2020 5-0060: Montage Technology TS2022 successfully identified
usb 1-9: DVB: registering adapter 0 frontend 0 (Montage Technology M88DS3103)...
rc rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-9/rc/rc0
Registered IR keymap rc-tt-1500
input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-9/rc/rc0/input21
dvb-usb: schedule remote query interval to 250 msecs.
dw2102: su3000_power_ctrl: 0, initialized 1
dvb-usb: TechnoTrend TT-connect S2-4600 successfully initialized and connected.
QXcbConnection: XCB error: 3 (BadWindow), sequence: 26346, resource id: 52428803, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 26899, resource id: 52428808, major code: 18 (ChangeProperty), minor code: 0
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
QObject::connect: invalid null parameter
WARNING: Cannot find style "org.kde.desktop" - fallback: "/usr/lib/qt/qml/QtQuick/Controls/Styles/Base"
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:98:103: Unable to assign int to QEasingCurve
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:98:103: Unable to assign int to QEasingCurve
ACPI group/action undefined: jack/lineout / LINEOUT
ACPI group/action undefined: jack/videoout / VIDEOOUT
<info> [1498209598.7065] manager: NetworkManager state is now DISCONNECTED
IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlp4s0u2 disabled_11b_rates=0
rfkill: Cannot get wiphy information
<info> [1498209598.7717] sup-iface[0x111cca0,wlp4s0u2]: supports 1 scan SSIDs
<info> [1498209598.7729] device (wlp4s0u2): supplicant interface state: starting -> ready
<info> [1498209598.7730] device (wlp4s0u2): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
ioctl[SIOCSIWSCAN]: Operation not permitted
wlp4s0u2: CTRL-EVENT-SCAN-FAILED ret=-1
IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
<info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1b.4/0000:04:00.0/usb3/3-2': not supported by any plugin
<info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin- dmesg | grep nvidia
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=xxx rw cryptdevice=xxx xxx=xxx resume=xxx resume_offset=xxx iommu=soft quiet loglevel=3 rd.systemd.show_status=auto rd.udev.log-priority=3 nvidia-drm.modeset=1 splash
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=xxx rw cryptdevice=xxx xxx=xxx resume=xxx resume_offset=xxx iommu=soft quiet loglevel=3 rd.systemd.show_status=auto rd.udev.log-priority=3 nvidia-drm.modeset=1 splash
[ 1.061626] nvidia: loading out-of-tree module taints kernel.
[ 1.061630] nvidia: module license 'NVIDIA' taints kernel.
[ 1.066012] nvidia-nvlink: Nvlink Core is being initialized, major device number 247
[ 1.066204] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[ 1.067069] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 381.22 Thu May 4 00:21:48 PDT 2017
[ 1.067634] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[ 1.799429] nvidia-modeset: Allocated GPU:0 (GPU-311f3fb9-c9ee-be90-d061-098bc394cb6c) @ PCI:0000:01:00.0
[ 1.908534] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
[ 1.941838] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 246
- dmesg | grep wlp4s0u2
[ 7792.445750] r8712u 3-2:1.0 wlp4s0u2: Suspending...
[ 7792.445750] r8712u 3-2:1.0 wlp4s0u2: Unable to suspend
[ 7795.436167] IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
[ 7796.889437] IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
[ 7796.957470] IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
[ 7796.958400] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 7800.099900] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 7810.111745] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 7843.114716] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 7886.140753] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 7939.097081] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 7982.805081] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 7982.806585] IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
[ 7984.246055] IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
[ 7984.301294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
[ 7984.301632] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 7987.099796] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 7997.108914] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 8030.100421] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 8073.140307] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 8126.150083] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1
[ 8189.161019] r8712u 3-2:1.0 wlp4s0u2: In r8711_wx_set_scan: bDriverStopped=1- lspci
01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Device 3732
Flags: bus master, fast devsel, latency 0, IRQ 122
Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f0000000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia- lsusb
Bus 003 Device 002: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bda Realtek Semiconductor Corp.
idProduct 0x8172 RTL8191SU 802.11n WLAN Adapter
bcdDevice 2.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 46
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0d EP 13 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0Oh and I am using the proprietary nvidia driver and running 4.11.6-1-ARCH.
Does anyone have an idea what I can do to fix it?
Best,
Hering
Last edited by Hering (2017-06-23 09:59:13)
Offline
#2 2017-06-23 19:50:43
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,017
Re: Wakeup after suspend fails for PCI and USB
Nothing "wakes up" from hibernation - the hardware gets a cold init and the memory is reloaded from disk.
According to the lspci/lsusb output the HW clearly responds.
=> How do you determine that those devices do not "wake up"?
It seems NM disconnects you when hibernating and fails to re-connect you afterwards, but that's probably more of a NM problem.
=> Did you try to stop NM and setup the wifi connection manually after waking up?
See https://wiki.archlinux.org/index.php/Wi … nual_setup
Offline
#3 2017-06-24 11:22:37
- Hering
- Member
- Registered: 2016-05-26
- Posts: 23
Re: Wakeup after suspend fails for PCI and USB
Yeah I know they don't really "wake up" 
But I guess everyone know what I meant with it.
When it starts up again all graphics which contain transparency are distorted (eg labels on desktop shortcuts etc), videos become so laggy. Just like the system is using some sort of software acceleration and not the hardware.
Also the WiFi doesn't work anymore. So the NetworkManager says it is enabled but it fails to find any networks. Restarting the service doesn't help either, only plugging the stick out and in again.
I tried to do it manually but it fails with a "can't connect to device". Using linux-ice actually let me successfully hibernate/suspend everything but that is not really an option for me.
Edit: I will attach a picture later when I got time to put it into hibernate again.
Last edited by Hering (2017-06-24 11:23:44)
Offline
#4 2017-06-24 12:58:47
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,017
Re: Wakeup after suspend fails for PCI and USB
Graphics seem a problem with the compositor, maybe X11
=> Which desktop environment / window manager do you use
As for WiFi, please ensure to stop NM after the hibernation, try the manual setup and log every command and output as is, not an interpretation of the events. (Don't start a discussion, the forum rules say you have to ;-)
Offline
#5 2017-06-30 14:28:26
- Hering
- Member
- Registered: 2016-05-26
- Posts: 23
Re: Wakeup after suspend fails for PCI and USB
Sorry for letting you wait.
Apparently updating to the new kernel 4.11.7 did somehow fix the messed up graphics but the WiFi is still not working.
Here is what I tried according to your answer:
sudo systemctl stop NetworkManager.service
iw dev wlp4s0u2 link
--> Not connected.
sudo ip link set dev wlp4s0u2 up
ip link show dev wlp4s0u2
--> 3: wlp4s0u2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether xxx brd ff:ff:ff:ff:ff:ff
sudo iw dev wlp4s0u2 scan
--> command failed: No such device (-19)Inside the journal it says:
systemd[1]: Stopping Network Manager...
NetworkManager[7684]: <info> [1498832130.2769] caught SIGTERM, shutting down normally.
NetworkManager[7684]: <info> [1498832130.2776] device (wlp4s0u2): state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3]
NetworkManager[7684]: <info> [1498832130.4856] exiting (success)
systemd[1]: Stopped Network Manager.
sudo[7763]: pam_unix(sudo:session): session closed for user root
sudo[7770]: hering : TTY=pts/2 ; PWD=/home/hering ; USER=root ; COMMAND=/usr/bin/ip link set dev wlp4s0u2 up
sudo[7770]: pam_unix(sudo:session): session opened for user root by hering(uid=0)
sudo[7770]: pam_unix(sudo:session): session closed for user root
kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
sudo[7776]: hering : TTY=pts/2 ; PWD=/home/hering ; USER=root ; COMMAND=/usr/bin/iw dev wlp4s0u2 scan
sudo[7776]: pam_unix(sudo:session): session opened for user root by hering(uid=0)
sudo[7776]: pam_unix(sudo:session): session closed for user rootAbove all happens right after a hibernate and "wakeup".
When I unplug the WiFi-Stick and plug it in again it works perfectly fine again:
wpa_supplicant[842]: nl80211: deinit ifname=wlp4s0u2 disabled_11b_rates=0
wpa_supplicant[842]: rfkill: Cannot get wiphy information
kdeconnectd[940]: UdevQt: unhandled device action "move"
kdeinit5[899]: UdevQt: unhandled device action "move"
kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
NetworkManager[7866]: <info> [1498832271.2576] sup-iface[0x2366280,wlp4s0u2]: supports 1 scan SSIDs
NetworkManager[7866]: <info> [1498832271.2585] device (wlp4s0u2): supplicant interface state: starting -> ready
NetworkManager[7866]: <info> [1498832271.2586] device (wlp4s0u2): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
sudo[7937]: hering : TTY=pts/1 ; PWD=/home/hering ; USER=root ; COMMAND=/usr/bin/journalctl -f
sudo[7937]: pam_unix(sudo:session): session opened for user root by hering(uid=0)
ModemManager[718]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1b.4/0000:04:00.0/usb3/3-2': not supported by any plugin
NetworkManager[7866]: <info> [1498832280.1139] manager: WiFi hardware radio set disabled
NetworkManager[7866]: <info> [1498832280.1139] device (wlp4s0u2): state change: disconnected -> unavailable (reason 'none') [30 20 0]
NetworkManager[7866]: <info> [1498832280.3221] audit: op="radio-control" arg="wireless-enabled:0" pid=943 uid=1000 result="success"
NetworkManager[7866]: <info> [1498832281.9781] manager: WiFi hardware radio set enabled
NetworkManager[7866]: <info> [1498832283.4192] audit: op="radio-control" arg="wireless-enabled:1" pid=943 uid=1000 result="success"
kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
wpa_supplicant[842]: nl80211: Driver does not support authentication/association or connect commands
wpa_supplicant[842]: nl80211: deinit ifname=wlp4s0u2 disabled_11b_rates=0
wpa_supplicant[842]: rfkill: Cannot get wiphy information
NetworkManager[7866]: <info> [1498832283.4764] sup-iface[0x2366000,wlp4s0u2]: supports 1 scan SSIDs
NetworkManager[7866]: <info> [1498832283.4778] device (wlp4s0u2): supplicant interface state: starting -> ready
NetworkManager[7866]: <info> [1498832283.4780] device (wlp4s0u2): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0u2: link is not ready
NetworkManager[7866]: <info> [1498832293.4947] device (wlp4s0u2): supplicant interface state: ready -> inactive
NetworkManager[7866]: <info> [1498832293.5020] policy: auto-activating connection 'xxx'
NetworkManager[7866]: <info> [1498832293.5027] device (wlp4s0u2): Activation: starting connection 'xxx' (xxx)
NetworkManager[7866]: <info> [1498832293.5029] device (wlp4s0u2): state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[7866]: <info> [1498832293.5030] manager: NetworkManager state is now CONNECTING
NetworkManager[7866]: <info> [1498832293.5034] device (wlp4s0u2): state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[7866]: <info> [1498832293.5035] device (wlp4s0u2): Activation: (wifi) access point 'xxx' has security, but secrets are required.
NetworkManager[7866]: <info> [1498832293.5035] device (wlp4s0u2): state change: config -> need-auth (reason 'none') [50 60 0]
NetworkManager[7866]: <info> [1498832293.5067] device (wlp4s0u2): state change: need-auth -> prepare (reason 'none') [60 40 0]
NetworkManager[7866]: <info> [1498832293.5071] device (wlp4s0u2): state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[7866]: <info> [1498832293.5073] device (wlp4s0u2): Activation: (wifi) connection 'xxx' has security, and secrets exist. No new secrets needed.
NetworkManager[7866]: <info> [1498832293.5074] Config: added 'ssid' value 'xxx'
NetworkManager[7866]: <info> [1498832293.5074] Config: added 'scan_ssid' value '1'
NetworkManager[7866]: <info> [1498832293.5074] Config: added 'key_mgmt' value 'WPA-PSK'
...Offline
#6 2017-06-30 15:22:16
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 21,657
Re: Wakeup after suspend fails for PCI and USB
Well r8712u is a bugfest from the staging drivers (I also had the "pleasure" of relying on it for a few months) and on its way out, it doesn't surprise me that it is causing issues. Does it work without an explicit replug if you reload the module?
sudo modprobe -r r8712u && sudo modprobe 8712uAlternatively check out its supposed replacement that is however still in development with a potential own slew of issues. rtl8192su
Last edited by V1del (2017-06-30 15:24:27)
Offline
#7 2017-06-30 15:29:23
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,017
Re: Wakeup after suspend fails for PCI and USB
In case: /usr/lib/systemd/system-sleep/reload_r8712u.sh
#!/bin/sh
case $1/$2 in
pre/*)
modprobe -r r8712u
;;
post/*)
modprobe r8712u
;;
esacbut you might have to force-remove the module (because NM et al still hanging on it)
Offline
#8 2017-07-01 09:15:54
- Hering
- Member
- Registered: 2016-05-26
- Posts: 23
Re: Wakeup after suspend fails for PCI and USB
I tried to do that but as soon as I run
sudo modprobe r8712u it literally kills my machine:
* Almost everything becomes unresponsive (UI(Plasma5) and even terminal commands).
* Shutting down via Ctrl+Del+Alt does work though except that it gets a timeout stopping /dev/dm-1 and every other process throws a "INFO: task xxx : blocked for more than 120 second".
* Rebooting does not work until I manually remove the splash entry in grub
* When logging it it loads the black KDE screen then only yakuake gets started and nothing else. But running commands in there does not work either.
* In the journal I only see "INFO: task xxx : blocked for more than 120 second" for every service
I can bring it back to work when arch-chrooting into it using a live stick and reinstall linux/linux-headers.
That is superweird... will keep searching trough the logs.
I did try the rtl8192su driver ages ago but it did not work with this stick. I will test it when there are some updates to it.
Offline
#9 2017-07-01 13:17:21
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,017
Re: Wakeup after suspend fails for PCI and USB
Did you also try to get rid of the module *before* the S4?
Offline
Pages: 1