Package: src:linux Version: 4.19.98-1 Severity: normal Dear Maintainer,
I encountered a problem when upgrading linux-image from 4.0.19-6 to 4.0.19-8 on two odroid xu4 servers. They do not boot anymore when using the vmlinuz-4.19.0-8-armmp image installed on /boot (but they still boot if I use the older vmlinuz-4.19.0-6-armmp). Using a serial console to check the boot process, I get these upon failure: Starting version 241 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. [ 10.468381] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330 [ 10.473603] dma-pl330 3880000.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6 [ 10.503820] dma-pl330 3880000.adma: PM domain MAU will not be powered off Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. ... lots of similar lines removed ... Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=e139ce78-9841-40fe-8823-96a304a09859 does not exist. Dropping to a shell! BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) So I ran the sugested commands: - cat /proc/modules returned absolutely nothing - ls /dev liste reported the following list, where there are no "disk" directory, hence no /dev/disk/by-uuid: apm_bios network_throughput tty40 char null tty41 console port tty42 cpu_dma_latency psaux tty43 fd ptmx tty44 full pts tty45 gpiochip0 random tty46 gpiochip1 snapshot tty47 gpiochip10 stderr tty48 gpiochip11 stdin tty49 gpiochip12 stdout tty5 gpiochip13 tty tty50 gpiochip14 tty0 tty51 gpiochip15 tty1 tty52 gpiochip16 tty10 tty53 gpiochip17 tty11 tty54 gpiochip18 tty12 tty55 gpiochip19 tty13 tty56 gpiochip2 tty14 tty57 gpiochip20 tty15 tty58 gpiochip21 tty16 tty59 gpiochip22 tty17 tty6 gpiochip23 tty18 tty60 gpiochip24 tty19 tty61 gpiochip25 tty2 tty62 gpiochip26 tty20 tty63 gpiochip27 tty21 tty7 gpiochip28 tty22 tty8 gpiochip29 tty23 tty9 gpiochip3 tty24 ttyS0 gpiochip30 tty25 ttyS1 gpiochip31 tty26 ttyS2 gpiochip32 tty27 ttyS3 gpiochip33 tty28 ttySAC0 gpiochip34 tty29 ttySAC1 gpiochip35 tty3 ttySAC2 gpiochip4 tty30 ttySAC3 gpiochip5 tty31 urandom gpiochip6 tty32 vcs gpiochip7 tty33 vcs1 gpiochip8 tty34 vcsa gpiochip9 tty35 vcsa1 input tty36 vcsu kmsg tty37 vcsu1 mem tty38 vga_arbiter memory_bandwidth tty39 zero network_latency tty4 - cat /proc/cmdline output was: console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes net.ifnames=0 smsc95xx.macaddr=00:1e:06:61:7a:39 This commandline comes from the uboot and is the one I epxected, and the one that works with previous kernel image. This command line looks for the rootfs using its UUID. The previous kernel image found the rootfs directly, but the new kernel image does not find it anymore. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information Hardware : SAMSUNG EXYNOS (Flattened Device Tree) Revision : 0000 Device Tree model: Hardkernel Odroid XU4 ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.19.0-6-armmp (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-8-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod 26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-8-armmp recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-4.19.0-8-armmp suggests: pn debian-kernel-handbook <none> pn linux-doc-4.19 <none> Versions of packages linux-image-4.19.0-8-armmp is related to: pn firmware-amd-graphics <none> pn firmware-atheros <none> pn firmware-bnx2 <none> pn firmware-bnx2x <none> pn firmware-brcm80211 <none> pn firmware-cavium <none> pn firmware-intel-sound <none> pn firmware-intelwimax <none> pn firmware-ipw2x00 <none> pn firmware-ivtv <none> pn firmware-iwlwifi <none> pn firmware-libertas <none> pn firmware-linux-nonfree <none> pn firmware-misc-nonfree <none> pn firmware-myricom <none> pn firmware-netxen <none> pn firmware-qlogic <none> pn firmware-realtek <none> pn firmware-samsung <none> pn firmware-siano <none> pn firmware-ti-connectivity <none> pn xen-hypervisor <none> -- no debconf information