[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

Hi Salvatore, 

      On 6/20/25 12:53, Salvatore Bonaccorso wrote:

    

    

      
Hi Jeremy,

On Fri, Jun 20, 2025 at 10:35:17AM -0600, Jeremy Lincicome wrote:


      

        
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.


      

      
Once you drop into the initramfs shell, can you run dmesg to get the
kernel messages printed, so we might see something more interesting? 

    

    

    I can certainly try. Just to make sure I understand, you want me to
    run dmesg after the system fails to boot, and the busybox shell
    loads? Or, are you asking me to run that from a chroot? Please
    understand that my only way to get any output to you from the
    busybox shell is to use the method I used in my initial report. I
    will need to use the Be My Eyes app to get a description of the
    screen, and the AI may not focus on the text, or worse, may try to
    summarize it.

    I know this is an unusual request; is there any possibility of
    meeting on something like Jitsi meet so that you can see my screen 
    through my phone's camera?

    

      

Given it is as well an issue in 6.15.3 based kernel it might now be
worth to bring this already to upstream attention (I have not found
yet a similar report though, which is bit surprising).

Additionally to get the dmesg output printed, as this might become
difficult to get that out to us, two more things:

If you are using quiet kernel parameter, rmeote it so it less quiet.

Secondly it might be a try to use the netconsole if we get far enough.
https://www.kernel.org/doc/html/latest/networking/netconsole.html

Parallel to those questions, I will ask the linux-mmc list if
something rings a bell with the changes between 6.12.30..6.12.32.



    

    

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

  







Reply to: