[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem with systemd-sleep in Jessie



On 10/23/2014 08:29 PM, Don Armstrong wrote:
> On Thu, 23 Oct 2014, ~Stack~ wrote:
>> It boots and it will sit at the log in screen for quite some time like
>> everything is good and happy. If I log in either via GUI (LXDE) or via
>> command line, the laptop goes to sleep anywhere between 2 and 15
>> seconds later. I have to hit the power button (no other button on the
>> laptop is responsive) and it will wake up again but promptly go back
>> to sleep 2-15 seconds later. And repeat.
> 
> For starters, if you append systemd.unit=rescue.target to the kernel
> command line, you'll get a rescue shell that you can use to interrogate
> the system.

Thanks! That does appear to work well to get me in un-interrupted.

> 
> I'm suspecting that you have some sort of contest between pm-utils or
> similar trying to suspend the laptop, but I'm not certain.
> 
> You should be able to examine the logs and use journalctl to see
> precisely what systemd is trying to do at that point.

Errr...fraid this is all rather new to me but at the moment I am not
getting much of anything out of journalctl. Let me bust out my
search-foo and see if I can get something useful.

> 
> You can also change /etc/systemd/logind.conf, and change the
> HandlePowerKey=, HandleSuspendKey=, HandleHibernateKey=,
> HandleLidSwitch= all to ignore temporarily.

Done. That seems to work! The laptop isn't sleeping incessantly. :-)




So while I was waiting on a response, I copied off the syslog to another
box to examine it (in only 3 tries! :-). There is a re-occuring theme
and it does look like I may have just missed the info previous to the
systemd-sleep. See snippet below. The CTRL-EVENT-SCAN-STARTED /always*/
starts the problem and the nm-dispatcher /always*/ ends.

*Where always == every time I have found it in my logs so far. :-)

There are usually several seconds between CTRL-EVENT-SCAN-STARTED and
whatever happened in the log before it. After this, the pattern is
almost identical every time and takes about the same amount of time.


sysctl snippet:

Oct 23 19:15:37 Senta wpa_supplicant[877]: wlan0: CTRL-EVENT-SCAN-STARTED
Oct 23 19:15:38 Senta NetworkManager[582]: <info> sleep requested
(sleeping: no  enabled: yes)
Oct 23 19:15:38 Senta NetworkManager[582]: <info> sleeping...
Oct 23 19:15:38 Senta NetworkManager[582]: <info> (wlan0): device state
change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Oct 23 19:15:38 Senta NetworkManager[582]: <info> (wlan0): deactivating
device (reason 'sleeping') [37]
Oct 23 19:15:38 Senta NetworkManager[582]: <info> (wlan0): canceled DHCP
transaction, DHCP client pid 2400
Oct 23 19:15:38 Senta kernel: [  394.584207] wlan0: deauthenticating
from 00:16:01:2d:98:ae by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 23 19:15:38 Senta wpa_supplicant[877]: wlan0:
CTRL-EVENT-DISCONNECTED bssid=00:16:01:2d:98:ae reason=3 locally_generated=1
Oct 23 19:15:38 Senta systemd-udevd[197]: Network interface NamePolicy=
disabled on kernel commandline, ignoring.
Oct 23 19:15:38 Senta kernel: [  394.610725] cfg80211: Calling CRDA to
update world regulatory domain
Oct 23 19:15:38 Senta kernel: [  394.685745] cfg80211: World regulatory
domain updated:
Oct 23 19:15:38 Senta kernel: [  394.685754] cfg80211:  DFS Master
region: unset
Oct 23 19:15:38 Senta kernel: [  394.685758] cfg80211:   (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Oct 23 19:15:38 Senta kernel: [  394.685765] cfg80211:   (2402000 KHz -
2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Oct 23 19:15:38 Senta kernel: [  394.685771] cfg80211:   (2457000 KHz -
2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Oct 23 19:15:38 Senta kernel: [  394.685777] cfg80211:   (2474000 KHz -
2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Oct 23 19:15:38 Senta kernel: [  394.685782] cfg80211:   (5170000 KHz -
5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
Oct 23 19:15:38 Senta kernel: [  394.685788] cfg80211:   (5250000 KHz -
5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Oct 23 19:15:38 Senta kernel: [  394.685794] cfg80211:   (5490000 KHz -
5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Oct 23 19:15:38 Senta kernel: [  394.685799] cfg80211:   (5735000 KHz -
5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Oct 23 19:15:38 Senta kernel: [  394.685804] cfg80211:   (57240000 KHz -
63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Oct 23 19:15:38 Senta dbus[586]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 23 19:15:38 Senta systemd-sleep[2471]: Suspending system...
Oct 23 19:15:38 Senta dbus[586]: [system] Successfully activated service
'org.freedesktop.nm_dispatcher'
Oct 23 19:15:38 Senta nm-dispatcher: Dispatching action 'down' for wlan0




One other thing that is very odd is that I see a lot of these messages
below. They are usually very-tightly grouped and again there is usually
a few seconds gap surrounding these messages. Should I be worried about
this?

Oct 23 19:15:19 Senta systemd[2303]: Stopping Default.
Oct 23 19:15:19 Senta systemd[2303]: Stopped target Default.
Oct 23 19:15:19 Senta systemd[2303]: Stopping Basic System.
Oct 23 19:15:19 Senta systemd[2303]: Stopped target Basic System.
Oct 23 19:15:19 Senta systemd[2303]: Stopping Paths.
Oct 23 19:15:19 Senta systemd[2303]: Stopped target Paths.
Oct 23 19:15:19 Senta systemd[2303]: Stopping Timers.
Oct 23 19:15:19 Senta systemd[2303]: Stopped target Timers.
Oct 23 19:15:19 Senta systemd[2303]: Stopping Sockets.
Oct 23 19:15:19 Senta systemd[2303]: Stopped target Sockets.
Oct 23 19:15:19 Senta systemd[2303]: Starting Shutdown.
Oct 23 19:15:19 Senta systemd[2303]: Reached target Shutdown.
Oct 23 19:15:19 Senta systemd[2303]: Starting Exit the Session...
Oct 23 19:15:19 Senta systemd[2449]: Failed at step CHDIR spawning
/bin/kill: No such file or directory
Oct 23 19:15:19 Senta systemd[2303]: systemd-exit.service: main process
exited, code=exited, status=200/CHDIR
Oct 23 19:15:19 Senta systemd[2303]: Failed to start Exit the Session.
Oct 23 19:15:19 Senta systemd[2303]: Dependency failed for Exit the Session.
Oct 23 19:15:19 Senta systemd[2303]: Unit systemd-exit.service entered
failed state.


Thanks!



Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: