Bug 1956924 - Soft lockups at boot time
Summary: Soft lockups at boot time
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 16:37 UTC by infrandomness
Modified: 2021-05-04 16:37 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
Kernel logs (124.65 KB, text/plain)
2021-05-04 16:37 UTC, infrandomness
no flags Details

Description infrandomness 2021-05-04 16:37:22 UTC
Created attachment 1779436 [details]
Kernel logs

1. Please describe the problem:
Something is going on with the linux kernel (probably a driver issue). When I boot my computer (running fedora 34, this also happened on 33) I get soft lockups that last at least ~22/~23 seconds 

2. What is the Version-Release number of the kernel:
5.11.17-300.fc34.x86_64

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 :
I have no idea, this first started happening at least a month or two before fedora 34's release date, I do not remember the kernel version


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
It happens almost everytime on an Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz


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``:
I do not wanna break my machine even more


6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

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.


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