Bug 1963316 - kernel 5.12.5 does not boot, freezes around 30 seconds after starting on a Lenovo T500
Summary: kernel 5.12.5 does not boot, freezes around 30 seconds after starting on a Le...
Keywords:
Status: CLOSED DUPLICATE of bug 1963782
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-22 08:44 UTC by Albert Flügel
Modified: 2021-05-31 08:02 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 11:31:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Log from journalctl -f, see comment #2 (17.92 KB, application/x-xz)
2021-05-22 12:23 UTC, Albert Flügel
no flags Details

Description Albert Flügel 2021-05-22 08:44:21 UTC
1. Please describe the problem:
See Subject. All Filesystems are LVM volumes

2. What is the Version-Release number of the kernel:
5.12.5

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 :
5.11 worked

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
install kernel 5.12.5
boot

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``:
Guess what. Installing warhide with these commands fails:
Downloading Packages:
(1/3): kernel-5.13.0-0.rc2.20210520gitc3d0e3fd4 778 kB/s | 302 kB     00:00    
(2/3): kernel-core-5.13.0-0.rc2.20210520gitc3d0 2.5 MB/s |  36 MB     00:14    
(3/3): kernel-modules-5.13.0-0.rc2.20210520gitc 2.2 MB/s |  33 MB     00:15    
--------------------------------------------------------------------------------
Total                                           4.5 MB/s |  69 MB     00:15     
warning: /var/cache/dnf/rawhide-2d95c80a1fa0a67d/packages/kernel-5.13.0-0.rc2.20210520gitc3d0e3fd41b7.21.fc35.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 9867c58f: NOKEY
...
The GPG keys listed for the "Fedora - Rawhide - Developmental packages for the next Fedora release" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.. Failing package is: kernel-5.13.0-0.rc2.20210520gitc3d0e3fd41b7.21.fc35.x86_64
...
Error: GPG check FAILED


6. Are you running any modules that not shipped with directly Fedora's kernel?:
not that i'm aware of

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.
No logs of the failing boot are written to disk

https://bugzilla.redhat.com/show_bug.cgi?id=1936996 sounds similar, but there we have 5.12.0 and allegedly this is fixed.

Comment 1 Albert Flügel 2021-05-22 12:20:57 UTC
Found out now:
The machine freezes, when gdm starts. When i disable gdm, the laptop boots into the text consoles.
When i systemctl start gdm there, i see shortly a graphical screen with the usual rotor in the middle, but after about 2 seconds the freeze is there.
In the text console i can start lightdm, that i tried to run instead. i can't login with lightdm, this thing and "deepin" seems to be a single big bug by the way.
However, the laptop does not freeze.
The logs from the time i start gdm, as far as the system still manages to write them to disk, can be found in the attached file.
And i have a new issue with fonts in a program, that works since decades. For this i'll open the next separate bug.

oh. my. god.

Comment 2 Albert Flügel 2021-05-22 12:23:09 UTC
Created attachment 1785787 [details]
Log from journalctl -f, see comment #2

Comment 3 Albert Flügel 2021-05-24 21:05:54 UTC
Same issue with 5.12.6-200

Comment 4 Albert Flügel 2021-05-24 21:10:00 UTC
Still today trying to install the rawhide kernel fails at the gpg check. Trying with --nogpgcheck now :-(

Comment 5 Albert Flügel 2021-05-24 21:23:52 UTC
5.13.0-0.rc2.20210521git79a106fc6585.22.fc35.x86_64 seems to boot and to survive the start of gdm.
However the test interval is too short that i'd consider this a reliable experience.
And i have noticed, that 5.12.5-200 is released for the Fedora updates repo, though it is making severe problems !?!

Comment 6 Justin M. Forbes 2021-05-24 21:32:31 UTC
It also fixes severe problems for some people. I made a call, as it seems to fix more than it breaks.  1 of the problems that it created is fixed in 5.12.6, I am still not sure on this one though. It appears that a patch was pulled back and missing a dependent patch.

Comment 7 please delete this account 2021-05-25 09:34:48 UTC
I've got a similar effect with an old hp compaq 6910p

unfortunately I can't confirm it's with 5.12.6

booting to former vmlinuz-5.11.21-300.fc34.x86_64 -> no problem

booting to runlevel 3 of vmlinuz-5.12.5-300.fc34.x86_64 or vmlinuz-5.12.6-300.fc34.x86_64 -> no problem

booting to graphical desktop of vmlinuz-5.12.5-300.fc34.x86_64 or vmlinuz-5.12.6-300.fc34.x86_64 -> freezes after 2-5 secs
- entering cryptfs password works without any trouble
- graphical desktop inc. background starts, but after a short moment e.g moving cursor -> freeze
- unfortunately no keybord or touchpad any mor, so I'm not able to switch to a console
- no problem report is created
- need to turn of power 

booting to runlevel 3 and then telinit 5 -> freeze

in contrast the 5.12.6 works on a new acer aspire 5 without any problems, as far as I noticed

I'll wait for 5.12.7 and will provide a feedback, if 5.12.7 solves the problem

if someone needs further information, feel free to contact me

Comment 8 Justin M. Forbes 2021-05-25 11:31:01 UTC

*** This bug has been marked as a duplicate of bug 1963782 ***


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