Watchdog: BUG: soft lockup - CPU#8 stuck for 23s

Getting Help
1

restic was running successfully on my machine for several months now, but recently it started causing problems. The last backup is running now for 80h and takes 100% CPU ( normally it is a very small local backup taking less than a minute).
It does not even react to kill command.
Below is message from dmesg.
What could be the reason?

restic 0.16.2, CentOS 8 stream.

[1130511.920240] watchdog: BUG: soft lockup - CPU#8 stuck for 23s! [restic:3883349]
[1130511.920292] CPU: 8 PID: 3883349 Comm: restic Kdump: loaded Tainted: P OEL --------- - - 4.18.0-521.el8.x86_64 #1
[1130539.920237] watchdog: BUG: soft lockup - CPU#8 stuck for 23s! [restic:3883349]
[1130539.920269] CPU: 8 PID: 3883349 Comm: restic Kdump: loaded Tainted: P OEL --------- - - 4.18.0-521.el8.x86_64 #1
[1130552.609243] CPU: 8 PID: 3883349 Comm: restic Kdump: loaded Tainted: P OEL --------- - - 4.18.0-521.el8.x86_64 #1
[1130579.920234] watchdog: BUG: soft lockup - CPU#8 stuck for 22s! [restic:3883349]
[1130579.920270] CPU: 8 PID: 3883349 Comm: restic Kdump: loaded Tainted: P OEL --------- - - 4.18.0-521.el8.x86_64 #1
[1130607.920231] watchdog: BUG: soft lockup - CPU#8 stuck for 22s! [restic:3883349]
[1130607.920269] CPU: 8 PID: 3883349 Comm: restic Kdump: loaded Tainted: P OEL --------- - - 4.18.0-521.el8.x86_64 #1

2

That looks like a hardware or kernel issue - maybe your disk is suffering from IO problems causing the messages.

Regardless, this isn’t a restic issue (even though I can see how you would think it is, seeing as running restic is triggering the issue) but an underlying system issue you’ve got.

1 Like