The latest stable kernel 6.1.0-18 (6.1.76-1) appears to enter an error loop when trying to boot on my laptop.
The boot screen messages scroll too quickly to see the 'start' of the problem but after a few seconds it starts repeating the following two lines:
(the printk messages can be ignored - I only mention them for completeness)
After approx 30 seconds of this a different message is repeated about 15 times, which scrolls by too fast to read, and then the console resumes displaying the two messages above until I power the system down. As it was just these two lines being repeated they were clear enough for me to be able to write them down.
The earlier 6.1.0-17 kernel still boots ok, as does my custom 6.1.69-1 kernel. I had a look at the Debian changelog for the kernel, going back to 6.1.69-1, but didn't see anything that seemed to apply - there were some ACPI changes relating to recent Lenovo laptops, including an additional blacklisted module, but the laptop with which I'm having this problem is a low-spec ~5 year-old Asus with a Celeron CPU and doesn't appear to use that particular module.
Subjectively, it seemed to take an inordinately long time to generate the init ramdisk during the installation of the kernel, but it appears to unpack ok at the start of the boot.
I'm really not sure where to start looking.
The boot screen messages scroll too quickly to see the 'start' of the problem but after a few seconds it starts repeating the following two lines:
Code:
ACPI Error: No installed handler for fixed event - PM_TIMER (0), disabling (2022331/evevent-255)
Code:
** 6 printk messages dropped **
After approx 30 seconds of this a different message is repeated about 15 times, which scrolls by too fast to read, and then the console resumes displaying the two messages above until I power the system down. As it was just these two lines being repeated they were clear enough for me to be able to write them down.
The earlier 6.1.0-17 kernel still boots ok, as does my custom 6.1.69-1 kernel. I had a look at the Debian changelog for the kernel, going back to 6.1.69-1, but didn't see anything that seemed to apply - there were some ACPI changes relating to recent Lenovo laptops, including an additional blacklisted module, but the laptop with which I'm having this problem is a low-spec ~5 year-old Asus with a Celeron CPU and doesn't appear to use that particular module.
Subjectively, it seemed to take an inordinately long time to generate the init ramdisk during the installation of the kernel, but it appears to unpack ok at the start of the boot.
I'm really not sure where to start looking.
Statistics: Posted by LeeE — 2024-02-25 22:06 — Replies 1 — Views 61