FS#57741 - [systemd] 238.0-1 causes segfault when booting linux-zen 4.15.7-1 and 4.15.6-1
Attached to Project:
Arch Linux
Opened by Geoffrey Host (carbonchauvinist) - Wednesday, 07 March 2018, 15:16 GMT
Last edited by Christian Hesse (eworm) - Friday, 09 March 2018, 13:57 GMT
Opened by Geoffrey Host (carbonchauvinist) - Wednesday, 07 March 2018, 15:16 GMT
Last edited by Christian Hesse (eworm) - Friday, 09 March 2018, 13:57 GMT
|
Details
Description: When upgrading systemd, libsystemd and
systemd-sysvcompat from 237.64-1 to 238.0-1 I'm unable to
boot into the 4.15.7-1 linux-zen kernel. Prior to the LUKS
passphrase prompt, I receive the following segfault and hard
freeze (transcribed):
[code] systemd[1]: segfault at 56347c000000 ip 000072f24d0e9d933 sp 00007ffe4da249d0 error 4 in libc.so.6[7f24d0e1booo+1ae000] systemd[1]: caught <SEGV>, dumped core as pid 119 systemd[1]: freezing execution [/code] Downgrading the linux-zen kernel from 4.15.7-1 to 4.15.6-1 had no effect. Similarly, switching from a systemd initramfs to a busybox only delayed the onset of the segfault; I was then able to enter the LUKS passphrase at least - but received the same segfault immediately after. My system is as follows: Dell Precision 5510, i5-6440HQ, Intel HD 530 May be of import to note that I'm able to boot my other kernels (mainline, lts, stock 'linux') without issue with systemd, libsystemd and systemd-sysvcompat at 238.0-1. Additionally, when downgrading systemd, libsystemd and systemd-sysvcompat to 237.64-1 I am able to boot linux-zen successfully (both 4.15.7-1 and 4.15.6-1). Additional info: * package version(s) * config and/or log files etc. [code] $ pacman -Q glibc systemd systemd-sysvcompat libsystemd linux-zen glibc 2.26-11 systemd 238.0-1 systemd-sysvcompat 238.0-1 libsystemd 238.0-1 linux-zen 4.15.7-1 [/code] Steps to reproduce: 1. Have linux-zen kernel installed 2. Upgrade libsystemd, systemd and systemd-sysvcompat to version 238.0-1 |
This task depends upon
Closed by Christian Hesse (eworm)
Friday, 09 March 2018, 13:57 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 238.0-3
Friday, 09 March 2018, 13:57 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 238.0-3
I would also add that when booting with linux or linux-lts and systemd-238.0-1, the laptop works ok but when I issue the poweroff/reboot/halt command I get errors related to umounting /oldroot. Sorry, I don't have the exact messages but they appear each and every time the laptop is halted, rebooted or powered-off.
Going back to systemd 237.64-1 make these errors disappear.
Stopping Mointoring of LVM2 mirros, snapshots etc. using dmeventd or polling...
sd-umoun[2013]: Failed to unmount /oldroot: Device or resource busy
shutdown[1]: Unmounting '/oldroot' failed abnormally, child process 2013 aborted or exited non-zero
sd-remount[2018]: Failed to remount '/oldroot/sys/fs/cgroup/memory' read-only: Device or resource busy
shutdown[1]: Remounting '/oldroot/sys/fs/cgroup/memory' failed abnormally, child process 2018 aborted or exited non-zero
....
repeats for following /oldroot/sys/fs/cgroup/memory, /oldroot/sys/fs/cgroup/pids, /oldroot/sys/fs/cgroup/devices, /oldroot/sys/fs/cgroup/systemd
Seems to be related to following, not sure of relevance to this possible issue, apologies if I'm muddying the waters:
https://github.com/systemd/systemd/issues/8155
Booting with systemd.unified_cgroup_hierarchy works.