mirror of
https://salsa.debian.org/kernel-team/initramfs-tools.git
synced 2026-01-26 15:39:08 +00:00
03d196f7c6
The qemu tests are somehow taking 10 more seconds than usual between
running systemd-udevd and discovering virtio-blk devices, which causes
the qemu-panic-shell test to exceed the timeout and error out:
[ 12.693906] Run /init as init process
Loading, please wait...
Starting systemd-udevd version 256~rc3-2
[ 20.470569] virtio_blk virtio3: 1/0/0 default/read/poll queues
[ 20.715954] virtio_blk virtio3: [vda] 556 512-byte logical blocks (285 kB/278 KiB)
Begin: Loading essential drivers ... [ 22.057615] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input2
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.
Begin: Running /scripts/local-block ... done.
[...]
qemu-system-amd64: terminating on signal 15 from pid 17745 (timeout)
Increase the timeout to 120s, so the qemu-panic-shell test can continue
long enough to print the emergency shell the test is looking for. S390X
also has a 120s timeout, so fold that into the new default case as well.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
initramfs-tools =============== The Linux kernel may boot using an "initramfs", an archive of files that it unpacks into an in-memory file system at the beginning of the boot process. This archive must contain its own init program which the kernel will run as the first user process. In a Debian system, the initramfs is responsible for: * Loading essential driver modules * Setting up a network connection, if required * Setting up layered storage devices, if required * Resuming from hibernation (suspend-to-disk), if possible * Checking and mounting the root and /usr file systems * Handing over to the main init system initramfs-tools is designed to be extensible, and many other packages provide these and additional features in the initramfs. On x86 systems, the initramfs can also contain CPU microcode updates that the kernel will apply at a very early stage. These are provided by the (non-free) intel-microcode and amd64-microcode packages. Debian's official kernel packages require the use of an initramfs, since drivers and filesystem code are built as modules that need to be loaded before the file systems can be mounted. Custom kernel packages that have this code built-in may still need an initramfs to set up layered storage devices or to provide microcode updates. If initramfs-tools is installed, it will generate an initramfs automatically whenever a kernel is installed or upgraded (and remove it when the kernel is removed). If only initramfs-tools-core is installed, you can run mkinitramfs to generate an initramfs. The initramfs-tools(7) manual page documents the supported parameters and how to extend initramfs-tools. There are additional manual pages for the various commands and configuration files.