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.
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?I think this is the same as the already reported #1107979.
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.
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 147:53:33 |
Calls: | 10,383 |
Calls today: | 8 |
Files: | 14,054 |
D/L today: |
2 files (1,861K bytes) |
Messages: | 6,417,737 |