Bug#770090: systemd: systemctl poweroff doesn't poweroff
Hi again,
I got the updated to 215-8 (latest version in jessie) but the problem still
persists.
Note that if I switch back to sysvinit (by installing sysvinit-core), my
system powers off properly so this is definitely a problem related to
systemd.
I also noticed that very few times, the system poweroff properly, so this
looks like some kind or race-condition. Do you know of a way to debug
systemd's poweroff procedure? Right now, I have no idea what it is doing
because the screen turns black right after I execute the poweroff command.
Is there a way for systemd to write a detailed log of what it's doing?
Regarding the kexec question, I have no kexec packages installed.
On Mon, Dec 15, 2014 at 8:27 PM, Francesc Zacarias
wrote:
> On 12/10/2014 08:59 PM, fzacarias3k . wrote:
>
> I use poweroff.
> Den 10 dec 2014 20:43 skrev "Andrei POPESCU" :
>
>> On Mi, 10 dec 14, 20:11:14, fzacaria...@gmail.com wrote:
>> > Package: systemd
>> > Version: 215-7
>> > Followup-For: Bug #770090
>> >
>> > Dear Maintainer,
>> >
>> > I'm having a similar issue. My laptop halts, but does not poweroff. I
>> > have to keep the hardware power button pressed for a few seconds for the
>> > host to successfully poweroff. This was not the case before.
>> > I haven't modified anything on systemd's config.
>> > I'm running a slightly newer version than the original post but the
>> > problem still persits.
>> > Also, replying to the question from the last message, I don't have any
>> > kexec* packages installed.
>> >
>> > Is there any other info I can provide to help?
>>
>> What command are you using, 'halt' or 'poweroff'? Please mind 'halt' is
>> not supposed to power off your system, unless you add -p.
>>
>> Kind regards,
>> Andrei
>> --
>> http://wiki.debian.org/FAQsFromDebianUser
>> Offtopic discussions among Debian users and developers:
>> http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
>> http://nuvreauspam.ro/gpg-transition.txt
>>
>
> Sorry for the delay.
> Unfortuantely, if I try to install systemd from experimental, apt will
> break my laptop's setup:
>
> The following NEW packages will be installed:
> sysvinit-core{a}
> The following packages will be REMOVED:
> colord{a} dns-root-data{u} dnsmasq-base{u} gvfs{a} gvfs-daemons{a}
> hplip{a} libmbim-glib4{u} libmbim-proxy{u} libmm-glib0{u}
> libmnl0{u} libndp0{u} libnetfilter-conntrack3{u} libnm-glib-vpn1{u}
> libnm-glib4{u} libnm-gtk-common{u} libnm-gtk0{u}
> libnm-util2{u} libpam-systemd{a} libqmi-glib1{u} libqmi-proxy{u}
> libteamdctl0{u} mobile-broadband-provider-info{u}
> modemmanager{u} network-manager{a} network-manager-gnome{a}
> policykit-1{a} policykit-1-gnome{a} printer-driver-postscript-hp{a}
> systemd{a} systemd-sysv{a} udisks2{a}
>
Bug#770090: systemd: systemctl poweroff doesn't poweroff
Hi again, I've found this site and followed the steps to try to debug the problem: http://freedesktop.org/wiki/Software/systemd/Debugging/ This is the output of dmesg during shutdown: [ 6792.054805] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 6792.068552] cfg80211: Calling CRDA to update world regulatory domain [ 6792.102857] systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE [ 6792.103138] systemd[1]: Unit lightdm.service entered failed state. [ 6792.177885] cfg80211: World regulatory domain updated: [ 6792.177889] cfg80211: DFS Master region: unset [ 6792.177891] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 6792.177893] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 6792.177896] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 6792.177898] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) [ 6792.177900] cfg80211: (517 KHz - 525 KHz @ 16 KHz), (N/A, 2000 mBm), (N/A) [ 6792.177902] cfg80211: (525 KHz - 533 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 6792.177904] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 6792.177906] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [ 6792.177908] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [ 6792.178140] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 6792.576545] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 6797.460556] systemd[1]: systemd-cryptsetup@sda2_crypt.service: control process exited, code=exited status=1 [ 6797.461659] systemd[1]: Unit systemd-cryptsetup@sda2_crypt.service entered failed state. [ 6797.470527] systemd[1]: Shutting down. [ 6797.505107] watchdog watchdog0: watchdog did not stop! [ 6797.557957] systemd-journald[239]: Received SIGTERM from PID 1 (systemd-shutdow). [ 6797.953759] EXT4-fs (dm-3): re-mounted. Opts: (null) [ 6797.962966] EXT4-fs (dm-3): re-mounted. Opts: (null) [ 6797.962971] EXT4-fs (dm-3): re-mounted. Opts: (null) [ 6797.984081] systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy [ 6797.984258] systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy [ 6798.060431] EXT4-fs (dm-3): re-mounted. Opts: (null) /dev/dm-0 is my encrypted partition, which contains my root, home and swap file-systems (lvm). I'm using Debian's default full-disk encryption scheme. systemd-cryptsetup@sda2_crypt.service is an auto-generated .service file which just invokes this on service stop: /lib/systemd/systemd-cryptsetup detach 'sda2_crypt' According to systemd's source, that command should print some error messages: https://github.com/systemd/systemd/blob/b9e616cc2256501f484f138999ec63a0094f5c4f/src/cryptsetup/cryptsetup.c But I don't see any of those on my dmesg log, even though I enabled debug output in systemd via kernel params: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 Any ideas about what else I could try to debug further? Kind regards, Francesc
Bug#770090: systemd: systemctl poweroff doesn't poweroff
Hi, Any updates on this issue? I tried to naively* backport systemd 219 from experimental but tests fail. Anything else I could try? * by naively I mean: $ apt-get build-dep systemd/experimental $ apt-get source systemd/experimental $ cd systemd/systemd-219 $ debuild -us -uc On Sat, Jan 17, 2015 at 11:01 PM, fzacarias3k . wrote: > Hi again, > > I've found this site and followed the steps to try to debug the problem: > http://freedesktop.org/wiki/Software/systemd/Debugging/ > > This is the output of dmesg during shutdown: > [ 6792.054805] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local > choice (Reason: 3=DEAUTH_LEAVING) > [ 6792.068552] cfg80211: Calling CRDA to update world regulatory domain > [ 6792.102857] systemd[1]: lightdm.service: main process exited, > code=exited, status=1/FAILURE > [ 6792.103138] systemd[1]: Unit lightdm.service entered failed state. > [ 6792.177885] cfg80211: World regulatory domain updated: > [ 6792.177889] cfg80211: DFS Master region: unset > [ 6792.177891] cfg80211: (start_freq - end_freq @ bandwidth), > (max_antenna_gain, max_eirp), (dfs_cac_time) > [ 6792.177893] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, > 2000 mBm), (N/A) > [ 6792.177896] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, > 2000 mBm), (N/A) > [ 6792.177898] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, > 2000 mBm), (N/A) > [ 6792.177900] cfg80211: (517 KHz - 525 KHz @ 16 KHz), (N/A, > 2000 mBm), (N/A) > [ 6792.177902] cfg80211: (525 KHz - 533 KHz @ 16 KHz), (N/A, > 2000 mBm), (0 s) > [ 6792.177904] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, > 2000 mBm), (0 s) > [ 6792.177906] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, > 2000 mBm), (N/A) > [ 6792.177908] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), > (N/A, 0 mBm), (N/A) > [ 6792.178140] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 6792.576545] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > [ 6797.460556] systemd[1]: systemd-cryptsetup@sda2_crypt.service: control > process exited, code=exited status=1 > [ 6797.461659] systemd[1]: Unit systemd-cryptsetup@sda2_crypt.service > entered failed state. > [ 6797.470527] systemd[1]: Shutting down. > [ 6797.505107] watchdog watchdog0: watchdog did not stop! > [ 6797.557957] systemd-journald[239]: Received SIGTERM from PID 1 > (systemd-shutdow). > [ 6797.953759] EXT4-fs (dm-3): re-mounted. Opts: (null) > [ 6797.962966] EXT4-fs (dm-3): re-mounted. Opts: (null) > [ 6797.962971] EXT4-fs (dm-3): re-mounted. Opts: (null) > [ 6797.984081] systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device > or resource busy > [ 6797.984258] systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device > or resource busy > [ 6798.060431] EXT4-fs (dm-3): re-mounted. Opts: (null) > > /dev/dm-0 is my encrypted partition, which contains my root, home and swap > file-systems (lvm). I'm using Debian's default full-disk encryption scheme. > > systemd-cryptsetup@sda2_crypt.service is an auto-generated .service file > which just invokes this on service stop: > /lib/systemd/systemd-cryptsetup detach 'sda2_crypt' > > According to systemd's source, that command should print some error > messages: > > https://github.com/systemd/systemd/blob/b9e616cc2256501f484f138999ec63a0094f5c4f/src/cryptsetup/cryptsetup.c > > But I don't see any of those on my dmesg log, even though I enabled debug > output in systemd via kernel params: > systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 > > Any ideas about what else I could try to debug further? > > Kind regards, > Francesc >
Bug#770090: systemd: systemctl poweroff doesn't poweroff
I use poweroff. Den 10 dec 2014 20:43 skrev "Andrei POPESCU" : > On Mi, 10 dec 14, 20:11:14, fzacaria...@gmail.com wrote: > > Package: systemd > > Version: 215-7 > > Followup-For: Bug #770090 > > > > Dear Maintainer, > > > > I'm having a similar issue. My laptop halts, but does not poweroff. I > > have to keep the hardware power button pressed for a few seconds for the > > host to successfully poweroff. This was not the case before. > > I haven't modified anything on systemd's config. > > I'm running a slightly newer version than the original post but the > > problem still persits. > > Also, replying to the question from the last message, I don't have any > > kexec* packages installed. > > > > Is there any other info I can provide to help? > > What command are you using, 'halt' or 'poweroff'? Please mind 'halt' is > not supposed to power off your system, unless you add -p. > > Kind regards, > Andrei > -- > http://wiki.debian.org/FAQsFromDebianUser > Offtopic discussions among Debian users and developers: > http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic > http://nuvreauspam.ro/gpg-transition.txt >
Bug#753345: wpasupplicant hook for pm-utils breaks pm-suspend when used with wicd
Package: wpasupplicant Version: 1.1-1 Severity: important Dear Maintainer, After installing wicd and wpasupplicant, suspending the computer with pm-suspend stops working. The problem lies in the wicd and wpasupplicant installed hooks for pm-utils colliding. wicd's hook runs first and disconnects my wireless device, causing wpa_supplicant process to stop. Then the wpasupplicant's hook runs and tries to execute the suspend command but the hook fails because wpa_cli can't find the control socket (because it was removed by the previous hook!). Extract from /var/log/pm-suspend.log: --- Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: Returned exit code 255. Mon Jun 30 20:03:15 CEST 2014: Inhibit found, will not perform suspend Mon Jun 30 20:03:15 CEST 2014: Running hooks for resume --- This can be reproduced every time. I temporarily fixed it by appending "exit 0" to wpasupplicant's hook. Better solutions might be: * run this hook before wicd's * verify wpa_supplicant's control socket existance -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wpasupplicant depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.2 ii libc6 2.19-3 ii libdbus-1-3 1.8.4-1 ii libnl-3-200 3.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libpcsclite1 1.8.11-3 ii libreadline6 6.3-6 ii libssl1.0.0 1.0.1h-3 ii lsb-base 4.1+Debian13 wpasupplicant recommends no packages. Versions of packages wpasupplicant suggests: pn libengine-pkcs11-openssl pn wpagui -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
