[Bug 1184575] New: kernel 5.3.18-lp152.69-default does not boot
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 Bug ID: 1184575 Summary: kernel 5.3.18-lp152.69-default does not boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: 64bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: diedrich.ehlerding@t-online.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- currently runnng kernel 5.3.18-lp152.66-default. Today kernel -69 was offered to be installed, and requires a reboot. However, the system does noit boot, it remains in a very early stage of grub stating "loading initial ram disk". No further messages for t least 5 minutes; system does not react to any keys. Having reset the system to a snapshot, the system boots again. Repeted the installation, same behaviour - after the reboot, the system does not boot. IOW: the bug is reproduceable. Resetting again, installed all other updates, and reboot: everything is fine. Conclusion: something is wrong with he installation script and/or initial ram, disk creation. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c1 Gordon Dickens <gordon@dickens.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gordon@dickens.com --- Comment #1 from Gordon Dickens <gordon@dickens.com> --- This is precisely what I experience when I upgrade to kernel-default version 5.3.18-lp152.69.1. Same exact problem.... I have now endeavored to do the upgrade three times with the exact same results. Here is a forum thread that I started: https://forums.opensuse.org/showthread.php/552551-New-kernel-will-not-boot?p... Gordon -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 Diedrich Ehlerding <diedrich.ehlerding@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c2 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None CC| |tiwai@suse.com Flags| |needinfo? --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- Please don't touch the Priority field on Bugzilla; it's the filed only the devs side changes. About the bug: it's hard to diagnose without any logs. Could you give the hardware details? The hwinfo output from the running kernel is a good minimum. Also, since it leads to a blank screen, please try to boot with nomodeset boot option. This will disable the native graphics, and if this works, it means that the graphics driver got broken. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c3 --- Comment #3 from Diedrich Ehlerding <diedrich.ehlerding@t-online.de> --- Created attachment 848218 --> http://bugzilla.opensuse.org/attachment.cgi?id=848218&action=edit output of hwinfo As requested by Takashi Iwai, I enclose output of hwinfo from kernel 5.3.18-66 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c4 --- Comment #4 from Diedrich Ehlerding <diedrich.ehlerding@t-online.de> --- sorry for misunderstanding priority field -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c5 --- Comment #5 from Diedrich Ehlerding <diedrich.ehlerding@t-online.de> --- booting with "nomodeset" option does not change anything. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c7 --- Comment #7 from Gordon Dickens <gordon@dickens.com> --- Created attachment 848219 --> http://bugzilla.opensuse.org/attachment.cgi?id=848219&action=edit hwinfo command output. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c8 --- Comment #8 from Gordon Dickens <gordon@dickens.com> --- Booting with "nomodeset", "splash=silent" and "quite" options makes no difference and there is no output. The screen basically freezes until it apparently times out and restarts. Also, there is no information ever written to /var/log/messages when I attempt to boot kernel-default version 5.3.18-lp152.69.1. Basically, it doesn't appear to get to the point where any logging takes place. Also, on the first boot attempt after installing kernel-default version 5.3.18-lp152.69.1. after posting BIOS, it immediately goes into a "Perform MOK management" screen that I have never seen before. I do not have secure boot enabled and I do not understand why the MOK management screen is being presented for the first time ever. In any event, it doesn't matter whether I "continue boot" or "Enroll MOK", when I then boot the new kernel the computer always basically freezes while displaying: Loading Linux 5.3.18-lp152.69-default ... Loading initial ramdisk ... However, I am able to continue to run the previous kernel-default version 5.3.18-lp152.66.1 by selecting it in the grub boot menu. Anybody got any ideas? Thanks, Gordon Dickens -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c9 --- Comment #9 from Diedrich Ehlerding <diedrich.ehlerding@t-online.de> --- spalsh=silent and/or quite were already remmoved from grub commandline. earlyprintk=efi doesn't change anything; the machine freezes after "loading inital ramdisk ..." and reboots after som,e minutes. As Gordon Dickens reported, it is still possible to select the older kernel nmanually. I reset the system to a btrfs snapshot before I installed the kernel. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c10 Howard Moreland <hrm_sfo@sonic.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hrm_sfo@sonic.net --- Comment #10 from Howard Moreland <hrm_sfo@sonic.net> --- Created attachment 848224 --> http://bugzilla.opensuse.org/attachment.cgi?id=848224&action=edit hwinfo for X390 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c11 --- Comment #11 from Howard Moreland <hrm_sfo@sonic.net> --- I have the same behavior on a ThinkPad X390 Leap 15.2 KDE, dual-boot Window 10, although I never saw the "Perform MOK management" screen. After failure, when next booted into kernel-default 5.3.18-lp152.66.1, I also get howard@localhost:~> sudo journalctl -b-1 [sudo] password for root: Specifying boot ID or boot offset has no effect, no persistent journal was found. howard@localhost:~> hwinfo file attached -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c12 Bill Wayson <bill_wayson@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bill_wayson@yahoo.com --- Comment #12 from Bill Wayson <bill_wayson@yahoo.com> --- I'm glad I'm not alone. I have a bit to add. The 5.3.18-lp152.69-default kernel boots and runs just fine on my desktop (it is running now as I type this). But I get Diedrich's behavior with it on my brand spanking-new Dell XPS 13 9310 laptop (so it is back at 5.3.18-lp152.66-default). Both machines use strict Secure Boot and have the openSUSE .DER enrolled. Let me know if you'd like any files or info on either machine. I'll get them to you ASAP, but you may need to be a bit patient with me. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c20 --- Comment #20 from Gordon Dickens <gordon@dickens.com> --- Takashi Iwai asked "Does it have to do anything with Secure Boot? Did you try to disable it on BIOS if it were on?" Secure boot has always been disabled in my BIOS since the initial installation. Also, as I previously stated, on the first boot attempt after installing kernel-default version 5.3.18-lp152.69.1. after posting BIOS, it immediately goes into a "Perform MOK management" screen that I have never seen before. What is this MOK management screen that is presented for the first time ever after each time that I reinstall kernel-default version 5.3.18-lp152.69.1? Could this have something to do with the failure to successfully boot up? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c22 Udo Lubich <bugzilla@lubich.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla@lubich.com OS|Other |openSUSE Leap 15.2 --- Comment #22 from Udo Lubich <bugzilla@lubich.com> --- Hello, my name is Udo. I also have the problem described with the kernel 15.2.8-lp152.69 on two test systems. My hardware is an Intel NUC10i7. The kernel 15.2.8-lp152.66 still starts without any problems. Secure boot is not activated. I have already tried the options described above without success. I have not yet installed the new kernel on my real system. greetings Udo -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c25 --- Comment #25 from Udo Lubich <bugzilla@lubich.com> --- (In reply to Takashi Iwai from comment #23)
Can anyone test the kernel in OBS Kernel:openSUSE-15.2 repo, just to be sure? http://download.opensuse.org/repositories/Kernel:/openSUSE-15.2/standard/
It's signed with an unofficial key, hence it won't work with Secure Boot.
In my case this Kernel started with the option "intel_iommu=off" greetings Udo -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c26 --- Comment #26 from Udo Lubich <bugzilla@lubich.com> --- ... and the kernel 5.3.18-lp152.69 also starts with this option. I probably had a typo on my first test. So ... with "intel_iommu=off" it works now. greetings Udo -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c27 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #27 from Takashi Iwai <tiwai@suse.com> --- (In reply to Udo Lubich from comment #26)
... and the kernel 5.3.18-lp152.69 also starts with this option. I probably had a typo on my first test. So ... with "intel_iommu=off" it works now.
OK, then your case is likely the bug 1184585. I'm building a test kernel with the reverts of a few iommu-related patches in OBS home:tiwai:bsc1184585 repo. It'll be available later (after an hour or so) at: http://download.opensuse.org/repositories/home:/tiwai:/bsc1184585/standard/ Please check it and verify whether it boots without the boot option workaround. Note that this is also a kernel with an unofficial key, so the Secure Boot won't work. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c28 --- Comment #28 from Udo Lubich <bugzilla@lubich.com> --- Created attachment 848271 --> http://bugzilla.opensuse.org/attachment.cgi?id=848271&action=edit System-Info -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c29 --- Comment #29 from Udo Lubich <bugzilla@lubich.com> --- (In reply to Takashi Iwai from comment #27)
(In reply to Udo Lubich from comment #26)
... and the kernel 5.3.18-lp152.69 also starts with this option. I probably had a typo on my first test. So ... with "intel_iommu=off" it works now.
OK, then your case is likely the bug 1184585.
I'm building a test kernel with the reverts of a few iommu-related patches in OBS home:tiwai:bsc1184585 repo. It'll be available later (after an hour or so) at: http://download.opensuse.org/repositories/home:/tiwai:/bsc1184585/standard/
Please check it and verify whether it boots without the boot option workaround. Note that this is also a kernel with an unofficial key, so the Secure Boot won't work.
Hi Takashi, I have now installed the provided kernel and the system starts without the option "intel_immo = off". Thanks for your work. What is Suse doing now? I wish a nice evening. greetings Udo -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c30 --- Comment #30 from Diedrich Ehlerding <diedrich.ehlerding@t-online.de> --- (In reply to Takashi Iwai from comment #27) Hi Takashi,
I'm building a test kernel with the reverts of a few iommu-related patches in OBS home:tiwai:bsc1184585 repo. It'll be available later (after an hour or so) at: http://download.opensuse.org/repositories/home:/tiwai:/bsc1184585/standard/
Please check it and verify whether it boots without the boot option workaround.
This kernel (5.3.18-default.69.1) bootson my laptop, but I need intel_iommu=off I do not know what iommu=off means - should I use this kernel, or should I revert to kernel -66? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c34 --- Comment #34 from Howard Moreland <hrm_sfo@sonic.net> --- (In reply to Takashi Iwai from comment #23)
Can anyone test the kernel in OBS Kernel:openSUSE-15.2 repo, just to be sure? http://download.opensuse.org/repositories/Kernel:/openSUSE-15.2/standard/
It's signed with an unofficial key, hence it won't work with Secure Boot.
I downloaded kernel-default-5.3.18-lp152.199.1.gfe68bba.x86_64.rpm from http://download.opensuse.org/repositories/Kernel:/openSUSE-15.2/standard/x86... but installing with YaST gave the error: "Package /Storage/Downloads/kernel-default-5.3.18-lp152.199.1.gfe68bba.x86_64.rpm could not be installed." Was that the right file to try? Thanks -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c36 --- Comment #36 from Howard Moreland <hrm_sfo@sonic.net> --- (In reply to Takashi Iwai from comment #35)
For the people who can boot with intel_iommu=off boot option, please go to bug 1184585. The culprit was identified and the test fix kernel is being built there.
If your machine doesn't boot with intel_iommu=off boot option, this must be a different bug, and we'd like to see whether other options make boot forward (even if not fully functional). If that's the case, please speak up.
My ThinkPad X390 does boot kernel-default 5.3.18-lp152.69.1 with intel_iommu=off boot option. The test fix kernel of bug 1184585 boots without any iommu option. Thanks, Howard -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c37 --- Comment #37 from Bill Wayson <bill_wayson@yahoo.com> --- (In reply to Takashi Iwai from comment #35)
For the people who can boot with intel_iommu=off boot option, please go to bug 1184585. The culprit was identified and the test fix kernel is being built there.
If your machine doesn't boot with intel_iommu=off boot option, this must be a different bug, and we'd like to see whether other options make boot forward (even if not fully functional). If that's the case, please speak up.
I'm with this bug. The intel_iommu=off boot option does not help me. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c39 --- Comment #39 from Gordon Dickens <gordon@dickens.com> --- The intel_iommu=off boot option worked to boot my laptop. So, I am with bug 1184585. FYI, Gordon -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184575 http://bugzilla.opensuse.org/show_bug.cgi?id=1184575#c45 Nikolai Nikolaevskii <kaykaykay123@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kaykaykay123@gmail.com --- Comment #45 from Nikolai Nikolaevskii <kaykaykay123@gmail.com> --- (In reply to Takashi Iwai from comment #6)
OK, then could you keep nomodeset boot option, but remove "splash=silent" and "quiet" options? This should show more kernel messages, at least.
If still nothing shown, try to boot with earlyprintk=efi option in addition.
Parameter "earlyprintk=efi" is not available anymore, neither for 5.3 kernel: https://www.kernel.org/doc/html/v5.3/admin-guide/kernel-parameters.html , nor for the latest: https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html . -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com