Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #89386
| From | Lloyd <ng2d68@proton.me> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#1116125: linux-image-amd64: system booted into emergency mode after upgrade to 6.12.48 |
| Date | 2025-09-24 06:20 +0200 |
| Message-ID | <Lyp8Z-8kn-7@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Package: linux-image-amd64 Version: 6.12.48-1 Severity: normal Upgraded the kernel from linux-image-6.12.43+deb13-amd64 to linux-image-6.12.48+deb13-amd64 via apt. On reboot into the new kernel, system was unreachable via SSH. Upon checking the console, the system entered emergency mode awaiting password to enter the emergency shell. Rebooting did not clear the fault. Upon checking further, the system could not mount two file systems, /boot and /boot/efi, which are both stored on onboard eMMC. All other FS are stored on various other disks. When logged into the emergency shell, I verified that device nodes /dev/mmcblk* did not exist hence the above from /etc/fstab could not be mounted. Multiple reboots into the new kernel could not clear the fault. I booted into the old kernel 6.12.43 and the system booted normally. All filesystems mounted as expected. I then booted into the new kernel 6.12.48 again and the system booted normally. Unable to reproduce after this point. I initially suspected hardware failure but this made no sense, as the eMMC disk it was unable to detect contained the bootloader, kernel, and initrd it was successfully running from to partially boot. So GRUB could see it just fine, but the kernel could not. Relevant dmesg: [ 1.530670] mmc1: SDHCI controller on PCI [0000:00:1c.0] using ADMA 64-bit [ 1.533312] mmc0: SDHCI controller on PCI [0000:00:1b.0] using ADMA 64-bit [ 1.677950] mmc1: new DDR MMC card at address 0001 [ 1.695380] mmcblk1: mmc1:0001 004GA0 3.69 GiB [ 1.698606] mmcblk1: p1 p2 [ 1.699469] mmcblk1boot0: mmc1:0001 004GA0 2.00 MiB [ 1.700699] mmcblk1boot1: mmc1:0001 004GA0 2.00 MiB [ 1.701879] mmcblk1rpmb: mmc1:0001 004GA0 512 KiB, chardev (244:0) [ 8.356788] systemd[1]: Expecting device dev-mmcblk1p2.device - /dev/mmcblk1p2... [ 9.875619] EXT4-fs (mmcblk1p2): mounting ext2 file system using the ext4 subsystem Relevant lspci: 00:1b.0 SD Host controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SDXC/MMC Host Controller (rev 0b) 00:1c.0 SD Host controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series eMMC Controller (rev 0b)
Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#1116125: linux-image-amd64: system booted into emergency mode after upgrade to 6.12.48 Lloyd <ng2d68@proton.me> - 2025-09-24 06:20 +0200
Bug#1116125: linux-image-amd64: system booted into emergency mode after upgrade to 6.12.48 Salvatore Bonaccorso <carnil@debian.org> - 2025-09-25 10:40 +0200
Bug#1116125: linux-image-amd64: system booted into emergency mode after upgrade to 6.12.48 Lloyd <ng2d68@proton.me> - 2025-09-26 01:40 +0200
Processed: Re: Bug#1116125: linux-image-amd64: system booted into emergency mode after upgrade to 6.12.48 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-09-25 10:40 +0200
Bug#1116125: marked as done (linux-image-amd64: system booted into emergency mode after upgrade to 6.12.48) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-09-26 21:20 +0200
csiph-web