systemd-shutdown hangs on Powering off after updating to Kernel 4.4.1

English Install/Boot/Login
1

After I updated my TUMBLEWEED system to kernel 4.4.1 the machine will not power off. Below you can find the last lines of the journal:


Feb 25 14:43:02 nb audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=42949672
Feb 25 14:43:02 nb systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Feb 25 14:43:02 nb kernel: audit: type=1131 audit(1456407782.425:247): pid=1 uid=0
Feb 25 14:43:02 nb systemd[1]: Unmounting /run/user/1000...
Feb 25 14:43:02 nb systemd[1]: Unmounting Runtime Directory...
Feb 25 14:43:02 nb umount[2327]: umount: /var/run: target is busy
Feb 25 14:43:02 nb umount[2327]: (In some cases useful info about processes that
Feb 25 14:43:02 nb umount[2327]: use the device is found by lsof(8) or fuser(1).)
Feb 25 14:43:02 nb systemd[1]: var-run.mount: Mount process exited, code=exited st
Feb 25 14:43:02 nb systemd[1]: Failed unmounting Runtime Directory.
Feb 25 14:43:02 nb systemd[1]: Unmounted /run/user/1000.
Feb 25 14:43:02 nb systemd[1]: Reached target Unmount All Filesystems.
Feb 25 14:43:02 nb systemd[1]: Stopped target Local File Systems (Pre).
Feb 25 14:43:02 nb systemd[1]: Stopped Create Static Device Nodes in /dev.
Feb 25 14:43:02 nb audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=42949672
Feb 25 14:43:02 nb systemd[1]: Stopped Remount Root and Kernel File Systems.
Feb 25 14:43:02 nb audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=42949672
Feb 25 14:43:02 nb kernel: audit: type=1131 audit(1456407782.469:248): pid=1 uid=0
Feb 25 14:43:02 nb kernel: audit: type=1131 audit(1456407782.473:249): pid=1 uid=0
Feb 25 14:43:02 nb systemd[1]: Reached target Shutdown.
Feb 25 14:43:02 nb systemd[1]: Starting /etc/init.d/halt.local Compatibility...
Feb 25 14:43:02 nb systemd[1]: Started /etc/init.d/halt.local Compatibility.
Feb 25 14:43:02 nb audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967
Feb 25 14:43:02 nb kernel: audit: type=1130 audit(1456407782.485:250): pid=1 uid=0
Feb 25 14:43:02 nb systemd[1]: Reached target Final Step.
Feb 25 14:43:02 nb systemd[1]: Starting Power-Off...
Feb 25 14:43:02 nb systemd[1]: Shutting down.
Feb 25 14:43:02 nb systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Feb 25 14:43:02 nb systemd-journald[406]: Journal stopped

Any help is highly appreciated.

Before upgrading to kernel 4.4 this problem did not exisit.

2

On my ASUS-Laptop (openSUSE 42.1, Kernel 4.4.2) i have a similar problem which is caused by a known bug : https://patchwork.ozlabs.org/patch/552082/.

I did not apply the proposed patch but blacklisted “asus_laptop” in “/etc/modprobe.d/50-blacklist.conf” and rebuild my initrd. Now my laptop shuts down correctly again.

Best regards

susejunky

3

This solved my problem as well since I also have an ASUS laptop. Nevertheless I am wondering what purpose of the “asus_laptop” module has. Does anybody have any idea? If I blacklist it will I have to expect any other issues?

Thank you very much again for your help

Best Regards

4

Sorry, I can’t really help with that. I blacklisted the module several weeks ago and so far have discovered no problems.

Best regards

susejunky

5

It porvides support for such things like special hotkeys, brightness, led, rfkill on ASUS laptops.

6

Has the “asus_laptop” module been introduce only in kernel 4.4 or did it also exist in earlier versions?

7

It existed for the past 7 years at least. It does not mean there are no changes though.

8

I see. Obviously some kind of bug crept in in the kernel 4.4 module. Let me know if there is anything i can help with to find out more about the bug. I could do further test on my ASUS laptop if that would be of any help.

9

From the information provided in the link (in my first post) i understand that the problem is already solved but not in the update repositories yet.

You should be able to apply the solution to your kernel sources and re-compile your kernel. I didn’t try that, because my notebook is quite old and it takes very long to compile the kernel.

Best regards

susejunky

10

I will try that and inform here about the outcome.

Thank you very much again for your help

11

I just upgraded to kernel 4.4.2 and it seems that the patch has been included in the repository. In this case I don’t have to compile a new kernel.

Thank you very much