1

Iv'e installed an Ubuntu 18.04.4 server hosting docker containers and every few days the system crashes with the following entries in the system log:

Jun 16 08:52:13 shauls_home_server kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [containerd:1293]
Jun 16 08:52:41 shauls_home_server kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [containerd:1293]
Jun 16 08:52:45 shauls_home_server kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 22s! [rtorrent main:4407]
Jun 16 08:52:45 shauls_home_server kernel: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [runc:11721]
Jun 16 08:53:09 shauls_home_server kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [containerd:1293]
Jun 16 08:53:13 shauls_home_server kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 23s! [rtorrent main:4407]
Jun 16 08:53:13 shauls_home_server kernel: watchdog: BUG: soft lockup - CPU#10 stuck for 23s! [runc:11721]

I've already tried this solution: adding nouveau.modeset=0 to GRUB's Linux line.

And this: echo 20 > /proc/sys/kernel/watchdog_thresh, As suggested here.

Here is my Journalctl log just before the crash.

Any help on how I can figure out what's causing the issue will be appreciated.

11
  • I've updated the bios on Saturday, waiting to see if the issue happens again.
    – Shaulliv
    Jun 22, 2020 at 11:30
  • The system hanged over the weekend, but there is nothing in the log. I'm planing to wait for at least another week before I do anything.
    – Shaulliv
    Jun 28, 2020 at 11:38
  • The system still crashes but now without writing anything to the log. I also tried changing the GPU to an AMD card, without success.
    – Shaulliv
    Jul 7, 2020 at 10:13
  • Setting the threshold to 20 seems like it won't help if the complaints you're getting are for 22 or 23 seconds. FWIW I'm experiencing this problem as well and still seeking resolution.
    – pattivacek
    Sep 11, 2020 at 5:51
  • 1
    So, I found the problem. It was the ryzen c6 state bug. Since I wasn't able to mitigate the issue (despite the issue having workarounds) I just bought an Intel CPU (and compatible MOBO). The PC now ran for two weeks with no problems. If anyone is interested here's the bug report on the ryzen c6 state bug issue: https://bugzilla.kernel.org/show_bug.cgi?id=196683
    – Shaulliv
    Nov 1, 2020 at 13:44

2 Answers 2

0

BIOS

Gigabyte Technology Co., Ltd. A320M-H/A320M-H-CF

You have BIOS F40, dated 06/28/2019.

There's a newer BIOS available, F50, dated 11/28/2019, and can be downloaded here.

Note: Verify that I have the correct web page for your model #.

Note: Have good backups before updating the BIOS.

0

I have Xeon CPU and exact same problem that prevents it from booting into Linux Mint 20 or Windows 10. What helped me is going to

bios > Chipset > Advanced Power Management Configuration > CPU C State Control > enabled CPU C3 report and disabled CPU C6 report.

(i have a basic AMI bios, your path may vary)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.