Package: linux Version: 6.11.9-1 Severity: normal X-Debbugs-Cc: fabstz...@yahoo.fr
Dear maintainer, Since bookworm which runs kernel 6.1 I have an extended boot delay which can last for a few minutes. Dmesg showed that the issue is with the clock source. Setting the kernel parameter 'tsc=unstable' at boot time fixes the issue. I have the same problem with Trixie which now has kernel 6.11 and of course the issue is also with the Debian installer media. (Bookworm and Trixie) The issue is that it is difficult to find out what is really making the boot be stuck for a long time and when booting the installation medium one would believe that the system is completely frozen since that can last for a few minutes. The system doesn't react to any user input when in that state. Moreover if I remove the 'quiet' parameter from the kernel it seems stuck on detecting USB. This is misleading. It is only by looking at the kernel logs that I found it was suggested to use tsc=unstable. How could we prevent users to be stuck at boot time for such a long time without having a clue on what is happening? Here are a few ideas: - run the installer by default with tsc=unstable, but maybe this would pass the value to the installed system, even when not appropriate? And if it doesn't pass it to the installed system, that would just move the problem to 1st boot time and reveal the delay at that time which isn't ideal either. - build the kernel for the installer medium with CONFIG_HAVE_UNSTABLE_SCHED_CLOCK ? - write a notice in the installation guide? In the meantime I sent a report to the kernel mailing list. <https://lore.kernel.org/all/10cf96aa-1276-4bd4-8966-c89037703...@yahoo.fr/> Regards
