On 3 May 2025 15:03:18 CEST, "Martin-Éric Racine" <martin-eric.rac...@iki.fi> 
wrote:
>la 3.5.2025 klo 14.42 Chris Hofstaedtler (z...@debian.org) kirjoitti:
>>
>> Control: tags -1 + moreinfo unreproducible
>>
>> On Fri, May 02, 2025 at 08:14:37PM +0300, Martin-Éric Racine wrote:
>> > pe 2.5.2025 klo 19.44 Chris Hofstaedtler (z...@debian.org) kirjoitti:
>> > >
>> > > On Sun, Apr 13, 2025 at 10:23:17AM +0300, Martin-Éric Racine wrote:
>> > > > Is there any way I can help the maintainers pinpoint the source of the 
>> > > > problem?
>> > >
>> > > This bug needs two things:
>> > >
>> > > 1) A full reproducer step list, starting from "I have nothing but an 
>> > > empty
>> > > amd64 VM".
>> >
>> > There isn't much to reproduce:
>> > 1) Start with a fully functional host running Bookworm with GRUB-EFI
>> > on a brtfs filesystem created using d-i/Bookworm's default @rootfs
>> > subvolume name.
>> > 2) Change APT sources from Bookworm to Trixie.
>> > 3) Dist-upgrade.
>> > 4) Reboot.
>> > 5) Find the above kernel panic.
>> > 6) Using Bookworm d-i's rescue mode via EFI, APT pin and downgrade
>> > grub* to Bookworm. All other packages remain at Trixie versions.
>> > 7) Reboot.
>> > 8) The host boots normally.
>>
>> I've followed these steps today, and cannot reproduce the problem.
>> The upgraded VM boots successfully.
>
>I beleive you.  Again, googling this exact error mostly pulls up
>reports of this failing on ASUS motherboards of various models.
>

Unfortunately some firmware is just broken and there isn't much that can be 
done about that.

As we're moving towards more upstream solutions that use more parts of the 
firmware, such as EFI LoadFile2 protocols for loading the initrd, more hardware 
will break.

We cannot commit to keep specific hardware working, whether it's between stable 
releases or even in security updates when we run out of ability to do backports.

I suggest documenting no longer supported hardware in the release notes, and 
potentially say we don't support mainboards made before 2020.

-- 
sent from my phone, excuse the brevity, if any

Reply via email to