[Bug 1215436] New: Unable to boot kernels 6.5.2 or 6.5.3 unless acpi=noirq specified
https://bugzilla.suse.com/show_bug.cgi?id=1215436 Bug ID: 1215436 Summary: Unable to boot kernels 6.5.2 or 6.5.3 unless acpi=noirq specified Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: stuart@stella-maris.org.uk QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869567 --> https://bugzilla.suse.com/attachment.cgi?id=869567&action=edit dmidecode and journal output On doing a zypper dup the other day it installed kernel 6.5.2 and immediately the system failed to boot, the grub menu appeared and when the timeout expired the display went black for a while and the system then rebooted to the grub menu again. I was able to switch back to kernel 6.4.12 and my system booted normally as it has done for months on kernel 6.4.x. After trying nomodeset to no avail I tried acpi=noirq on the grub linux command and my system would the boot OK. I also tried acpi_enforce_resources=lax but again the system failed to boot.So I'm left having to run with acpi=noirq to get a working system. The CPU is an AMD Ryzen 5 3400G with Radeon Vega Graphics on an MSI B450-A PRO MAX motherboard with the latest available BIOS from July 2023. I have run dmidecode and journal -b and captured the data which is appended here. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c1 --- Comment #1 from Stuart Rogers <stuart@stella-maris.org.uk> --- Created attachment 869568 --> https://bugzilla.suse.com/attachment.cgi?id=869568&action=edit Journal output -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c2 --- Comment #2 from Stuart Rogers <stuart@stella-maris.org.uk> --- Just to add the /proc/cmdline is BOOT_IMAGE=/boot/vmlinuz-6.5.3-1-default root=UUID=190442a2-32b3-47e7-bac7-a39e6841236f splash=silent resume=/dev/disk/by-id/nvme-KINGSTON_SA2000M8250G_50026B728266A552-part3 quiet acpi=noirq mitigations=auto -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 Stuart Rogers <stuart@stella-maris.org.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Hardware|Other |x86-64 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P5 - None -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c4 Stuart Rogers <stuart@stella-maris.org.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(stuart@stella-mar | |is.org.uk) | --- Comment #4 from Stuart Rogers <stuart@stella-maris.org.uk> --- Tried that loglevel=7 without quiet and acpi-noirq but all I get is a load of messages flashing past on screen but too fast to see clearly. Looks from memory the same as when I do it without quiet and acpi. Then it just reboots. On next good boot with acpi=noirq I can see no messages anywhere relating to this fail boot, nothing in dmesg or journal relating to the fail. Where would messages be expected to be saved if any? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c7 --- Comment #7 from Stuart Rogers <stuart@stella-maris.org.uk> --- I downloaded kernel-default-6.5.4-3.1.x86_64.rpm when it finished and it boots OK when I use acpi=noirq, however when I remove quiet and acpi=noirq and add boot_delay it waits a ling time before the messages start but they still go through too quickly to really see, even when I used a delay of 100. I was not sure what the devel and vdso kernels were for. Is it worth tying the 6.6 kernel as mentioned in bug 1215328 to see if a vanilla kernel still fails? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c12 --- Comment #12 from Stuart Rogers <stuart@stella-maris.org.uk> --- Well by the time I read your update I had already removed your kernel, so I tried those options with the 6.5.3 kernel but the messages still flew by too fast. Which is best now to try the 6.6 kernel or reload your 6.5.4 kernel and try those options with that? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c14 --- Comment #14 from Stuart Rogers <stuart@stella-maris.org.uk> --- Well I just tried the 6.6 kernel with the sysctl etc additions and removing acpi & quiet but it still fails to boot exactly like the others. The messages are still to fast for the naked eye so I might try a video with my phone! Anyway 6.6 boots OK with acpi=noirq. Is it still worth trying your 6.5.4? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c15 --- Comment #15 from Stuart Rogers <stuart@stella-maris.org.uk> --- I have managed to video the messages on screen with all those parameters added and on viewing it I can see no obvious errors. The last message which shows prior to it rebooting relates to the firewire interface on the motherboard it starts with initcall fw_ohci_int and has [firewire_ohci] as part of it. I'll try to extract the full message in the morning as it is a bit blurred! Anyway the screen then goes blank and it reboots to the hardware messages about entering BIOS etc and the goes to the standard GRUB menu. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c22 --- Comment #22 from Stuart Rogers <stuart@stella-maris.org.uk> --- Will do, I also just tried 6.6 RC3 on my test system and that still only works with the blacklist added. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c23 --- Comment #23 from Stuart Rogers <stuart@stella-maris.org.uk> --- Just tested your latest build 6.5.5 and it works fine without the blacklist. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c26 --- Comment #26 from Stuart Rogers <stuart@stella-maris.org.uk> --- Created attachment 869781 --> https://bugzilla.suse.com/attachment.cgi?id=869781&action=edit hwinfo -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c27 --- Comment #27 from Stuart Rogers <stuart@stella-maris.org.uk> --- Created attachment 869782 --> https://bugzilla.suse.com/attachment.cgi?id=869782&action=edit lspci -vvnnxxx -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c28 --- Comment #28 from Stuart Rogers <stuart@stella-maris.org.uk> --- Created attachment 869783 --> https://bugzilla.suse.com/attachment.cgi?id=869783&action=edit lspci -tv -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c29 --- Comment #29 from Stuart Rogers <stuart@stella-maris.org.uk> --- Tested kernel-default-6.5.5-7.1.x86_64.rpm this morning and it fails to boot if I remove the blacklist. The command outputs are from a working kernel and are added as attachments. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c31 --- Comment #31 from Stuart Rogers <stuart@stella-maris.org.uk> --- Just tested kernel-default-6.5.5-8.1.x86_64.rpm and it fails to boot with no blacklist, boots OK if I leave blacklist in. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c33 --- Comment #33 from Stuart Rogers <stuart@stella-maris.org.uk> --- I just went to look this morning and found kernel-default-6.5.5-8.2.x86_64.rpm so I tested that as well just in case but it still fails if I remove the blacklist. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c36 --- Comment #36 from Stuart Rogers <stuart@stella-maris.org.uk> --- Checked again this evening and found kernel-default-6.5.5-8.4.x86_64.rpm which I thought I'd try, still no go with blacklist removed sadly. I really appreciate the help I'm getting here. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c38 --- Comment #38 from Stuart Rogers <stuart@stella-maris.org.uk> --- OK success this time it booted fine without the blacklist using kernel-default-6.5.5-9.1.x86_64.rpm, so I'm guessing one of these last reverts is the issue. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c41 --- Comment #41 from Stuart Rogers <stuart@stella-maris.org.uk> --- So kernel-default-6.5.5-9.1.x86_64.rpm earlier today worked fine without the blacklist. Now kernel-default-6.5.5-10.1.x86_64.rpm fails to boot without the blacklist. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c44 --- Comment #44 from Stuart Rogers <stuart@stella-maris.org.uk> --- Well I just tested the 11.1 kernel with all the extra parameters to slow down booting so I could watch the messages. Still went too fast for me but it did boot to desktop eventually so I have capture the journal and dmesg output which I will upload. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c45 --- Comment #45 from Stuart Rogers <stuart@stella-maris.org.uk> --- Created attachment 869871 --> https://bugzilla.suse.com/attachment.cgi?id=869871&action=edit Journal output from booting 11.1 kernel -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c46 --- Comment #46 from Stuart Rogers <stuart@stella-maris.org.uk> --- Created attachment 869872 --> https://bugzilla.suse.com/attachment.cgi?id=869872&action=edit dmesg output from booting kernel 11.1 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c48 --- Comment #48 from Stuart Rogers <stuart@stella-maris.org.uk> --- Initial test boot of 14.1 kernel did not boot, so tried again with all the delay and other added parameters and it still did not boot, loads of messages but I blinked and missed the final ones. Anyway I'll try again later with phone ready to capture the messages and see what I find. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c49 --- Comment #49 from Stuart Rogers <stuart@stella-maris.org.uk> --- Managed to video the messages this time and around 4:11:16 into the video you can see the message saying the firewire_ohci was added but the a whole bunch more messages before it gives up and reboots. I'll upload the video in case anything can be seen in it of more value. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c50 --- Comment #50 from Stuart Rogers <stuart@stella-maris.org.uk> --- Video asis is too large to upload and I'm not sure I have anywhere I can upload it to, it's 1.3gb. Is there anything I should look out for in the messages which might help and perhaps I can reduce the video to just the relevant part to upload? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c51 --- Comment #51 from Stuart Rogers <stuart@stella-maris.org.uk> --- Created attachment 869879 --> https://bugzilla.suse.com/attachment.cgi?id=869879&action=edit Section of video of kernel 14.1 booting -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c52 --- Comment #52 from Stuart Rogers <stuart@stella-maris.org.uk> --- I'm had a go at reducing the video to where it says it is booting paravirtualized kernel up to the point it reboots. Hope this might give what you need. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c55 --- Comment #55 from Stuart Rogers <stuart@stella-maris.org.uk> --- Yes that's no problem as it is a desktop I assembled myself so no warranty worries. It might be a short while before I get the chance so will update when done with photos. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c56 --- Comment #56 from Stuart Rogers <stuart@stella-maris.org.uk> --- OK so I opened the PC case and to be honest I'd forgotten this was a PCI-E add-on firewire card, anyway I have photo graphed it so you can see the two chips. It was a purchase back in 2020 and was described as PCI-e 1X IEEE 1394A 4 Port (3+1) Firewire Card Adapter. I will upload the photo. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c57 --- Comment #57 from Stuart Rogers <stuart@stella-maris.org.uk> --- Created attachment 869905 --> https://bugzilla.suse.com/attachment.cgi?id=869905&action=edit Photo of Firewire PCI-E card -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c58 --- Comment #58 from Stuart Rogers <stuart@stella-maris.org.uk> --- I discovered two new kernels 16.1 and 17.1 so decided to test them to see what happened. Both booted successfully to the desktop without the blacklist for firewire. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c61 --- Comment #61 from Stuart Rogers <stuart@stella-maris.org.uk> --- I just replaced my Firewire card with one which does not have the Asmedia chip on it and the system boots perfectly, this card has a VIA chip. I can test any fix easily by replacing my old card in the PC when required. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com