Bug 2404521
| Summary: | Consistent watchdog: BUG: soft lockup on kernels >= 6.16.8 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chloe Surett <cj> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 42 | CC: | acaringi, adscvr, airlied, dreamsky2003, hans, hpa, josef, kernel-maint, linville, masami256, mchehab, ptalbert, steved, suraj.ghimire7 | ||||
| Target Milestone: | --- | Keywords: | Desktop, Regression | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | --- | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2026-06-09 13:18:03 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Chloe Surett
2025-10-16 17:27:14 UTC
Created attachment 2109975 [details]
Kernel log
The crash was also observed with the nouveau drivers as well. I have just tested with a clean KDE 42 install with no Nvidia drivers and only having java to trigger it. I wasn't able to grab the logs but it seems to be the same behavior. Observed same all-core lockup on an AMD system with integrated graphics card. OpenJDK 21 from official Fedora repo. Running Minecraft server. From journalctl it appears that a core trapped into hard lockup first and other cores soon trapped into soft lockup after the first core. Everything looks fine without starting Minecraft server, but the lockup is triggered every time after the server being started and running for 1-2 minutes. On 6.15.8 no lockup observed, but on 6.16.8 and 6.16.12 the problem is consistent. Not tested on other kernels. No additional module is inserted manually, but according to one of my friends who tried to find out why there might be some BPF module registered by the JDK(or audit) to monitor performance of the server. System info: CPU: AMD Ryzen 7 7700X GPU: Integrated Motherboard: TUF B650-PLUS WiFi (In reply to Yan Pan from comment #4) > Observed same all-core lockup on an AMD system with integrated graphics > card. OpenJDK 21 from official Fedora repo. Running Minecraft server. > From journalctl it appears that a core trapped into hard lockup first and > other cores soon trapped into soft lockup after the first core. Everything > looks fine without starting Minecraft server, but the lockup is triggered > every time after the server being started and running for 1-2 minutes. > On 6.15.8 no lockup observed, but on 6.16.8 and 6.16.12 the problem is > consistent. Not tested on other kernels. No additional module is inserted > manually, but according to one of my friends who tried to find out why there > might be some BPF module registered by the JDK(or audit) to monitor > performance of the server. This seems to match up exactly with what I'm experiencing. I'll try testing in a vm tomorrow. So it's possible that this is related to the spark mod. I was able to reproduce it in a VM as well. https://github.com/lucko/spark/issues/530 and has been reported to upstream. https://lore.kernel.org/stable/CAHPNGSQpXEopYreir+uDDEbtXTBvBvi8c6fYXJvceqtgTPao3Q@mail.gmail.com/T/#u This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. 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 '42'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 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 42 entered end-of-life (EOL) status on 2026-05-27. Fedora Linux 42 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |