From: owner@bugs.debian.org 
  
 This is a multi-part message in MIME format... 
  
 Your message dated Fri, 26 Sep 2025 21:11:05 +0200 
 with message-id  
 and subject line Re: Bug#1116125: linux-image-amd64: system booted into 
 emergency mode after upgrade to 6.12.48 
 has caused the Debian Bug report #1116125, 
 regarding linux-image-amd64: system booted into emergency mode after upgrade 
 to 6.12.48 
 to be marked as done. 
  
 This means that you claim that the problem has been dealt with. 
 If this is not the case it is now your responsibility to reopen the 
 Bug report if necessary, and/or fix the problem forthwith. 
  
 (NB: If you are a system administrator and have no idea what this 
 message is talking about, this may indicate a serious mail system 
 misconfiguration somewhere. Please contact owner@bugs.debian.org 
 immediately.) 
  
  
 -- 
 1116125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116125 
 Debian Bug Tracking System 
 Contact owner@bugs.debian.org with problems 
  
 Received: (at submit) by bugs.debian.org; 24 Sep 2025 04:15:00 +0000 
 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02 
  (2024-03-25) on buxtehude.debian.org 
 X-Spam-Level: 
 X-Spam-Status: No, score=-14.1 required=4.0 tests=BAYES_00, 
  BODY_INCLUDES_PACKAGE,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU, 
  DKIM_VALID_EF,FOURLA,HAS_PACKAGE,RCVD_IN_VALIDITY_CERTIFIED_BLOCKED, 
  RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED, 
  SPF_HELO_PASS,SPF_PASS,WORD_WITHOUT_VOWELS autolearn=ham 
  autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 
 X-Spam-Bayes: score:0.0000 Tokens: new, 42; hammy, 150; neutral, 80; spammy, 
  0. spammytokens: hammytokens:0.000-+--UD:device, 
  0.000-+--HFeedback-ID:user, 0.000-+--HFeedback-ID:proton, 
  0.000-+--deb13-amd64, 0.000-+--deb13amd64 
 Return-path:  
 Received: from mail-106110.protonmail.ch ([79.135.106.110]:50589) 
  by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_P 
 S_RSAE_SHA256__AES_256_GCM:256) 
  (Exim 4.96) 
  (envelope-from ) 
  id 1v1Gu7-006i1W-1B 
  for submit@bugs.debian.org; 
  Wed, 24 Sep 2025 04:15:00 +0000 
 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; 
  s=mkjifq54tzatfluoc2gcsdtj6i.protonmail; t=1758686763; x=1758945963; 
  bh=v9hhjX7X/n+Eujs3LlvMiojKv7l7ShfxvoAVIRPO3LM=; 
  h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: 
   Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; 
  b=dXi8bBoqtK2CMtBe5cjluRa53U9Ieb4f6zbJCtpPQG3fBQI8KPURmgnjVw/9d+A39 
   4ImXCn2VooKlUPlSNi5PVcGDi3WdyDE6dlrpKrB6aOA9L9MkJHd9LiEewmpSleTzJm 
   peoY6Mg5nzleBVIFHmOJe45BUCbPEIckfkWtMADT46UvIX8oXS927I+Tr1UV85JTLL 
   IgipQYsyQW4Mzx7StPU9Uu7d3TvUPPTAMI7pzS8VwSNs2c4MrgW7VC2s4iCSo8EcAF 
   AiTI+raEUy57TnNj6k8CEVj+QFZsOqwEx5EP3xWEUe+HtUTZldYpC4yFKP5fP8hmpo 
   TWuhgkJdyPm8w== 
 Date: Wed, 24 Sep 2025 04:06:00 +0000 
 To: "submit@bugs.debian.org"  
 From: Lloyd  
 Subject: linux-image-amd64: system booted into emergency mode after upgrade 
 to 
 6.12.48 
 Message-ID:  
 Feedback-ID: 125691088:user:proton 
 X-Pm-Message-ID: cedbe4623b97cf97e26ba67303ccd54bbc587b48 
 MIME-Version: 1.0 
 Content-Type: text/plain; charset=utf-8 
 Content-Transfer-Encoding: quoted-printable 
 X-Greylist: delayed 519 seconds by postgrey-1.37 at buxtehude; Wed, 24 Sep 
 2025 04:14:55 UTC 
 Delivered-To: submit@bugs.debian.org 
  
 Package: linux-image-amd64 
 Version: 6.12.48-1 
 Severity: normal 
  
 Upgraded the kernel from linux-image-6.12.43+deb13-amd64 to linu 
 -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... 
  
 [continued in next message] 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)