1. Please describe the problem: Fedora 34 is totally unusable on an Acer Aspire 1 A114-32-P9MN (laptop), which probably does not have a quality BIOS implementation, but does work fine with Debian 11, Oracle Linux 8.4, etc. It only has problems with Fedora 34. The machine constantly reports "soft lockup" and something about a watchdog, which I know nothing about, really. The "soft lockup" occurs in many different modules and contexts (as indicated by the vast number of stack traces in the system logs). Booting from a live USB of Fedora 34, it often took more than 30 minutes to reach the initial desktop, whereas Oracle Linux boots in about 10 seconds and never causes a "soft lockup". I tried dozens of configuration adjustments to workaround the problem, but nothing improved. Considering the large number of user reports mentioning "soft lockup" on Fedora 34, it seems to me that something is seriously wrong with the build. For now, I have moved to Oracle Linux and will not install Fedora again on any machine. 2. What is the Version-Release number of the kernel: 5.13.4-200.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 didn't notice any problems on Fedora 32. After upgrading to Fedora 34 (5.13.4-200.fc34.x86_64), the machine is totally unusable because of constant "soft lockups" occurring in many different components and contexts. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Install Fedora 34 on an Acer Aspire 1 A114-32-P9MN, or just boot from a live USB. It will hang with soft lockups. 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``: Sorry, I switched to Oracle Linux, and am in the process of migrating all my machines. Fedora is not an option if it has such severe problems on basic commodity hardware. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No, just a plain live USB will trigger the problem at its fullest severity. 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. Sorry, the system has been wiped clean for an install of Oracle Linux, which works with no problems. But it any case, the machine was responding so poorly under Fedora 34 that it would have been nearly impossible to obtain the logs, even by simply copying them to a USB drive. The machine is entirely crippled under Fedora 34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.