dear Uwe, i found time to proceed as you proposed, managed to send an updated bug report with reportbug. Please see the Bug#1121348best regards
On Tue, Dec 2, 2025 at 12:03 AM Uwe Kleine-König < [email protected]> wrote: > Hello Giorgos, > > On Tue, Nov 25, 2025 at 01:07:58AM +0200, Giorgos Kourafas wrote: > > the new number og the bug is Bug#1121348 > > the new bug report doesn't contain the requested kernel log however. > > Please proceed as follows: > > - Boot the broken kernel and login (if that doesn't work using keyboard > and monitor, please use ssh). > - Run `reportbug linux-image-$(uname -r)` > - On the prompt "Is the bug you found listed above > [y|N|b|m|r|q|s|f|e|?]?" enter "1121348" (without the quotes). > - On the next prompt "What do you want to do now [N|x|o|r|b|e|q|?]?" > reply "x" and then answer the question "Use sudo to read the kernel > log?" with "y". > > After some more interaction with reportbug that should result in an > addition to the original bug that we can work with. > > Thanks > Uwe >
