[mythtv-users] a new type of error
Michael T. Dean
mtdean at thirdcontact.com
Fri Mar 9 11:52:39 UTC 2018
On 03/08/2018 06:31 PM, James Abernathy wrote:
> I’ve setup my mythtv backend to daily optimize and backup the
> database. I have it email me with the results. So when I don’t get
> the 2 emails at 7:35am each day, I go looking for problems. The system
> still records problems and the frontends work for viewing.
>
> What I’ve seen lately is I can’t ssh or login at the PC console of the
> backend, and I get errors on the console like:
> Mar 7 12:11:47 mythbuntu kernel: [317584.873671] NMI watchdog: BUG:
> soft lockup - CPU#4 stuck for 22s! [TFWWrite:25774]
> Mar 7 12:12:15 mythbuntu kernel: [317612.872998] NMI watchdog: BUG:
> soft lockup - CPU#4 stuck for 23s! [TFWWrite:25774]
> Mar 7 12:12:55 mythbuntu kernel: [317652.872033] NMI watchdog: BUG:
> soft lockup - CPU#4 stuck for 23s! [TFWWrite:25774]
> Mar 7 12:13:23 mythbuntu kernel: [317680.871359] NMI watchdog: BUG:
> soft lockup - CPU#4 stuck for 22s! [TFWWrite:25774]
>
> The Host name is mythbuntu. It’s a Ubuntu 16.04 system
>
> Once I reboot, the system works fine and I get my optimize emails
> after a short time. But a day or so later I notice this problem
> again. I have not changed anything, but I have done some updating
> using: apt update and apt upgrade.
>
> Any ideas??
Power issue? Unless it's a bug in a kernel or a misconfigured virtual
machine, it could be caused by anything from a failing CPU (not too
common) to a failing PSU (pretty common) or a failing motherboard
(generally having issues delivering power/providing a stable vcore).
Mike
More information about the mythtv-users
mailing list