using xfce, screen does not come back on from suspend, on kernels newer than 4.4.38 on Slackware64-14.2

khronosschoty · 11-17-2017, 08:55 PM

So on Slackware64-14.2 when using xfce the screen does not come back on after resuming from suspend. This issue did not appear until after kernel 4.4.38. This issue does not appear to effect kde. If console switching takes place then the screen wakes back up.

brobr · 11-18-2017, 05:19 PM

In XFCE there is a setting in the powermanager plugin to lock the screen before suspend. A mouse click is needed to wake the screen, i.e it lights up and asks for the login password. Could something like this be at work here?

EDIT: maybe a problem with an extra graphics card as encountered here?

bamunds · 11-20-2017, 10:20 AM

I have this same issue with Slackware64-14.2 multilib running Nouveau. I also frequently when using KDE have the issue that after a suspend the AR9271 wireless dongle is hung in a stopped state. Instead I've built and used the latest window manager versions of WindowMaker, FVWM, and E, which have never hung after suspend. I access suspend by creating icons with pm-suspend-hybrid xlock calls. I've been unable to get a trace or seen anything in the logs for X.Org.log that indicate anything nefarious causing this hang, but it would be nice to get XFCE and KDE working properly. Maybe by reporting it here volkerdi or AlienBob might be aware and find or suggest some test to narrow down the issue. Cheers.

brobr · 11-20-2017, 01:27 PM

Hi bamunds, I had some problems after suspending at work and resuming at home; mostly something with dns and/or caching by browsers. Anyway, plainly annoying. I now have a script in /etc/pm/sleep.d/10_disconnect that ensures that all connections get stopped via networkmanager before sleep kicks in:

Code:

#!/bin/bash
#
# want to disconnect internet stuff when going to sleep
# kill wifi connection; kill mail, browsers, dropbox
# like nm does after losing connection
#

case $1 in
    hibernate)
	/usr/bin/nmcli networking off
    ;;
    suspend)
	/usr/bin/nmcli networking off
    ;;
    thaw)
    ;;
    resume)
	/usr/bin/nmcli networking on 
	# maybe not to save battery when opening on train    
    ;;
    *) 
    ;;
esac

scripts in /etc/NetworkManager/dispatcher.d then take over.

Maybe something to consider?

hth

bamunds · 11-20-2017, 08:21 PM

Thanks for the suggestion. I'm not using network manager, I'm using WICD, so would have to adapt this for WICD. However, I'm not sure why the problem would only exist with the DE's and not the WM's. Also I don't have two graphics cards, so the XFCE failing to provide a screen is also pointing to an issue. I've read the article you referred to and it doesn't apply to my setup, the only thing I could try is applying the NVIDIA drivers instead of Nouveau just to see if it makes a difference. Maybe I'll try that this weekend.

bamunds · 10-23-2018, 09:32 AM

I'm not sure what corrected this issue shortly after my last post. However, after a re-install of the base system, due to problems created after trying KTOWN latest, I again have this problem happening. IE. The system will not recover from from a suspend and only provides a blank screen or if screen recovers the wireless interface will not. I'm using kernel 4.4.157, the standard DE's and WM's, and Nouveau. The problem is now happening with both 'stable' WM's and DE's. I suspect the issue is with DBUS attempting to communicate with the wifi dongle (AR9271) and waiting for reply, which it never gets. I have found that in the cases when the screen recovers if I disconnect the wifi dongle, then stop /etc/rc.d/rc.wicd, wait about 30 seconds, re-insert the wifi dongle, and start rc.wicd that sometimes the network will recover. Usually I can wait two to ten minutes for a recovered screen, but have been forced to hard reboot the PC. Nothing in X.org.
DMesg says the following:
[27357.658636] ath: phy0: Unable to reset channel (2412 Mhz) reset status -5
[27357.658651] ath: phy0: Unable to set channel
[27357.761600] ath: phy0: Chip reset failed
[27357.761607] ath: phy0: Unable to reset channel (2412 Mhz) reset status -22
[27357.761743] ath: phy0: Unable to set channel
[27357.874294] ath: phy0: Failed to wakeup in 500us

I'll appreciate help in diagnosing or suggestions on fixes. Cheers, BrianA_MN