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 . <fzacaria...@gmail.com> 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 @ 40000 KHz), (N/A, > 2000 mBm), (N/A) > [ 6792.177896] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, > 2000 mBm), (N/A) > [ 6792.177898] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, > 2000 mBm), (N/A) > [ 6792.177900] cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, > 2000 mBm), (N/A) > [ 6792.177902] cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, > 2000 mBm), (0 s) > [ 6792.177904] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, > 2000 mBm), (0 s) > [ 6792.177906] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, > 2000 mBm), (N/A) > [ 6792.177908] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 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 >