Pointer needed for systemd / boot sequence debugging

English Install/Boot/Login
1

Hi everybody,

I’ve been using Tumbleweed for years now with great success. Nevertheless I had a severe problem with my laptop (XPS13) not booting after an update performed with YAST/“Install Software” beginning last week (i run updates regularly every 2-3 days), when my encrypted disk was not unlocked anymore during boot (Bug reports: see https://bugzilla.opensuse.org/show_bug.cgi?id=904987 and https://bugzilla.opensuse.org/show_bug.cgi?id=1024240).
As noted in the former report, I am back to being able to boot my system, but only to rescue.target or multi-user.target, whereas booting straight to graphical.target does not bing up X, but hangs after “Switching to root”. At that point, I can not switch to any other console to perform a login (also no login prompt is given), but the notebook has not crashed as it reacts to a ctrl-alt-del with rebooting.
But if I boot into multi-user.target, login and then

systemctl isolate graphical.target

, X comes up and is seemingly fully functional, though I have to restart NetworkManager to get networking resp. the Plasma applet connected to NM.

What I am looking for is some clues at which point the boot sequence to multi-user.target versus graphical.target differs and what my cause the unsuccessfull boot sequence. I checked


Failed boot to graphical.target:

journalctl -b -1 -p warn

-- Logs begin at Tue 2016-12-06 18:53:21 CET, end at Thu 2017-02-09 12:17:29 CET. --                                                                         
Feb 09 12:10:20 GreyHound kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED                                                                
Feb 09 12:10:20 GreyHound kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'                                                                       
Feb 09 12:10:20 GreyHound kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)                                                           
Feb 09 12:10:20 GreyHound kernel: i8042: Warning: Keylock active                                                                                             
Feb 09 12:10:20 GreyHound kernel: intel_pmc_core: probe of 0000:00:1f.2 failed with error -22                                                                
Feb 09 12:10:20 GreyHound kernel: usb: port power management may be unreliable                                                                               
Feb 09 12:10:41 GreyHound kernel: systemd: 19 output lines suppressed due to ratelimiting                                                                    
Feb 09 12:10:41 GreyHound systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped                                                         
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found ordering cycle on dracut-pre-mount.service/start                                       
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found dependency on dracut-initqueue.service/start                                           
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found dependency on systemd-udev-trigger.service/start                                       
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found dependency on dracut-pre-trigger.service/start                                         
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found dependency on systemd-udevd.service/start                                              
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found dependency on systemd-tmpfiles-setup-dev.service/start                                 
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found dependency on systemd-sysusers.service/start                                           
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found dependency on systemd-firstboot.service/start
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found dependency on systemd-remount-fs.service/start
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found dependency on systemd-fsck-root.service/stop
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Found dependency on dracut-pre-mount.service/start
Feb 09 12:10:41 GreyHound systemd[1]: dracut-pre-mount.service: Breaking ordering cycle by deleting job dracut-initqueue.service/start
Feb 09 12:10:41 GreyHound systemd[1]: dracut-initqueue.service: Job dracut-initqueue.service/start deleted to break ordering cycle starting with dracut-pre-mount.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found ordering cycle on cryptsetup.target/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on lvm2-activation-early.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on systemd-udev-settle.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on systemd-udev-trigger.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on dracut-pre-trigger.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on systemd-udevd.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on systemd-tmpfiles-setup-dev.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on systemd-sysusers.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on systemd-firstboot.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on systemd-remount-fs.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on systemd-fsck-root.service/stop
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on dracut-pre-mount.service/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start
Feb 09 12:10:41 GreyHound systemd[1]: cryptsetup.target: Breaking ordering cycle by deleting job lvm2-activation-early.service/start
Feb 09 12:10:41 GreyHound systemd[1]: lvm2-activation-early.service: Job lvm2-activation-early.service/start deleted to break ordering cycle starting with cryptsetup.target/start
Feb 09 12:10:41 GreyHound kernel: Setting dangerous option enable_psr - tainting kernel
Feb 09 12:10:42 GreyHound kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 09 12:10:42 GreyHound kernel: ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:3a:00.0.bin failed with error -2
Feb 09 12:10:42 GreyHound kernel: ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-0000:3a:00.0.bin failed with error -2
Feb 09 12:10:42 GreyHound kernel: ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
Feb 09 12:10:42 GreyHound kernel: ath10k_pci 0000:3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
Feb 09 12:10:42 GreyHound bluetoothd[1309]: Failed to obtain handles for "Service Changed" characteristic
Feb 09 12:10:42 GreyHound bluetoothd[1309]: Sap driver initialization failed.
Feb 09 12:10:42 GreyHound bluetoothd[1309]: sap-server: Operation not permitted (1)

Shutdown initiated with ctrl-alt-del:

Feb 09 12:11:11 GreyHound systemd[1]: Failed to propagate agent release message: Connection reset by peer
Feb 09 12:11:11 GreyHound systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected
Feb 09 12:11:11 GreyHound systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected
Feb 09 12:11:11 GreyHound systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected
Feb 09 12:11:12 GreyHound systemd[1]: Failed unmounting /var/log.
Feb 09 12:11:16 GreyHound systemd-cryptsetup[1356]: Failed to deactivate: Device or resource busy
Feb 09 12:11:16 GreyHound systemd[1]: systemd-cryptsetup@luks\x2d7b286aff\x2d95ab\x2d4c84\x2d83e3\x2d32a39a805d67.service: Failed with result 'exit-code'.
Feb 09 12:11:16 GreyHound kernel: watchdog: watchdog0: watchdog did not stop!

without any problems obvious to me, though I wonder what these “… found dependency…” and “…break ordering cycle…” warnings mean.

Thanks a lot for any help,

Joost

2

The way I interpret the log you posted…

There is likely a kernel problem related to your Intel CPU, and the first result of that is your networking isn’t starting up properly at first.

This then caused a domino effect where systemd wants to continue to boot, starting services and mounting your encrypted partition in a particular order, the normal sequence is broken due to your initial problem, but booting is still continuing.

It’s then not surprising that your boot might end at multi-target, which <all> boots must successfully reach before optionally proceeding to boot to graphical.target.

So,
I’m going to guess that your immediate problem should be solved simply by booting to an older kernel (You should be able to do so when your GRUB menu displays).

Googling that first error (assuming you’ve posted the entire relevant log, you’re not missing anything before) “intel_pmc_core: probe of 0000:00:1f.2 failed with error -22” returns a few <very> recent hits starting in Nov 2016, so this is likely already being looked at upstream, but you might still submit a bug to https://bugzilla.opensuse.org.

Be sure to include your log file, your <exact> Intel CPU and your kernel version

uname -a

TSU