[mythtv-users] failure to shutdown

Daryl McDonald darylangela at gmail.com
Mon Dec 14 23:09:13 UTC 2020


If/when this happens again what other logs might I look into?

On Mon, Dec 14, 2020 at 5:49 PM Stuart Auchterlonie <
stuarta at squashedfrog.net> wrote:

> On 14/12/2020 22:27, Daryl McDonald wrote:
> >
> >
> > On Mon, Dec 14, 2020 at 8:07 AM Stuart Auchterlonie
> > <stuarta at squashedfrog.net <mailto:stuarta at squashedfrog.net>> wrote:
> >
> >     On 14/12/2020 11:41, Stuart Auchterlonie wrote:
> >      > On 11/12/2020 17:43, Daryl McDonald wrote:
> >      >> I think it tried to shutdown at 00:52:01 and I intervened at
> >     03:41:52
> >      >> with a hard reboot. Seeing the machine still active I turned the
> >      >> monitor on to see the mobo logo. see paste:
> >      >> https://paste.ubuntu.com/p/XSC52khFjC/
> >     <https://paste.ubuntu.com/p/XSC52khFjC/>
> >      >> <https://paste.ubuntu.com/p/XSC52khFjC/
> >     <https://paste.ubuntu.com/p/XSC52khFjC/>>
> >      >>
> >      >> Would any other logs be helpful?  TIA  Daryl
> >      >>
> >      >
> >      > Only time i've ever seen that is when my DVB USB sticks
> >      > were dying :(
> >      >
> >      > Check dmesg / journal for relevant errors communicating with
> >      > devices.
> >      >
> >
> >     Just noticed your logs are dmesg, not seeing anything in there
> >     that shows errors on devices.
> >
> >     I was the behaviour that i have seen before, but there isn't any
> >     evidence to support it in those logs
> >
> >
> >     Regards
> >     Stuart
> >
> >     _______________________________________________
> >
> > OK so does that explain this:
> > aryl at trieli:~$ dmesg | grep -i journal
> > [    2.030456] systemd[1]: Listening on Journal Audit Socket.
> > [    2.030529] systemd[1]: Listening on Journal Socket (/dev/log).
> > [    2.030617] systemd[1]: Listening on Journal Socket.
> > [    2.036405] systemd[1]: Starting Journal Service...
> > [    2.237178] systemd[1]: Started Journal Service.
> > [    2.245224] systemd-journald[282]: Received client request to flush
> > runtime journal
> >
>
> no, what I had was horrible kernel oops from the usb subsystem
> because the device was locking up and being unresponsive.
>
> > and is this the response you expected from your suggestion? I use three
> > PCI and one PCIe cards. This happens only rarely at most, just a head
> > scratcher. Most of my box's unexplainable behavior stopped when I
> > replaced my power supply, it had melted insulation form an internal pyro
> > event, I'm surprised it worked at all. Thanks for the look Stuart.
> >
>
> Bad PSU's can cause all sorts of weird issues!
>
>
> Regards
> Stuart
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20201214/e97577e7/attachment-0001.htm>


More information about the mythtv-users mailing list