Created attachment 1868180 [details] kernel log (probably from successful boot) 1. Please describe the problem: I use Fedora 36 KDE on a Thinkpad T580 with Linux kernel 5.17.0-300.fc36.x86_64. The CPU I have is an i5-7300. The Wifi card I have is "Intel Corporation Wireless 8265 / 8275 (rev 78)". If I reboot my system, the next time I boot up and log in, 1 or 2 minutes after logging in I get a full system freeze, and I have to poweroff by holding the power button. If I shut down and power on without rebooting, I don't get the freeze. Right before the freeze, I get a notification message in KDE about the network being disconnected or something like that. 2. What is the Version-Release number of the kernel: 5.17.0-300.fc36.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 didn't have the problem in Fedora 35. I noticed this first on Fedora 36, kernel 5.17 rc7 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes, by rebooting and logging in, and waiting a minute. 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``: N/A 6. Are you running any modules that not shipped with directly Fedora's kernel?: vhba (cdemu), droidcam, openrazer 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. Attached is kernel log but it is probably from a successful boot. I think the logs from the crashed boots were not saved.
Actually, my initial description was wrong. it happens every other boot.
This bug report seems like the issue: https://bugzilla.redhat.com/show_bug.cgi?id=2066304 , so might not be kernel related.
*** This bug has been marked as a duplicate of bug 2070130 ***