home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   linux.debian.kernel      Debian kernel discussions      2,884 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 1,336 of 2,884   
   Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= to Benjamin Drung   
   Re: Bug#1116251: linux-image-6.12.48+deb   
   05 Nov 25 20:20:01   
   
   XPost: linux.debian.bugs.dist   
   From: u.kleine-koenig@baylibre.com   
      
   On Thu, Oct 30, 2025 at 08:35:37PM +0100, Benjamin Drung wrote:   
   > On Wed, 24 Sep 2025 20:46:32 +0200 Benjamin Drung    
   > wrote:   
   > > Package: src:linux   
   > > Version: 6.12.48-1   
   > > Severity: normal   
   > > X-Debbugs-Cc: bdrung@debian.org   
   > >    
   > > Hi,   
   > >    
   > > I have three Raspberry Pi Zero W running trixie headless. All stopped   
   > > working after upgrading to linux-image-6.12.48+deb13-rpi. Since they   
   > are   
   > > headless, I removed the SD card and checked the logs on there. The   
   > last   
   > > logs where from upgrading to linux-image-6.12.48+deb13-rpi and the   
   > > shutdown (from the reboot). There were no logs from the   
   > > linux-image-6.12.48+deb13-rpi boot. So it probably failed to boot in   
   > the   
   > > kernel or initrd (before switching to the root fs).   
   > >    
   > > I changed the kernel+initrd in /boot/firmware/config.txt from   
   > > 6.12.48+deb13-rpi to 6.12.43+deb13-rpi and then the system worked   
   > again.   
   > > I checked that content of the initrd looks okay (only the kernel   
   > module   
   > > versions differ).   
   >    
   > I found some time to rip one out of the installation, solder a cable to   
   > the UART pins and boot with a serial console attached.   
   >    
   > I configured /boot/firmware/config.txt:   
   >    
   > ```   
   > enable_uart=1   
   > uart_2ndstage=1   
   > ```   
   >    
   > When I boot with 6.12.48+deb13-rpi it hangs here:   
   >    
   > ```   
   > Raspberry Pi Bootcode   
   > Read File: config.txt, 532   
   > Read File: start.elf, 2981056 (bytes)   
   > Read File: fixup.dat, 7303 (bytes)   
   > MESS:00:00:01.252151:0: brfs: File read: /mfs/sd/config.txt   
   > MESS:00:00:01.256416:0: brfs: File read: 532 bytes   
   > MESS:00:00:01.292170:0: HDMI0:EDID error reading EDID block 0 attempt 0   
   > MESS:00:00:01.298336:0: HDMI0:EDID error reading EDID block 0 attempt 1   
   > MESS:00:00:01.304672:0: HDMI0:EDID error reading EDID block 0 attempt 2   
   > MESS:00:00:01.311009:0: HDMI0:EDID error reading EDID block 0 attempt 3   
   > MESS:00:00:01.317346:0: HDMI0:EDID error reading EDID block 0 attempt 4   
   > MESS:00:00:01.323683:0: HDMI0:EDID error reading EDID block 0 attempt 5   
   > MESS:00:00:01.330019:0: HDMI0:EDID error reading EDID block 0 attempt 6   
   > MESS:00:00:01.336356:0: HDMI0:EDID error reading EDID block 0 attempt 7   
   > MESS:00:00:01.342693:0: HDMI0:EDID error reading EDID block 0 attempt 8   
   > MESS:00:00:01.349030:0: HDMI0:EDID error reading EDID block 0 attempt 9   
   > MESS:00:00:01.355125:0: HDMI0:EDID giving up on reading EDID block 0   
   > MESS:00:00:01.361505:0: brfs: File read: /mfs/sd/config.txt   
   > MESS:00:00:01.365951:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not   
   defined   
   > MESS:00:00:01.558660:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not   
   defined   
   > MESS:00:00:01.564486:0: *** Restart logging   
   > MESS:00:00:01.568364:0: brfs: File read: 532 bytes   
   > MESS:00:00:01.573602:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 0   
   > MESS:00:00:01.580979:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 1   
   > MESS:00:00:01.587837:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 2   
   > MESS:00:00:01.594695:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 3   
   > MESS:00:00:01.601552:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 4   
   > MESS:00:00:01.608410:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 5   
   > MESS:00:00:01.615267:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 6   
   > MESS:00:00:01.622126:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 7   
   > MESS:00:00:01.628983:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 8   
   > MESS:00:00:01.635841:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 9   
   > MESS:00:00:01.642457:0: hdmi: HDMI0:EDID giving up on reading EDID block 0   
   > MESS:00:00:01.648361:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 0   
   > MESS:00:00:01.656152:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 1   
   > MESS:00:00:01.663011:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 2   
   > MESS:00:00:01.669869:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 3   
   > MESS:00:00:01.676725:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 4   
   > MESS:00:00:01.683584:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 5   
   > MESS:00:00:01.690442:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 6   
   > MESS:00:00:01.697299:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 7   
   > MESS:00:00:01.704157:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 8   
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca