Results 1 to 7 of 7

Thread: Problems recovering from sleep

  1. #1

    Default Problems recovering from sleep

    I recently installed Leap 42.3 and have run into problems: when I close the lid on my laptop (ie fold the screen onto the keyboard) the laptop goes to sleep. This takes 5-10 seconds, and I can see no problem with it. The problem arises later, when I fold the screen back up: the laptop comes to life, and within three seconds it displays the mouse pointer on the screen. Unfortunately, that is all it does: no amount of waiting will get anything else on the screen, and no amount of wiggling with the mouse will move the pointer on the screen.

    When I was using Leap 42.1 this worked flawlessly on the same hardware (Lenovo Ideapad Z710). Does anybody have any tips?

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: Problems recovering from sleep

    You'll probably have to see if your system log can provide any info.

    Kill (Power off) your machine and reboot as you're probably already doing.

    Then, run the following command which should display your last entries in reverse order (last entries first)
    Code:
    journalctl -r -b -1
    If you have any problems interpreting the entries, post the last 50 or so entries.

    HTH,
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  3. #3

    Default Re: Problems recovering from sleep

    I gave the command you recommend, and I got nothing that looks fishy in any way, although I must admit I have never seen this log file before. Anyway, among the text I got there was a small notice (the first 1-2 lines of text) that only users belonging to group X (not the real name, but I forgot it) get to see system messages. So I added myself to this group, and now I get ridiculous amounts of text! Before adding myself I got a total of 25-30 lines of text, but now I get in the region of 3500...

    Is there anything specific I should be looking for in all this?

  4. #4
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,710
    Blog Entries
    1

    Default Re: Problems recovering from sleep

    Is there anything specific I should be looking for in all this?
    You could run it like this (following an unsuccessful resume and reboot) to capture to a file
    Code:
    sudo journalctl -r -b -1 > journal.txt
    an if necessary upload the log to https://paste.opensuse.org/ for others to review. Post the link that it generates here. Having said all that, for resume issues like this I seldom find anything useful reported from the journal logging.

    It would be useful to tell us which desktop environment is use and the graphics hardware you have. For the last answer run...
    Code:
    /usr/sbin/hwinfo --gfxcard

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,710
    Blog Entries
    1

    Default Re: Problems recovering from sleep

    Returning to your opening post where you mentioned...
    The problem arises later, when I fold the screen back up: the laptop comes to life, and within three seconds it displays the mouse pointer on the screen. Unfortunately, that is all it does: no amount of waiting will get anything else on the screen, and no amount of wiggling with the mouse will move the pointer on the screen.
    If you switch VT consoles to VT1 and back again (ie Ctrl+Alt+F1 then Ctrl+Alt+F7) does that help at all?

  6. #6

    Default Re: Problems recovering from sleep

    This ought to be the relevant parts of the logfile:

    feb 05 00:06:10 linux-ncuh systemd-sleep[5105]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
    feb 05 00:06:10 linux-ncuh systemd[1]: Starting Suspend...
    feb 05 00:06:10 linux-ncuh systemd[1]: Reached target Sleep.
    feb 05 00:06:10 linux-ncuh nm-dispatcher[5090]: Dispatching action 'down' for wlan0
    feb 05 00:06:10 linux-ncuh systemd[1]: Started Network Manager Script Dispatcher Service.
    feb 05 00:06:10 linux-ncuh dbus[1020]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    feb 05 00:06:10 linux-ncuh systemd[1]: Starting Network Manager Script Dispatcher Service...
    feb 05 00:06:10 linux-ncuh kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: <warn> Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
    feb 05 00:06:10 linux-ncuh dbus[1020]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
    feb 05 00:06:10 linux-ncuh kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
    feb 05 00:06:10 linux-ncuh kernel: nouveau 0000:01:00.0: DRM: resuming client object trees...
    feb 05 00:06:10 linux-ncuh kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1b40822c)
    feb 05 00:06:10 linux-ncuh kernel: nouveau 0000:01:00.0: priv: HUB0: 6013d4 ffff573f (1f408200)
    feb 05 00:06:10 linux-ncuh kernel: nouveau 0000:01:00.0: DRM: resuming kernel object tree...
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: <info> NetworkManager state is now ASLEEP
    feb 05 00:06:10 linux-ncuh nscd[1047]: 1047 monitored file `/etc/resolv.conf` was moved into place, adding watch
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: You can find my version in /etc/resolv.conf.netconfig ...
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: <13>Feb 5 00:06:10 dns-resolver: You can find my version in /etc/resolv.conf.netconfig
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: <13>Feb 5 00:06:10 dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
    feb 05 00:06:10 linux-ncuh dns-resolver[5033]: You can find my version in /etc/resolv.conf.netconfig
    feb 05 00:06:10 linux-ncuh dns-resolver[5031]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A)
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: DFS Master region: unset
    feb 05 00:06:10 linux-ncuh kernel: cfg80211: World regulatory domain updated:
    feb 05 00:06:10 linux-ncuh avahi-daemon[1032]: Interface wlan0.IPv4 no longer relevant for mDNS.
    feb 05 00:06:10 linux-ncuh avahi-daemon[1032]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.64.
    feb 05 00:06:10 linux-ncuh avahi-daemon[1032]: Withdrawing address record for 192.168.1.64 on wlan0.
    feb 05 00:06:10 linux-ncuh avahi-daemon[1032]: Interface wlan0.IPv6 no longer relevant for mDNS.
    feb 05 00:06:10 linux-ncuh kernel: wlan0: deauthenticating from 30:91:8f:97:f5:d1 by local choice (Reason: 3=DEAUTH_LEAVING)
    feb 05 00:06:10 linux-ncuh avahi-daemon[1032]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::1acf:5eff:fe48:ffd.
    feb 05 00:06:10 linux-ncuh avahi-daemon[1032]: Withdrawing address record for fe80::1acf:5eff:fe48:ffd on wlan0.
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: <info> (wlan0): DHCPv4 state changed bound -> done
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 2133
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: <info> (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: <info> sleeping...
    feb 05 00:06:10 linux-ncuh NetworkManager[1150]: <info> sleep requested (sleeping: no enabled: yes)
    feb 05 00:06:10 linux-ncuh systemd-logind[1058]: Lid closed.
    There is only one line of text before this, telling me when the logfile starts and ends.

    As to the graphics hardware, the command /usr/sbin/hwinfo --gfxcard gives the following text:

    08: PCI 02.0: 0300 VGA compatible controller (VGA)
    [Created at pci.378]
    Unique ID: _Znp.dJHy2PPnIb9
    SysFS ID: /devices/pci0000:00/0000:00:02.0
    SysFS BusID: 0000:00:02.0
    Hardware Class: graphics card
    Model: "Intel 4th Gen Core Processor Integrated Graphics Controller"
    Vendor: pci 0x8086 "Intel Corporation"
    Device: pci 0x0416 "4th Gen Core Processor Integrated Graphics Controller"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x3809
    Revision: 0x06
    Driver: "i915"
    Driver Modules: "i915"
    Memory Range: 0xd1000000-0xd13fffff (rw,non-prefetchable)
    Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable)
    I/O Ports: 0x5000-0x503f (rw)
    IRQ: 30 (38734 events)
    Module Alias: "pci:v00008086d00000416sv000017AAsd00003809bc03sc00i00"
    Driver Info #0:
    Driver Status: i915 is active
    Driver Activation Cmd: "modprobe i915"
    Config Status: cfg=no, avail=yes, need=no, active=unknown

    20: PCI 100.0: 0302 3D controller
    [Created at pci.378]
    Unique ID: VCu0.VEYgQPhgi3E
    Parent ID: vSkL.T2uGoOSG4d3
    SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
    SysFS BusID: 0000:01:00.0
    Hardware Class: graphics card
    Model: "nVidia GM108M [GeForce 840M]"
    Vendor: pci 0x10de "nVidia Corporation"
    Device: pci 0x1341 "GM108M [GeForce 840M]"
    SubVendor: pci 0x17aa "Lenovo"
    SubDevice: pci 0x3809
    Revision: 0xa2
    Driver: "nouveau"
    Driver Modules: "drm"
    Memory Range: 0xd0000000-0xd0ffffff (rw,non-prefetchable)
    Memory Range: 0xa0000000-0xafffffff (ro,non-prefetchable)
    Memory Range: 0xb0000000-0xb1ffffff (ro,non-prefetchable)
    I/O Ports: 0x4000-0x4fff (rw)
    Memory Range: 0xb2000000-0xb207ffff (ro,non-prefetchable,disabled)
    IRQ: 27 (20 events)
    Module Alias: "pci:v000010DEd00001341sv000017AAsd00003809bc03sc02i00"
    Driver Info #0:
    Driver Status: nouveau is active
    Driver Activation Cmd: "modprobe nouveau"
    Config Status: cfg=no, avail=yes, need=no, active=unknown
    Attached to: #7 (PCI bridge)

    Primary display adapter: #8


    The desktop I am using is KDE (whatever version comes as standard). The tip of trying CTRL+ALT+F1 and CTRL+ALT+F7 did not achieve anything.

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,710
    Blog Entries
    1

    Default Re: Problems recovering from sleep

    Quote Originally Posted by dubbelnisse1980 View Post
    This ought to be the relevant parts of the logfile:
    Unfortunately, that only shows the suspend operation.

    As to the graphics hardware, the command /usr/sbin/hwinfo --gfxcard gives the following text:
    Two graphics devices are shown (Intel and nVidia) ie Optimus (hybrid) graphics is employed here. The output also shows that you're using the open source graphics "nouveau" driver for the nVidia GM108M chipset. It might be beneficial to install bumblebee...

    https://en.opensuse.org/SDB:NVIDIA_Bumblebee

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •