[mythtv-users] a new type of error

Anthony Giggins seven at seven.dorksville.net
Fri Mar 9 13:00:39 UTC 2018


On 9 March 2018 at 09:31, James Abernathy <jfabernathy at gmail.com> 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??
>
> Jim Abernathy
> jfabernathy at gmail.com
>
>
>
Jim try installing mcelog (sudo apt-get install mcelog)  and check
/var/log/mcelog after the error has occurred.

you should also see those log errors in you /var/log/syslog and dmesg which
might give you more detail

I dont think you've mentioned what hardware this is running on?

Cheers,

Anthony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20180309/c0a3cae3/attachment.html>


More information about the mythtv-users mailing list