FS#44098 - [linux] 3.19.1 hangs on boot

Attached to Project: Arch Linux
Opened by abc (Xiflite) - Sunday, 08 March 2015, 15:46 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 08 March 2015, 22:00 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Can not boot Kernel 3.19.1 on a Lenovo T430. Kernel 3.19 works fine. The systemd log is displayed but no switch to any tty possible nor lightdm appears.

Additional info:
3.19.1-1

Log attached.

What is strange in compare to the normal 3.19 log:

- iptable fails.... wtf?
- creating virbr0 not possible

Both immediately works fine when using 3.19
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 08 March 2015, 22:00 GMT
Reason for closing:  Not a bug
Additional comments about closing:  User requested: Layer 8 problem
Comment by abc (Xiflite) - Sunday, 08 March 2015, 15:46 GMT
The log.
   crash.log (107.2 KiB)
Comment by AK (Andreaskem) - Sunday, 08 March 2015, 16:10 GMT
Mär 08 16:12:15 comp1 systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Mär 08 16:12:15 comp1 systemd[1]: Failed to start Load Kernel Modules.
Mär 08 16:12:15 comp1 systemd[1]: Unit systemd-modules-load.service entered failed state.
Mär 08 16:12:15 comp1 systemd[1]: systemd-modules-load.service failed.

These lines are suspicious. What is the output of "systemctl status systemd-modules-load.service"?

Wait, do you even get a chance to type the command? If not, there's rescue.target or emergency.target.
Comment by abc (Xiflite) - Sunday, 08 March 2015, 16:15 GMT
As I wrote above I can not switch to any TTY and though can not do any commands.

But:
I am using dkms with the modules exfat and acpi_call. They are compiled by dkms automatically after each restart and no needed necessarily for booting. At least from 3.9 up to 3.19 I did not had any problems regarding this two modules.
Comment by AK (Andreaskem) - Sunday, 08 March 2015, 16:21 GMT
"systemd.unit=rescue.target" or, if that fails "systemd.unit=emergency.target" on the kernel command line should allow you to boot a minimal environment.
Comment by Dave Reisner (falconindy) - Sunday, 08 March 2015, 16:26 GMT
Looks like a fubar'd upgrade. You're either missing a large number of kernel modules, or the indexes created by depmod are missing/corrupt.

I don't see any evidence that this is specifically related to 3.19.
Comment by abc (Xiflite) - Sunday, 08 March 2015, 16:35 GMT
Just wanted to generate the new kernel again to get more debug infos. This seems to be related:

Kernel 3.19.1.
>>> Updating module dependencies. Please wait ...
depmod: ERROR: failed to load symbols from /lib/modules/3.19.1-1-ARCH/extra/acpi_call.ko: Invalid argument
depmod: ERROR: failed to load symbols from /lib/modules/3.19.1-1-ARCH/kernel/fs/exfat/exfat.ko: Invalid argument
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.19.1-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.19.1-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.RdQcHl/root/lib/modules/3.19.1-1-ARCH/kernel/exfat.ko: Invalid argument
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful


Kernel 3.19:
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.19.0-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.19.0-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
Comment by abc (Xiflite) - Sunday, 08 March 2015, 18:00 GMT
Deleted /usr/lib/modules/3.19.1-1-ARCH and installed the kernel again.
Seems to work now (including iptables).

Loading...