Bug 1710185
| Summary: | kernel won't boot after update from 5.0.9 to 5.0.14 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Monkey Bizness <monkey> | ||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 30 | CC: | airlied, alexmeadows, bskeggs, guy.carre+redhat, hdegoede, hvtaifwkbgefbaei, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, m.orenstrat, steved | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2019-08-10 07:54:04 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Monkey Bizness
2019-05-15 04:49:42 UTC
Fedora 29, kernel 5.0.14 [ 1.328952] Run /init as init process /init: error while loading shared libraries: libsystemd-shared-239.so: cannot open shared object file: No such file or directory [ 1.330947] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [ 1.332430] CPU: 1 PID: 1 Comm: init Not tainted 5.0.14-200.fc29.x86_64 #1 [ 1.333416] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20180724_192412-buildhw-07.phx2.fedoraproject.org-1.fc29 04/01/2014 If there is something i can do to gather information or test, just tell me. I'll be happy to help. It bothers me to not have any log to show... Don't worry, let's just wait if someone reads these bug reports https://bugzilla.redhat.com/show_bug.cgi?id=1710718 I think I have the same problem monkey has. My laptop is an Asus Zenbook UX433FN - The last kernel that boots is 5.0.13. 5.0.14 and 5.0.16 do not boot. I removed "rhgb quiet" and added "nomodeset acpi=off" to the kernel command line and I can see that the kernels freeze at "Freeing unused kernel image memory: 2204K". I have the same problem with the latest Ubuntu version (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826065) and there are other people affected, too. Created attachment 1571346 [details]
Screenshot
I tried with the option used by m.orenstrat and i get the same result. See attachment. Created attachment 1571348 [details]
Boot error fedora
Hello, just to confirm the problem on my side with Fedora 30 Kernel 5.0.16. With my Asus Laptop ZenBook Pro 14 UX433FN Intel Core i7-8565U CPU @1.80GHz x 8 Graphic card Intel HD Graphics (Whiskey Lake 3x8 GT2) I could install Fedora 30 with a live USB which embedded kernel 5.0.9-301, reboot and see everything is fine. But if I update the Kernel to 5.0.16-300 and reboot my laptop stick after Grub menu. For information I have the same problem with Ubuntu 18.10 : Installing with USB it is Ok but if I update to kernel 4.18.20 I goes into the same problem. And trying with live USB Ubuntu 19.04 gone stuck directly after the Grub menu. Disabling Fast Boot and/or Secure Boot do not change anything. I tried acpi=off too like m.orenstrat and got the same ending. Regards, After installation of the latest 5.0.17 , same issue. No change. There is a new BIOS version out for the UX433FN and that seems to fix the problem. I can not boot kernel-5.1.6-300.fc30 without any problems. Oh, BIOS version number is 304. > There is a new BIOS version out for the UX433FN and that seems to fix the > problem. I can not boot kernel-5.1.6-300.fc30 without any problems. "I can now boot" is what I mean - sorry for the typo (In reply to morenstrat from comment #10) confirmed, kernel-5.1.6-300.fc30 seems to fix the issue. I didn't need to update the bios firmware... Created attachment 1578285 [details]
journal output with kernel 5.1.6-300
for analysis if needed. 5.1.6-300 seems to work
This is strange, it worked for about a day and now i can't boot with kernel 5.1.6-300.... The only thing i did was fwupdmgr in order to be sure my firmware was at the latest level. Even by reinstalling the kernel packages, it doesn't work anymore. So what is your BIOS version now? I updated using System Setup and Asus EZ Flash 3. New version in 304. it was in version 302. fwupd didn't have the new 304 version available. Updating using the Asus EZ Flash 3 utility to version 304 fixes the issue. I can now boot. Hello, I just upgraded my BIOS to 304 version and now it's working as expected. I could upgrade the linux kernel to the latest version provided by Fedora repository and reboot in a normal way. I have also tested with Ubuntu 19.04 live usb and now it is working as expected. Regards, Just wanted to confirm as well that once upgrading the BIOS to 304 and now am able to boot into the latest linux kernal in Fedora stable with my Asus Laptop ZenBook Pro 14 UX433FN. So it looks like it was a bios issue, not the kernel. (In reply to Monkey Bizness from comment #20) > So it looks like it was a bios issue, not the kernel. Not sure, because it was working with initial kernel from Fedora live usb and it was working too with Ubuntu 18.04 kernel 4.15. Regards, After some time and many kernel updates, i don't have the issue anymore. Fixed with bios 304 and kernel-5.1.6-300.fc30 and higher. |