Bug 1710185 - kernel won't boot after update from 5.0.9 to 5.0.14
Summary: kernel won't boot after update from 5.0.9 to 5.0.14
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 30
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-15 04:49 UTC by Monkey Bizness
Modified: 2019-08-10 07:54 UTC (History)
20 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-10 07:54:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lspci -vvv (25.64 KB, text/plain)
2019-05-15 04:49 UTC, Monkey Bizness
no flags Details
Screenshot (417.87 KB, image/jpeg)
2019-05-20 17:45 UTC, morenstrat
no flags Details
Boot error fedora (5.29 MB, image/jpeg)
2019-05-20 18:00 UTC, Monkey Bizness
no flags Details
journal output with kernel 5.1.6-300 (80.63 KB, text/plain)
2019-06-07 09:41 UTC, Monkey Bizness
no flags Details

Description Monkey Bizness 2019-05-15 04:49:42 UTC
Created attachment 1568782 [details]
lspci -vvv

1. Please describe the problem:
I fresh installed Fedora 30 on a laptop ASUS UX433F (i7-8565U). and it works out of the box. After a dnf upgrade i can't boot on the new kernel.
During the boot sequence, i can see the grub menu. When selecting the entry, i just get a black screen. (even when removing the "rhgb quiet" opetions.
I can still boot with kernel 5.0.9-301 which is the version install by the installation iso.

2. What is the Version-Release number of the kernel:
appeared with 5.0.13 and still have it with 5.0.14.
version 5.1.1 from koji shows the same issue

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
appeared with the first update to 5.0.13

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Install Fedora 30
perform dnf upgrade
reboot on the new kernel.


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
yes it appears in rawhide too

6. Are you running any modules that not shipped with directly Fedora's kernel?:
no, this is a stock kernel + modules

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
I have absolutely no logs to show...

Comment 1 Sami Farin 2019-05-15 10:02:05 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

Comment 2 Monkey Bizness 2019-05-15 17:29:33 UTC
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...

Comment 3 Sami Farin 2019-05-16 07:36:55 UTC
Don't worry, let's just wait if someone reads these bug reports
https://bugzilla.redhat.com/show_bug.cgi?id=1710718

Comment 4 morenstrat 2019-05-20 17:36:40 UTC
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.

Comment 5 morenstrat 2019-05-20 17:45:05 UTC
Created attachment 1571346 [details]
Screenshot

Comment 6 Monkey Bizness 2019-05-20 17:58:21 UTC
I tried with the option used by m.orenstrat and i get the same result.
See attachment.

Comment 7 Monkey Bizness 2019-05-20 18:00:16 UTC
Created attachment 1571348 [details]
Boot error fedora

Comment 8 DualBoot 2019-05-20 19:34:48 UTC
  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,

Comment 9 Monkey Bizness 2019-05-23 21:34:32 UTC
After installation of the latest 5.0.17 , same issue. No change.

Comment 10 morenstrat 2019-06-06 21:37:37 UTC
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.

Comment 11 morenstrat 2019-06-06 21:38:02 UTC
Oh, BIOS version number is 304.

Comment 12 morenstrat 2019-06-06 21:45:47 UTC
> 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)

Comment 13 Monkey Bizness 2019-06-07 09:39:31 UTC
confirmed, kernel-5.1.6-300.fc30 seems to fix the issue.
I didn't need to update the bios firmware...

Comment 14 Monkey Bizness 2019-06-07 09:41:42 UTC
Created attachment 1578285 [details]
journal output with kernel 5.1.6-300

for analysis if needed. 5.1.6-300 seems to work

Comment 15 Monkey Bizness 2019-06-09 15:37:06 UTC
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.

Comment 16 morenstrat 2019-06-09 19:17:14 UTC
So what is your BIOS version now? I updated using System Setup and Asus EZ Flash 3. New version in 304.

Comment 17 Monkey Bizness 2019-06-09 22:05:02 UTC
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.

Comment 18 DualBoot 2019-06-10 16:07:32 UTC
  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,

Comment 19 Alex Meadows 2019-06-10 23:59:03 UTC
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.

Comment 20 Monkey Bizness 2019-06-11 06:20:51 UTC
So it looks like it was a bios issue, not the kernel.

Comment 21 DualBoot 2019-06-11 15:08:34 UTC
(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,

Comment 22 Monkey Bizness 2019-08-10 07:54:04 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.