+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: DotNet CPU Lockups (/t-dotnet-cpu-lockups)
DotNet CPU Lockups - muddy - 2023-10-22
I've been troubleshooting an ongoing issue for months now and finally asking for some areas to investigate that maybe I have not thought about.
Jellyfin was on my old Dell Poweredge server running Ubuntu Server and ran without issue other than it was consuming a lot of the box.
I had upgraded my machine and took the hardware I replaced and made a new Jellyfin server with it, migrated the data over and it seemed to work fine.
However since moving to Arch and the X470 Motherboard with AMD 1800X CPU with Nvidia GTX1050 for transcoding it now locks up with
Code:
jellyfin login: [xxxx.xxxx] watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [.NET ThreadPool:xxxxx]What I'm trying to determine is where to start as the logs have been absent of anything that looks useful.
I don't have crash dumps to review since it's not creating them.
Any ideas where to look would be great, thanks.
-Muddy
RE: DotNet CPU Lockups - Deleted User - 2023-10-22
i think you will find this is not from or due to jellyfin and as such you would find better answers external to jellyfin
such as this link - https://askubuntu.com/questions/1264859/watchdog-bug-soft-lockup-cpu6-stuck-for-23s
(was just a related search result)
https://www.google.com/search?q=ubuntu+watchdog%3A+BUG%3A+soft+lockup
RE: DotNet CPU Lockups - bitmap - 2023-10-23
On the off chance you believe it's related to Jellyfin (not been reported before that I've seen), you can turn on debug logging but it seems like that's a long shot...
RE: DotNet CPU Lockups - muddy - 2023-10-23
I "think" it's related to the C6 State.. Have some fix applied will see if it holds and update once I have some data.
RE: DotNet CPU Lockups - TheDreadPirate - 2023-10-23
Make sure your BIOS are recent. I remember when I was still running a 1700X that it was recommended to turn off those low power states in the BIOS until it was eventually fixed in an AGESA/BIOS update.