Solved: Boot stalls since linux418 4.18.5-1 & 4.19RC1


#1

Hi all,
I just updated my stable GNOME build to the latest stable [Stable Update] 2018-08-31 and since then the 4.18.5-1 kernel won’t boot.
It stalls after printing: starting version 239

Kernel version 4.14.67-1 boots without a problem.

Here’s my system info:

System:    Host: gTux Kernel: 4.14.67-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.0 
           Desktop: Gnome 3.28.3 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Dell product: XPS 15 9550 v: N/A serial: <root required> 
           Mobo: Dell model: 0N7TVV v: A00 serial: <root required> UEFI: Dell v: 1.8.0 date: 07/18/2018 
Battery:   ID-1: BAT0 charge: 16.5 Wh condition: 81.5/84.0 Wh (97%) model: SMP DELL 1P6KD5A 
           status: Charging 
CPU:       Topology: Quad Core model: Intel Core i7-6700HQ bits: 64 type: MT MCP arch: Skylake-S rev: 3 
           L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 41488 
           Speed: 850 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 870 2: 894 3: 840 4: 839 5: 899 
           6: 895 7: 840 8: 842 
Graphics:  Device-1: Intel HD Graphics 530 driver: i915 v: kernel bus ID: 00:02.0 
           Device-2: NVIDIA GM107M [GeForce GTX 960M] driver: N/A bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.1 driver: intel resolution: 3840x2160~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) v: 4.5 Mesa 18.1.7 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-H HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Sound Server: ALSA v: k4.14.67-1-MANJARO 
Network:   Device-1: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC driver: brcmfmac v: kernel 
           bus ID: 02:00 
           IF: wlp2s0 state: up mac: 60:6d:c7:c6:a7:a5 
           IF-ID-1: virbr0 state: down mac: 52:54:00:60:77:2b 
           IF-ID-2: virbr0-nic state: down mac: 52:54:00:60:77:2b 
Drives:    Local Storage: total: 491.26 GiB used: 133.75 GiB (27.2%) 
           ID-1: /dev/nvme0n1 vendor: Hynix model: PC401 NVMe SK 512GB size: 476.94 GiB 
           ID-2: /dev/sda type: USB vendor: SanDisk model: Ultra USB 3.0 size: 14.32 GiB 
Partition: ID-1: / size: 451.17 GiB used: 131.95 GiB (29.2%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: swap-1 size: 17.04 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 63.5 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 261 Uptime: 11m Memory: 15.49 GiB used: 2.13 GiB (13.7%) Init: systemd Compilers: 
           gcc: 8.2.0 Shell: fish v: 2.7.1 inxi: 3.0.21

mkinitcpio -p linux418 runs also without a problem

Here’s a picture of the screen:


The ACPI errors are kind of a thing with this DELL Notebook and always present, even when running it as a hackintosh.

For now I can not leave 4.14 behind me, but I’d like to for nvidia-xrun sake and gaming with proton :wink:


[Stable Update] 2018-08-31 - Kernels, Mesa, Qemu, Nvidia, Firefox, Python, Haskell
#2

Go to the grub menu and press E for edit. Find the word quiet and remove it. By pressing CTRL+X it will start with that modification and give you more output. What was the last kernel of given series working on your end. We may then find the regression in added patches of the newer point-releases.


#3

I had that removed when I took the picture :thinking:

4.18.5 worked before the stable update from yesterday, 31st of August 2018.


#4

Try to boot with fallback option and if you still can boot with linux414 please check /var/log/pacman.log for the last changes made:

tac /var/log/pacman.log | less


#5

The fallback has the same issue, but linux414 boots. I will post the logs :slight_smile:
Thanks for helping.

EDIT: The command

tac /var/log/pacman.log | less

Yields pages upon pages of install logs, should I copy and past them all?
Installing kernel 419 as well as install and reinstall activity for other packages like nvidia-xrun-git pop up there. Is there a way to be more targeted?

Since 414 runs well - could it be something with the Intel graphics driver?

EDIT2: Just installed and tested 4.17.19-1-MANJARO - This kernel works as well.

This is my boot command:

GRUB_CMDLINE_LINUX_DEFAULT=“i915.enable_guc=3 clocksource=hpet”

I added the clocksoure=hpet because I read in an arch forum that it might help with the stalling for Kernel 4.18+, but it doesn’t.


#6

Copy only the last update, when you updated your kernels.


#7

Alright, here are the logs for the kernel installs:

[2018-09-01 19:15] [ALPM] running 'systemd-update.hook'...
[2018-09-01 19:15] [ALPM-SCRIPTLET] done
[2018-09-01 19:15] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme0n1.
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.14-x86_64
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.17-x86_64-fallback.img
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.17-x86_64.img
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.17-x86_64
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.18-x86_64-fallback.img
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.18-x86_64.img
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.18-x86_64
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.19-x86_64
[2018-09-01 19:15] [ALPM-SCRIPTLET] Found background: /usr/share/grub/background.png
[2018-09-01 19:15] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2018-09-01 19:15] [ALPM] running '99-grub.hook'...
[2018-09-01 19:15] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-09-01 19:15] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.17-x86_64-fallback.img
[2018-09-01 19:15] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-09-01 19:15] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-09-01 19:14] [ALPM-SCRIPTLET] ==> Starting build: 4.17.19-1-MANJARO
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-4.17-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.17-x86_64-fallback.img -S autodetect
[2018-09-01 19:14] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux417.preset: 'fallback'
[2018-09-01 19:14] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-09-01 19:14] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.17-x86_64.img
[2018-09-01 19:14] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-09-01 19:14] [ALPM-SCRIPTLET] ==> Starting build: 4.17.19-1-MANJARO
[2018-09-01 19:14] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-4.17-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.17-x86_64.img
[2018-09-01 19:14] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux417.preset: 'default'
[2018-09-01 19:14] [ALPM] running '90-linux417.hook'...
[2018-09-01 19:14] [ALPM] running '70-dkms-install.hook'...
[2018-09-01 19:14] [ALPM] running '60-linux417.hook'...
[2018-09-01 19:14] [ALPM] transaction completed
[2018-09-01 19:14] [ALPM-SCRIPTLET] In order to use nvidia module, reboot the system.
[2018-09-01 19:14] [ALPM] installed linux417-nvidia (1:396.54-3)
[2018-09-01 19:14] [ALPM] installed linux417-bbswitch (0.8-14)
[2018-09-01 19:14] [ALPM] installed linux417-headers (4.17.19-1)
[2018-09-01 19:14] [ALPM] installed linux417 (4.17.19-1)
[2018-09-01 19:14] [ALPM] transaction started
[2018-09-01 19:14] [PACMAN] Running '/usr/bin/pacman --noconfirm --noprogressbar -S linux417 linux417-headers linux417-bbswitch linux417-nvidia'
[2018-09-01 16:18] [ALPM] running 'systemd-update.hook'...
[2018-09-01 16:18] [ALPM] transaction completed
[2018-09-01 16:18] [ALPM] installed xorg-xdpyinfo (1.3.2-2)
[2018-09-01 16:18] [ALPM] installed libdmx (1.1.4-1)
[2018-09-01 16:18] [ALPM] installed libxxf86dga (1.1.4-2)
[2018-09-01 16:18] [ALPM] transaction started
[2018-09-01 16:18] [PACMAN] Running 'pacman -S --config /etc/pacman.conf -- xorg-xdpyinfo'
[2018-09-01 15:53] [ALPM] running 'systemd-update.hook'...
[2018-09-01 15:53] [ALPM] running 'systemd-daemon-reload.hook'...
[2018-09-01 15:53] [ALPM] transaction completed
[2018-09-01 15:53] [ALPM] removed i8kutils (1.43-3)
[2018-09-01 15:53] [ALPM] transaction started
[2018-09-01 15:52] [PACMAN] Running 'pacman -R --config /etc/pacman.conf -- dell-smm-hwmon.conf'
[2018-09-01 15:52] [PACMAN] Running 'pacman -R --config /etc/pacman.conf -- dell-smm-hwmon.conf'
[2018-09-01 15:52] [PACMAN] Running 'pacman -R --config /etc/pacman.conf -- dell-smm'
[2018-09-01 15:52] [PACMAN] Running 'pacman -R --config /etc/pacman.conf -- dell-smm-hwmon'
[2018-09-01 15:50] [PACMAN] Running 'pacman -S --config /etc/pacman.conf -- mesa'
[2018-09-01 15:49] [ALPM] running 'systemd-update.hook'...
[2018-09-01 15:49] [ALPM] transaction completed
[2018-09-01 15:49] [ALPM] reinstalled xf86-video-intel (1:2.99.917+831+ge7bfc906-1)
[2018-09-01 15:49] [ALPM] transaction started
[2018-09-01 15:49] [PACMAN] Running 'pacman -S --config /etc/pacman.conf -- xf86-video-intel'
[2018-09-01 15:38] [ALPM] running 'systemd-update.hook'...
[2018-09-01 15:38] [ALPM-SCRIPTLET] done
[2018-09-01 15:38] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme0n1.
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.14-x86_64
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.18-x86_64-fallback.img
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.18-x86_64.img
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.18-x86_64
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.19-x86_64
[2018-09-01 15:38] [ALPM-SCRIPTLET] Found background: /usr/share/grub/background.png
[2018-09-01 15:38] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2018-09-01 15:38] [ALPM] running '99-grub.hook'...
[2018-09-01 15:38] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-09-01 15:38] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64-fallback.img
[2018-09-01 15:38] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-09-01 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-09-01 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-09-01 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2018-09-01 15:38] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-09-01 15:37] [ALPM-SCRIPTLET] ==> Starting build: 4.19.0-1-MANJARO
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64-fallback.img -S autodetect
[2018-09-01 15:37] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'fallback'
[2018-09-01 15:37] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-09-01 15:37] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64.img
[2018-09-01 15:37] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-09-01 15:37] [ALPM-SCRIPTLET] ==> Starting build: 4.19.0-1-MANJARO
[2018-09-01 15:37] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64.img
[2018-09-01 15:37] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'default'


#8

You misunderstood.

cat /var/log/pacman.log | grep "2018-09-01"

#9

The result of that command was too big for a post: https://pastebin.com/1p3RSfdf


#10

I am not an expert, but I think you missed sharing some relevant information about your kernels


[2018-09-01 13:47] [ALPM] running '99-grub.hook'...
[2018-09-01 13:47] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2018-09-01 13:47] [ALPM-SCRIPTLET] Found background: /usr/share/grub/background.png
[2018-09-01 13:47] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.18-x86_64
[2018-09-01 13:47] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.18-x86_64.img
[2018-09-01 13:47] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.18-x86_64-fallback.img
[2018-09-01 13:47] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-4.14-x86_64
[2018-09-01 13:47] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
[2018-09-01 13:47] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
[2018-09-01 13:47] [ALPM-SCRIPTLET] /dev/mapper/control: open failed: No such device
[2018-09-01 13:47] [ALPM-SCRIPTLET] Failure to communicate with kernel device-mapper driver.
[2018-09-01 13:47] [ALPM-SCRIPTLET] Check that device-mapper is available in the kernel.
[2018-09-01 13:47] [ALPM-SCRIPTLET] Incompatible libdevmapper 1.02.150 (2018-08-01) and kernel driver (unknown version).
[2018-09-01 13:47] [ALPM-SCRIPTLET] Command failed.
[2018-09-01 13:47] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2018-09-01 13:47] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme0n1.
[2018-09-01 13:47] [ALPM-SCRIPTLET] done
[2018-09-01 13:47] [ALPM] running 'kernel-alive-post.hook'...
[2018-09-01 13:47] [ALPM-SCRIPTLET] ls: cannot access 'backup': No such file or directory
[2018-09-01 13:47] [ALPM-SCRIPTLET]
[2018-09-01 13:47] [ALPM-SCRIPTLET] ==> Warning:
[2018-09-01 13:47] [ALPM-SCRIPTLET]      -> Kernel has been updated. Modules of the current kernel
[2018-09-01 13:47] [ALPM-SCRIPTLET]      -> have been backed up so you can continue to use your
[2018-09-01 13:47] [ALPM-SCRIPTLET]      -> computer. However, the new kernel will only work
[2018-09-01 13:47] [ALPM-SCRIPTLET]      -> at next boot.
[2018-09-01 13:47] [ALPM-SCRIPTLET]    
[2018-09-01 13:47] [ALPM-SCRIPTLET]    
[2018-09-01 13:47] [ALPM] running 'systemd-update.hook'...

[2018-09-01 14:27] [PACMAN] Running 'pacman -S bbswitch'
[2018-09-01 14:27] [ALPM] running 'kernel-alive-pre.hook'...
[2018-09-01 14:27] [ALPM] transaction started
[2018-09-01 14:27] [ALPM] reinstalled linux414-bbswitch (0.8-56)
[2018-09-01 14:27] [ALPM] transaction completed
[2018-09-01 14:27] [ALPM] running '60-linux414.hook'...
[2018-09-01 14:27] [ALPM] running 'kernel-alive-post.hook'...
[2018-09-01 14:27] [ALPM-SCRIPTLET]
[2018-09-01 14:27] [ALPM-SCRIPTLET] ==> Warning:
[2018-09-01 14:27] [ALPM-SCRIPTLET]      -> This computer hasn't been restarted for a while.
[2018-09-01 14:27] [ALPM-SCRIPTLET]      -> You are running an old kernel. In order to use a
[2018-09-01 14:27] [ALPM-SCRIPTLET]      -> new version of the kernel, please restart your
[2018-09-01 14:27] [ALPM-SCRIPTLET]      -> computer as soon as possible.
[2018-09-01 14:27] [ALPM-SCRIPTLET]    
[2018-09-01 14:27] [ALPM-SCRIPTLET]    
[2018-09-01 14:27] [ALPM] running 'systemd-update.hook'...
[2018-09-01 14:35] [PACMAN] Running 'pacman -R kernel-alive'
[2018-09-01 14:35] [ALPM] running 'kernel-alive-remove.hook'...
[2018-09-01 14:35] [ALPM-SCRIPTLET] Failed to disable unit: Unit file linux-modules-cleanup.service does not exist.
[2018-09-01 14:35] [ALPM] transaction started
[2018-09-01 14:35] [ALPM] removed kernel-alive (0.4-1)
[2018-09-01 14:35] [ALPM] transaction completed
[2018-09-01 14:35] [ALPM] running 'systemd-update.hook'...
[2018-09-01 14:35] [PACMAN] Running 'pacman -R kernel-alive'
---  ---
---  ---

[2018-09-01 14:37] [PACMAN] Running 'pacman -R kernel-alive'

Can you describe your adventure with kernel-alive?


#11

I wish I could. I saw it this morning, to my knowledge I never consciously installed it, so I removed it when I saw it was installed…


#12

Then you have to inspect how/when it was installed

cat /var/log/pacman.log | grep "kernel-alive" | head

#13

Same problem here. Just to say Gymnae is not the only one affected with this issue. Kernel 4.14 and 4.17 are running like a charm but 4.18 from the beginning did booting randomised. It’s like the SSD can’t be initialised.


#14
cat /var/log/pacman.log | grep "kernel-alive" | head                                         21:20:20
[2018-08-28 22:43] [ALPM] running 'kernel-alive-pre.hook'...
[2018-08-28 22:44] [ALPM] running 'kernel-alive-post.hook'...
[2018-08-31 10:52] [ALPM] running 'kernel-alive-pre.hook'...
[2018-08-31 10:52] [ALPM] running 'kernel-alive-post.hook'...
[2018-08-31 10:54] [ALPM] running 'kernel-alive-pre.hook'...
[2018-08-31 10:55] [ALPM] running 'kernel-alive-post.hook'...
[2018-08-31 11:14] [ALPM] running 'kernel-alive-pre.hook'...
[2018-08-31 11:14] [ALPM] running 'kernel-alive-post.hook'...
[2018-09-01 00:49] [ALPM] running 'kernel-alive-pre.hook'...
[2018-09-01 00:51] [ALPM] running 'kernel-alive-post.hook'...

My Manjaro adventure started onthe 28th - it’s the date I installed it on my SSD

EDIT: Also, the problems remained after I removed kernel-alive an re-installed 4.18+ kernels

EDIT 2: This is the output from journalctl -b -3 capturing an attempt to boot with the 4.18.5-1 after the problems started. This boot s not successful:
https://pastebin.com/AqDjVHDw


#15

Actually, kernel-alive was not installed, it seems it was included from the start.
Which ISO have you used?


#16

The latest stable GNOME ISO: 17.1.12

I just tried it again, to get a fresh journal entry:
I let it sit for a good minute, to see if maybe it’s just the X server not coming online
https://pastebin.com/AmetXNLU

It might be the X server:

Sep 01 22:50:07 gTux NetworkManager[380]: <info>  [1535835007.1309] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 01 22:50:07 gTux nm-dispatcher[894]: req:2 'connectivity-change': new request (0 scripts)
Sep 01 22:50:07 gTux nm-dispatcher[894]: req:2 'connectivity-change': completed: no scripts
Sep 01 22:51:15 gTux systemd-logind[376]: Power key pressed.
Sep 01 22:51:15 gTux systemd-logind[376]: Powering Off...
Sep 01 22:51:15 gTux systemd-logind[376]: System is powering down.
Sep 01 22:51:15 gTux systemd[1]: Stopping Authorization Manager...

But I’m not seeing any of this on-screen, the last thing I see is starting version <number>


#17

I did not know that. As I checked, it’s not in Xfce or KDE official ISOs.
I guess @oberon has a special taste!! :stuck_out_tongue_winking_eye:
Maybe @Ste74 can understand if the issue has to do with kernel-alive or it is just a coincidence.


#18

I tend to edit my own posts :wink:
So from the journal entries it seems that it boots, but it’s not visible to me. So something with the X server / Intel / Nvidia drivers?
There are the same for all the kernels, I did not change the setting.

EDIT:
I found this striking difference in the log by a successful and a failing boot:

⋊> ~ journalctl -b -0 | grep fbcon                                                                                                              23:05:58
Sep 01 22:51:49 gTux kernel: fbcon: inteldrmfb (fb0) is primary device
⋊> ~ journalctl -b -1 | grep fbcon                                                                                                              23:06:06
Sep 01 22:49:53 gTux /usr/lib/gdm-x-session[492]: modprobe: FATAL: Module fbcon not found in directory /lib/modules/4.18.5-1-MANJARO

#19

I don’t think kernel-alive is the guilty because if don t work simply don’t boot… The module kernel are not present if k-a fail during the boot…
As i know no more report in my side… ( please point me if k-a is the guilty so i can check to solve the issue)…


#20

Sucess!!
This comment helped

[ ](https://bugs.archlinux.org /task/50619#comment150689) Comment by [Victor Trac (victortrac)](https://bugs.archlinux.org /user/18860) - Sunday, 04 September 2016, 18:43 GMT
Doug: I had this issue on my XPS 13 (9350) as well. I managed to fix it by:

  • removing xf86-video-intel
  • removing the intel xorg config in /etc/X11/xorg.conf.d/
  • removing any i915 module options in /etc/modprobe.d/i915.conf (commented out all lines)
  • removing any kernel pararms for i915 in /boot/
  • rebuilding initramfs

I basically followed him, apart from the kernel parameter, so the firmware blob is still loaded.
Now 4.18.5 works :slight_smile: