Arch Linux

p90

Member

Registered: 2013-06-07

Posts: 21

Shutdown Problem on Via C7 Epia SN18000

Hi,

I have a Via Epia SN18000 as router as home.
Two months ago I switched from a old debian installation to arch linux.
Most works pretty good but one thing.
Shutdown does not work or to be more precise, takes a very long time (in the order of 20 minutes)

So I followed this guide: http://freedesktop.org/wiki/Software/sy … eventually and got this

[3970474.541160] systemd[1]: Failed to send unit remove signal for sockets.target: Transport endpoint is not connected
[3970474.541190] systemd[1]: Failed to send unit remove signal for -.slice: Transport endpoint is not connected
[3970474.541222] systemd[1]: Failed to send unit remove signal for systemd-random-seed.service: Transport endpoint is not connected
[3970474.541279] systemd[1]: Failed to send unit remove signal for local-fs-pre.target: Transport endpoint is not connected
[3970474.541309] systemd[1]: Failed to send unit remove signal for systemd-ask-password-console.service: Transport endpoint is not connected
[3970474.541344] systemd[1]: Failed to send unit remove signal for systemd-user-sessions.service: Transport endpoint is not connected
[3970474.541384] systemd[1]: Failed to send unit remove signal for sys-devices-pci0000:00-0000:00:0f.0-ata1-host0-target0:0:0-0:0:0:0-block-sda.device: Tran$
[3970474.556683] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[3970474.563847] systemd-udevd[4325]: Unload module index
[3970474.563890] systemd-udevd[4325]: Unloaded link configuration context.
[3970474.564683] systemd-udevd[4324]: Unload module index
[3970474.564723] systemd-udevd[4324]: Unloaded link configuration context.
[3970474.571906] systemd-journald[83]: Received SIGTERM from PID 1 (systemd-shutdow).
[3970474.571926] systemd-journald[83]: systemd-journald stopped as pid 83
[3970474.576614] systemd-udevd[116]: worker [4324] exit
[3970474.576628] systemd-udevd[116]: worker [4324] cleaned up
[3970474.576658] systemd-udevd[116]: worker [4325] exit
[3970474.576665] systemd-udevd[116]: worker [4325] cleaned up
[3970474.576741] systemd-udevd[116]: Unload module index
[3970474.576765] systemd-udevd[116]: Unloaded link configuration context.
[3970474.896017] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[3970474.908979] systemd-shutdown[1]: Unmounting file systems.
[3970474.910075] systemd-shutdown[1]: Unmounting /dev/hugepages.
[3970474.923068] systemd-shutdown[1]: Unmounting /sys/kernel/config.
[3970474.939727] systemd-shutdown[1]: Unmounting /sys/kernel/debug.
[3970474.959692] systemd-shutdown[1]: Unmounting /dev/mqueue.
[3970475.339050] EXT4-fs (sda1): re-mounted. Opts: (null)
[3970475.402003] EXT4-fs (sda1): re-mounted. Opts: (null)
[3970475.402015] EXT4-fs (sda1): re-mounted. Opts: (null)
[3970475.402046] systemd-shutdown[1]: All filesystems unmounted.
[3970475.402056] systemd-shutdown[1]: Deactivating swaps.
[3970475.402196] systemd-shutdown[1]: All swaps deactivated.
[3970475.402204] systemd-shutdown[1]: Detaching loop devices.
[3970475.403078] systemd-shutdown[1]: All loop devices detached.
[3970475.403091] systemd-shutdown[1]: Detaching DM devices.
[3970475.403221] systemd-shutdown[1]: All DM devices detached.
[3970475.404475] systemd-shutdown[4406]: Spawned /usr/lib/systemd/system-shutdown/debug.sh as 4407.
[3970475.421445] EXT4-fs (sda1): re-mounted. Opts: discard,data=ordered

Which does not seem to help at all.
So my next try was using systemctl poweroff -f which also takes about 20-30 minutes to actually poweroff for some reason.
The system btw is always pingable but ssh is already down.

Last but not least, I tried the magic sysreq way which works.

echo 1 > /proc/sys/kernel/sysrq
echo b > /proc/sysrq-trigger

will force a reboot.

So my question is, does anybody know that is going on here?
My guess is that there is a hanging service somewhere but how do i find and fix it?

With best regards,

p90