Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #88062 > unrolled thread

Bug#1108065: linux-image-6.12.32-amd64: Fails to boot on emmc

Started byJeremy Lincicome <w0jrl1@gmail.com>
First post2025-06-20 00:40 +0200
Last post2025-06-23 11:30 +0200
Articles 6 — 3 participants

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1108065: linux-image-6.12.32-amd64: Fails to boot on emmc Jeremy Lincicome <w0jrl1@gmail.com> - 2025-06-20 00:40 +0200
    Bug#1108065: linux-image-6.12.32-amd64: Fails to boot on emmc Jeremy Lincicome <w0jrl1@gmail.com> - 2025-06-20 01:00 +0200
    Bug#1108065: linux-image-6.12.32-amd64: Fails to boot on emmc Salvatore Bonaccorso <carnil@debian.org> - 2025-06-20 01:00 +0200
      Bug#1108065: linux-image-6.12.32-amd64: Fails to boot on emmc Jeremy Lincicome <w0jrl1@gmail.com> - 2025-06-20 02:40 +0200
        Bug#1108065: linux-image-6.12.32-amd64: Fails to boot on emmc Jeremy Lincicome <w0jrl1@gmail.com> - 2025-06-20 18:40 +0200
    Bug#1108065: [regression v6.12.30..v6.12.32] mmc1: mmc_select_hs400 failed, error -110 / boot regression on Lenovo IdeaPad 1 15ADA7 Shawn Lin <shawn.lin@rock-chips.com> - 2025-06-23 11:30 +0200

#88062 — Bug#1108065: linux-image-6.12.32-amd64: Fails to boot on emmc

FromJeremy Lincicome <w0jrl1@gmail.com>
Date2025-06-20 00:40 +0200
SubjectBug#1108065: linux-image-6.12.32-amd64: Fails to boot on emmc
Message-ID<KZw5j-bL1v-9@gated-at.bofh.it>
Package: linux-image-6.12.32-amd64
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: debian-amd64@lists.debian.org
User: debian-amd64@lists.debian.org
Usertags: amd64

Dear Maintainer,

I have a Lenovo IdeaPad 1 15ADA7, and am not able to boot from the EMMC 
starting with this kernel. I'm including a link from the Be My Eyes app 
that shows the boot error. I used this app to get the error because I'm 
blind, and cannot read the boot screen independently.
https://share.bemyeyes.com/chat/kE3kuHs4c3

* What led up to the situation?
Booting the machine.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I restored a btrfs snapshot with  6.12.30-amd64 to get the machine 
running again.
* What was the outcome of this action?
I'm not able to update the system. If I do, it won't boot.
* What outcome did you expect instead?
The system should boot after an update.

-- System Information:
Debian Release: 13.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.30-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-6.12.32-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.148.1
ii kmod 34.2-2
ii linux-base 4.12

Versions of packages linux-image-6.12.32-amd64 recommends:
ii apparmor 4.1.0-1

Versions of packages linux-image-6.12.32-amd64 suggests:
pn debian-kernel-handbook <none>
ii firmware-linux-free 20241210-2
ii grub-efi-amd64 2.12-7
pn linux-doc-6.12 <none>

-- 
Sincerely,
Jeremy Lincicome W0JRL
JL Applied Technologies:
https://jlappliedtechnologies.com
SkyHubLink System:
https://skyhublink.com

[toc] | [next] | [standalone]

#88063

FromJeremy Lincicome <w0jrl1@gmail.com>
Date2025-06-20 01:00 +0200
Message-ID<KZwoF-bL8G-1@gated-at.bofh.it>
In reply to#88062
On 6/19/25 16:38, Salvatore Bonaccorso wrote:
> Control: reassign -1 src:linux 6.12.32-1
> Control: tags -1 + moreinfo
> Control: severity 1108065 serious
>
> Hi,
>
> On Thu, Jun 19, 2025 at 04:29:32PM -0600, Jeremy Lincicome wrote:
>> Package: linux-image-6.12.32-amd64
>> Severity: critical
>> Justification: breaks the whole system
>> X-Debbugs-Cc: debian-amd64@lists.debian.org
>> User: debian-amd64@lists.debian.org
>> Usertags: amd64
>>
>> Dear Maintainer,
>>
>> I have a Lenovo IdeaPad 1 15ADA7, and am not able to boot from the EMMC
>> starting with this kernel. I'm including a link from the Be My Eyes app that
>> shows the boot error. I used this app to get the error because I'm blind,
>> and cannot read the boot screen independently.
>> https://share.bemyeyes.com/chat/kE3kuHs4c3
>>
>> * What led up to the situation?
>> Booting the machine.
>> * What exactly did you do (or not do) that was effective (or
>> ineffective)?
>> I restored a btrfs snapshot with  6.12.30-amd64 to get the machine running
>> again.
>> * What was the outcome of this action?
>> I'm not able to update the system. If I do, it won't boot.
>> * What outcome did you expect instead?
>> The system should boot after an update.
> I think this is the same as the already reported #1107979.

That bug sounds very similar to this one.

> Would you be able to bisect the changes between 6.12.30 upstream and
> 6.12.32 to identify the offending commit?

No, not without a little hand-holding.

> Regards,
> Salvatore


-- 
Sincerely,
Jeremy Lincicome W0JRL
JL Applied Technologies:
https://jlappliedtechnologies.com
SkyHubLink System:
https://skyhublink.com

[toc] | [prev] | [next] | [standalone]

#88064

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-06-20 01:00 +0200
Message-ID<KZwoF-bL8G-5@gated-at.bofh.it>
In reply to#88062
Hi,

On Fri, Jun 20, 2025 at 12:38:16AM +0200, Salvatore Bonaccorso wrote:
> Control: reassign -1 src:linux 6.12.32-1
> Control: tags -1 + moreinfo
> Control: severity 1108065 serious
> 
> Hi,
> 
> On Thu, Jun 19, 2025 at 04:29:32PM -0600, Jeremy Lincicome wrote:
> > Package: linux-image-6.12.32-amd64
> > Severity: critical
> > Justification: breaks the whole system
> > X-Debbugs-Cc: debian-amd64@lists.debian.org
> > User: debian-amd64@lists.debian.org
> > Usertags: amd64
> > 
> > Dear Maintainer,
> > 
> > I have a Lenovo IdeaPad 1 15ADA7, and am not able to boot from the EMMC
> > starting with this kernel. I'm including a link from the Be My Eyes app that
> > shows the boot error. I used this app to get the error because I'm blind,
> > and cannot read the boot screen independently.
> > https://share.bemyeyes.com/chat/kE3kuHs4c3
> > 
> > * What led up to the situation?
> > Booting the machine.
> > * What exactly did you do (or not do) that was effective (or
> > ineffective)?
> > I restored a btrfs snapshot with  6.12.30-amd64 to get the machine running
> > again.
> > * What was the outcome of this action?
> > I'm not able to update the system. If I do, it won't boot.
> > * What outcome did you expect instead?
> > The system should boot after an update.
> 
> I think this is the same as the already reported #1107979.
> 
> Would you be able to bisect the changes between 6.12.30 upstream and
> 6.12.32 to identify the offending commit?

Additionally, please do test as well the kernel from experimental
(6.15.2-1~exp1 and soonish 6.15.3-1~exp1) to see if the problem
persists there as well.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#88065

FromJeremy Lincicome <w0jrl1@gmail.com>
Date2025-06-20 02:40 +0200
Message-ID<KZxXr-bM9S-1@gated-at.bofh.it>
In reply to#88064
Hi,

On 6/19/25 16:49, Salvatore Bonaccorso wrote:
> Hi,
>
> On Fri, Jun 20, 2025 at 12:38:16AM +0200, Salvatore Bonaccorso wrote:
>> Control: reassign -1 src:linux 6.12.32-1
>> Control: tags -1 + moreinfo
>> Control: severity 1108065 serious
>>
>> Hi,
>>
>> On Thu, Jun 19, 2025 at 04:29:32PM -0600, Jeremy Lincicome wrote:
>>> Package: linux-image-6.12.32-amd64
>>> Severity: critical
>>> Justification: breaks the whole system
>>> X-Debbugs-Cc: debian-amd64@lists.debian.org
>>> User: debian-amd64@lists.debian.org
>>> Usertags: amd64
>>>
>>> Dear Maintainer,
>>>
>>> I have a Lenovo IdeaPad 1 15ADA7, and am not able to boot from the EMMC
>>> starting with this kernel. I'm including a link from the Be My Eyes app that
>>> shows the boot error. I used this app to get the error because I'm blind,
>>> and cannot read the boot screen independently.
>>> https://share.bemyeyes.com/chat/kE3kuHs4c3
>>>
>>> * What led up to the situation?
>>> Booting the machine.
>>> * What exactly did you do (or not do) that was effective (or
>>> ineffective)?
>>> I restored a btrfs snapshot with  6.12.30-amd64 to get the machine running
>>> again.
>>> * What was the outcome of this action?
>>> I'm not able to update the system. If I do, it won't boot.
>>> * What outcome did you expect instead?
>>> The system should boot after an update.
>> I think this is the same as the already reported #1107979.
>>
>> Would you be able to bisect the changes between 6.12.30 upstream and
>> 6.12.32 to identify the offending commit?
> Additionally, please do test as well the kernel from experimental
> (6.15.2-1~exp1 and soonish 6.15.3-1~exp1) to see if the problem
> persists there as well.

I just tested 6.15.2-1~exp1, and as far as I can tell, got the same error.

-- 
Sincerely,
Jeremy Lincicome W0JRL
JL Applied Technologies:
https://jlappliedtechnologies.com
SkyHubLink System:
https://skyhublink.com

[toc] | [prev] | [next] | [standalone]

#88090

FromJeremy Lincicome <w0jrl1@gmail.com>
Date2025-06-20 18:40 +0200
Message-ID<KZMWt-bVX7-1@gated-at.bofh.it>
In reply to#88065
On 6/19/25 18:36, Jeremy Lincicome wrote:
> Hi,
>
> On 6/19/25 16:49, Salvatore Bonaccorso wrote:
>> Hi,
>>
>> On Fri, Jun 20, 2025 at 12:38:16AM +0200, Salvatore Bonaccorso wrote:
>>> Control: reassign -1 src:linux 6.12.32-1
>>> Control: tags -1 + moreinfo
>>> Control: severity 1108065 serious
>>>
>>> Hi,
>>>
>>> On Thu, Jun 19, 2025 at 04:29:32PM -0600, Jeremy Lincicome wrote:
>>>> Package: linux-image-6.12.32-amd64
>>>> Severity: critical
>>>> Justification: breaks the whole system
>>>> X-Debbugs-Cc: debian-amd64@lists.debian.org
>>>> User: debian-amd64@lists.debian.org
>>>> Usertags: amd64
>>>>
>>>> Dear Maintainer,
>>>>
>>>> I have a Lenovo IdeaPad 1 15ADA7, and am not able to boot from the 
>>>> EMMC
>>>> starting with this kernel. I'm including a link from the Be My Eyes 
>>>> app that
>>>> shows the boot error. I used this app to get the error because I'm 
>>>> blind,
>>>> and cannot read the boot screen independently.
>>>> https://share.bemyeyes.com/chat/kE3kuHs4c3
>>>>
>>>> * What led up to the situation?
>>>> Booting the machine.
>>>> * What exactly did you do (or not do) that was effective (or
>>>> ineffective)?
>>>> I restored a btrfs snapshot with  6.12.30-amd64 to get the machine 
>>>> running
>>>> again.
>>>> * What was the outcome of this action?
>>>> I'm not able to update the system. If I do, it won't boot.
>>>> * What outcome did you expect instead?
>>>> The system should boot after an update.
>>> I think this is the same as the already reported #1107979.
>>>
>>> Would you be able to bisect the changes between 6.12.30 upstream and
>>> 6.12.32 to identify the offending commit?
>> Additionally, please do test as well the kernel from experimental
>> (6.15.2-1~exp1 and soonish 6.15.3-1~exp1) to see if the problem
>> persists there as well.
>
> I just tested 6.15.2-1~exp1, and as far as I can tell, got the same 
> error.

I just tried 6.15.3-1~exp1 and got the same error.
Am I correct in assuming that the error won't show up in any logs with 
more information?
I can chroot into the installed system from a Gnome live image if needed.

-- 
Sincerely,
Jeremy Lincicome W0JRL
JL Applied Technologies:
https://jlappliedtechnologies.com
SkyHubLink System:
https://skyhublink.com

[toc] | [prev] | [next] | [standalone]

#88121 — Bug#1108065: [regression v6.12.30..v6.12.32] mmc1: mmc_select_hs400 failed, error -110 / boot regression on Lenovo IdeaPad 1 15ADA7

FromShawn Lin <shawn.lin@rock-chips.com>
Date2025-06-23 11:30 +0200
SubjectBug#1108065: [regression v6.12.30..v6.12.32] mmc1: mmc_select_hs400 failed, error -110 / boot regression on Lenovo IdeaPad 1 15ADA7
Message-ID<L0LEZ-cyMS-1@gated-at.bofh.it>
In reply to#88062
+ Jonathan Liu

在 2025/06/21 星期六 4:21, Salvatore Bonaccorso 写道:
> On Fri, Jun 20, 2025 at 09:20:41PM +0200, Salvatore Bonaccorso wrote:
>> Hi
>>
>> In Debian we got a regression report booting on a Lenovo IdeaPad 1
>> 15ADA7 dropping finally into the initramfs shell after updating from
>> 6.12.30 to 6.12.32 with messages before dropping into the intiramfs
>> shell:
>>
>> mmc1: mmc_select_hs400 failed, error -110
>> mmc1: error -110 whilst initialising MMC card
>>
>> The original report is at https://bugs.debian.org/1107979 and the
>> reporter tested as well kernel up to 6.15.3 which still fails to boot.
>>
>> Another similar report landed with after the same version update as
>> https://bugs.debian.org/1107979 .
>>
>> I only see three commits touching drivers/mmc between
>> 6.12.30..6.12.32:
>>
>> 28306c58daf8 ("mmc: sdhci: Disable SD card clock before changing parameters")
>> 38828e0dc771 ("mmc: dw_mmc: add exynos7870 DW MMC support")
>> 67bb2175095e ("mmc: host: Wait for Vdd to settle on card power off")
>>
>> I have found a potential similar issue reported in ArchLinux at
>> https://bbs.archlinux.org/viewtopic.php?id=306024
>>
>> I have asked if we can get more information out of the boot, but maybe
>> this regression report already rings  bell for you?

Jonathan reported a similar failure regarding to hs400 on RK3399
platform.
https://lkml.org/lkml/2025/6/19/145

Maybe you could try to revert :
28306c58daf8 ("mmc: sdhci: Disable SD card clock before changing 
parameters")

>>
>> #regzbot introduced v6.12.30..v6.12.32
>> #regzbot link: https://bugs.debian.org/1107979
>> #regzbot link: https://bbs.archlinux.org/viewtopic.php?id=306024
> 
> *sigh* apologies for the "mess", the actual right report is
> https://bugs.debian.org/1108065 (where #1107979 at least has
> similarities or might have the same root cause).
> 
> #regzbot link: https://bugs.debian.org/1108065
> 
> Regards,
> Salvatore
> 
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web