All my 3 systems (all using stable repos) were updated to the new versions of systemd and kernel. Two of my systems updated fine with only systemd-resolved.service and systemd-timesyncd.service units showed up as failed, but no other issues that I can tell.

The third system, which is a Dell Lattitude E6540 laptop, had some rather severe issues. On boot, I'd see a timer going off for 1 minutes while systemd tried to mount home and linux swap partitions, but it eventually failed most of the time. journalctl -xb or systemctl --failed didn't show any abnormal messages. I did make sure the filesystems were clean and I was able to mount the /home partition when I booted using live KaOS USB drive (used 2015.05 version). There were never any issues mounting the root partition, which is on the same drive as home and swap. Also, this failed-to-mount behavior wasn't very consistent either; once in a while (1 out of 6 or 7 attempts) the home and swap partitions did get mounted, but then it didn't recognize my wifi adapter (Qualcomm Atheros AR9485), so no network connectivity. In the end I ended up rolling back to Linux 3.19 and systemd 218. Now my system is back to normal.

Did anyone else have any issues with the latest kernel and systemd?

inxi output:

System: Host: td-linux Kernel: 3.19.4-1 x86_64 (64 bit) Desktop: N/A Distro: KaOS rolling

Machine: System: Dell product: Latitude E6540 v: 01 serial: D0TJYZ1

Mobo: Dell model: 0725FP v: A00 serial: /D0TJYZ1/CN1296344O0221/ Bios: Dell v: A08 date: 02/18/2014

CPU: Quad core Intel Core i7-4800MQ (-HT-MCP-) cache: 6144 KB

clock speeds: max: 3700 MHz 1: 3646 MHz 2: 3586 MHz 3: 3589 MHz 4: 3647 MHz 5: 3531 MHz 6: 3594 MHz

7: 3574 MHz 8: 3600 MHz

Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller

Card-2: Advanced Micro Devices [AMD/ATI] Mars XTX [Radeon HD 8790M]

Display Server: X.org 1.16.4 driver: intel tty size: 210x52 Advanced Data: N/A for root

Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller driver: snd_hda_intel

Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel

Sound: Advanced Linux Sound Architecture v: k3.19.4-1

Network: Card-1: Intel Ethernet Connection I217-LM driver: e1000e

IF: eno1 state: down mac: ec:f4:bb:28:f6:1d

Card-2: Qualcomm Atheros AR9485 Wireless Network Adapter driver: ath9k

IF: wlp3s0 state: up mac: b8:ee:65:18:24:6f

Drives: HDD Total Size: 620.1GB (12.4% used) ID-1: /dev/sda model: ST500LM000 size: 500.1GB

ID-2: /dev/sdb model: SPCC_Solid_State size: 120.0GB

Partition: ID-1: / size: 19G used: 16G (85%) fs: ext4 dev: /dev/sdb1

ID-2: /home size: 84G used: 49G (60%) fs: ext4 dev: /dev/sdb3

ID-3: swap-1 size: 8.19GB used: 0.00GB (0%) fs: swap dev: /dev/sdb2

Sensors: System Temperatures: cpu: 54.0C mobo: 49.0C gpu: 44.0

Fan Speeds (in rpm): cpu: N/A fan-2: 3212

Info: Processes: 205 Uptime: 2:03 Memory: 2342.1/7892.3MB Client: Shell (sudo) inxi: 2.2.23

Since no-one has shown any of these issues, did you check that the update on that system went ok? Was the mirror synced? (yesterday the data-center in LA were the main mirror is was offline for 12 hours)

You might want to reinstall those 2, linux & systemd 220, though systemd 221 seems to have a lot of bug-fixes, maybe your mount issue is one of them. 221 will move to stable in a few days.

Here systemd 220 listed the above mentioned systemd-resolved.service and systemd-timesyncd.service errors, but without harmful consequences.

These errors disappeared with systemd 221.

There are some new ones but also without noticeable harm.

6.817850] systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE

[ 6.818492] systemd[1]: Failed to start Load Kernel Modules.

[ 6.818619] systemd[1]: systemd-modules-load.service: Unit entered failed state.

[ 6.818626] systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

[ 40.571453] QXcbEventReader[518]: segfault at 7f972e327379 ip 00007f972e327379 sp 00007f972b59fd20 error 14 in locale-archive[7f972e3b3000+1c6000]

[ 40.571499] audit: type=1701 audit(1435003455.828:3): auid=1000 uid=1000 gid=100 ses=1 pid=518 comm="QXcbEventReader" exe="/usr/bin/kactivitymanagerd" sig=11

[ 40.572284] audit: type=1701 audit(1435003455.828:4): auid=1000 uid=1000 gid=100 ses=1 pid=501 comm="QXcbEventReader" exe="/usr/bin/kded5" sig=11

[ 51.477994] QXcbEventReader[583]: segfault at 7f16c4eb7379 ip 00007f16c4eb7379 sp 00007f16c2b36ce0 error 14 in locale-archive[7f16c4f43000+1c6000]

Make sure to update the vbox kernel modules (needed on any kernel update or booting into linux-next from linux or vice-versa), those are most probably your errors.

/usr/bin/vboxsetup setup

I think I narrowed down the issue to linux 4+ kernels. I installed systemd-1 from build while retaining 3.19 kernel, and it worked like a charm. I then updated to linux-4.0.5 and on reboot it went back to waiting to mount home and swap partitions. (While installing 4.0.5 kernel this time, I was carefully looking at pacman output but I didn't see any error messages). I then tried linux-next from build (kernel 4.1 released) but same issue of mounting home and swap partitions. I captured output of journalctl -xb after booting both 3.19 and 4.1 kernels. Following messages stood out during 4.1 boot time that didn't appear during 3.19 boot.

Jun 24 16:52:55 td-linux audit[260]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=260 comm="systemd-udevd" exe="/usr/lib/systemd/systemd-udevd" sig=4

Jun 24 16:52:55 td-linux kernel: traps: systemd-udevd[260] trap invalid opcode ip:7f2ca1b95c1a sp:7ffc8860ee48 error:0 in libpthread-2.21.so[7f2ca1b8a000+18000]

Jun 24 16:52:55 td-linux kernel: audit: type=1701 audit(1435179175.916:2): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=260 comm="systemd-udevd" exe="/usr/lib/systemd/systemd-udevd" sig=4

Jun 24 16:52:55 td-linux systemd-udevd[230]: worker [260] terminated by signal 4 (Illegal instruction)

Jun 24 16:52:55 td-linux kernel: microcode: CPU1 sig=0x306c3, pf=0x10, revision=0x17

Jun 24 16:52:55 td-linux kernel: microcode: CPU1 updated to revision 0x1c, date = 2014-07-03

Jun 24 16:52:55 td-linux systemd-udevd[230]: worker [260] failed while handling '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0'

Jun 24 16:52:55 td-linux kernel: microcode: CPU2 sig=0x306c3, pf=0x10, revision=0x17

Jun 24 16:52:55 td-linux kernel: microcode: CPU2 sig=0x306c3, pf=0x10, revision=0x17

Jun 24 16:52:55 td-linux kernel: microcode: CPU2 updated to revision 0x1c, date = 2014-07-03

Jun 24 16:52:55 td-linux kernel: microcode: CPU3 sig=0x306c3, pf=0x10, revision=0x17

Jun 24 16:52:55 td-linux kernel: microcode: CPU3 sig=0x306c3, pf=0x10, revision=0x17

Jun 24 16:52:55 td-linux kernel: traps: systemd-udevd[240] trap invalid opcode ip:7f2ca1b95c1a sp:7ffc8860eef8 error:0 in libpthread-2.21.so[7f2ca1b8a000+18000]

Jun 24 16:52:55 td-linux kernel: audit: type=1701 audit(1435179175.919:3): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=240 comm="systemd-udevd" exe="/usr/lib/systemd/systemd-udevd" sig=4

Jun 24 16:52:55 td-linux kernel: microcode: CPU3 updated to revision 0x1c, date = 2014-07-03

Jun 24 16:52:55 td-linux kernel: traps: systemd-udevd[244] trap invalid opcode ip:7f2ca1b95c1a sp:7ffc8860ee48 error:0 in libpthread-2.21.so[7f2ca1b8a000+18000]

Jun 24 16:52:55 td-linux kernel: audit: type=1701 audit(1435179175.923:4): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=244 comm="systemd-udevd" exe="/usr/lib/systemd/systemd-udevd" sig=4

Jun 24 16:52:55 td-linux audit[240]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=240 comm="systemd-udevd" exe="/usr/lib/systemd/systemd-udevd" sig=4

Jun 24 16:52:55 td-linux audit[244]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=244 comm="systemd-udevd" exe="/usr/lib/systemd/systemd-udevd" sig=4

Jun 24 16:52:55 td-linux kernel: microcode: CPU4 sig=0x306c3, pf=0x10, revision=0x17

Jun 24 16:52:55 td-linux kernel: traps: systemd-udevd[230] trap invalid opcode ip:7f2ca1b95c1a sp:7ffc88611078 error:0 in libpthread-2.21.so[7f2ca1b8a000+18000]

Jun 24 16:52:55 td-linux kernel: audit: type=1701 audit(1435179175.923:5): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=230 comm="systemd-udevd" exe="/usr/lib/systemd/systemd-udevd" sig=4

Jun 24 16:52:55 td-linux audit[230]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=230 comm="systemd-udevd" exe="/usr/lib/systemd/systemd-udevd" sig=4

Jun 24 16:52:55 td-linux systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=4/ILL

Not sure if something got messed up on my installation that manifested on linux-4+ kernels or if this is a regression; but for now I am staying put on 3.19 kernel.

To the last user, @panky, who reported having same issue: Can you share what type system do you have and if you can replicate my findings.

Thanks

A quick google search led me to my twin on the gentoo side of the world. I am going to try the solution and see if that works for me.

This looks not kernel 4 related, but the microcode change.

Could it be your BIOS can't handle newer microcode?

I'll see if I can find a way to have a kernel boot line that disables the microde update.

Could you try if removing the package "intel-ucode" fixes your issue with kernels 4?

Best leave the stable linux 3.19 installed to fall back too, try this with linux-next (4.1)

Yep, removing microcode fixed the mounting of non-root partitions issue.

However, not sure if this is related, but now when KDE boots up, I hear a cracking sound and then sound doesn't work at all. Of course, not having sound is a lot less worse than having a non-bootable laptop. If I switch back to 3.19 kernel, sound comes back. What I can't still understand is, with 3.19 why the same microcode works that 4.1 has heartburn with.

Thanks for providing the quick workaround. I'd still keep the 3.19 around to be able to use sound.

Again, not the kernels, it is a change in the microcode loading that was introduced with the 4.0 builds see:

Removing intel-ucode is not a final solution, it was just a check if my hunch was right.

If you are the only one facing this issue, I'll find a way to stop the microde module from loading & updating in grub/systemd-boot.

If more are faced with this, then another way of updating the microcode has to be found.

Looks like it will as simple as just adding "microcode=0" to the kernel line in grub/systemd-boot

Leave the intel-ucode package installed.

EDIT:

If the above doesn't work, blacklisting might:

modprobe.blacklist=microcode