U4 keeps crashing when I'm away

[gtwundke]

Hi all,
Three weeks ago I was interstate for a week, and came back to find my U4 running but non-responsive. Looking at the recordings, this seems to have happened on (I think) the Wednesday evening. Unfortunately I didn't think to look at the logs to see what had happened (it was a long week). I have debug logging on, but they automatically get wiped after a few days (using the inbuilt log cleaning mechanism).

I was again away this last week, and came home on Friday evening to this time find my U4 stuck on "Booting..." on the LCD. I've just had a look at the logs, and it's my old friend the "no framebuffer available" issue (I've had this very occasionally for a while now), happening since Wednesday morning. Given that this issue caused 6 new log files to be written every 5 minutes (3 debug logs, 3 crash logs), I now have 4145 log files sitting on my hard drive!

So, a different issue to last time, but again 3 or so days of missed recordings, which is... unfortunate.

My U4 is set up to go into deep standby 30 minutes after going into standby, so it's generally always waking up from that state.

I'll attach the last good debug log, which probably won't provide any helpful details as I think it all shut down cleanly, and a crash log. Perhaps it can shed some light on what's going on?

I really wish I'd grabbed the logs from a few weeks ago, but that ship has sailed. I'm away again this coming week, so we'll see how many days of missed recordings I get this time!

(Edit: I've just realised that this should perhaps have gone into the Bug Reports section... feel free to move it if necessary).

Tim

[prl]

it's my old friend the "no framebuffer available" issue (I've had this very occasionally for a while now), happening since Wednesday morning.

I can't find any other posts from you about this.

So, a different issue to last time, but again 3 or so days of missed recordings, which is... unfortunate.

By "last time", do you mean: U4 crash playing H.265 files created using latest handbrake? If not, what do you mean by "last time", and in what way is it different?

It sounds a bit like a hardware issue to me, but it may be worth updating to the latest beta (beyonwiz-19.3 20190818) before pursuing that line. Since you're updating from a 17.5 firmware version to a 19.3 firmware version, you will be able to restore your settings after upgrading.

(Edit: I've just realised that this should perhaps have gone into the Bug Reports section... feel free to move it if necessary).

Done.

[gtwundke]

I can't find any other posts from you about this.

Nope, I've never bothered as it has happened pretty infrequently and never been a major issue as I've always been around to fix it at the time (and to be honest, sometimes the thought of having to write a post on here is just too much trouble). The "my old friend" was more just a personal reference. Note that I have however seen another reference to the issue somewhere on the forum, but it was a fair while ago and certainly doesn't seem to be common.

By "last time", do you mean: U4 crash playing H.265 files created using latest handbrake? If not, what do you mean by "last time", and in what way is it different?

I just meant different from a few weeks ago, where I came home and the machine had stopped responding while running.

It sounds a bit like a hardware issue to me, but it may be worth updating to the latest beta (beyonwiz-19.3 20190818) before pursuing that line. Since you're updating from a 17.5 firmware version to a 19.3 firmware version, you will be able to restore your settings after upgrading.

Ahh, I'm on the beta feed, but haven't had any indication about updating to 19.3. Looking at the thread it seems like it's manual update only. I'll give it a go, but it's only likely to be in a few weeks when I have more time (I have a few local modifications that I'll likely have to revert before performing the upgrade).

Tim

[Grumpy_Geoff]

it's my old friend the "no framebuffer available" issue (I've had this very occasionally for a while now), happening since Wednesday morning.

I can't find any other posts from you about this.

You'd have seen it from me though I've had it on our T2 and U4.
I believe it's a wonky (USB) driver sucking up the memory.
I defend against it now in my enigma2 pre-start script - viewtopic.php?f=47&t=13169#p178593

[prl]

Ahh, I'm on the beta feed, but haven't had any indication about updating to 19.3. Looking at the thread it seems like it's manual update only.

That's correct. You won't be offered an online update that will take you from a 17.5 firmware version to a 19.3 firmware version.

After the USB update, the U4 will automatically get online beta upgrades without needing to explicitly enable them.

[gtwundke]

You'd have seen it from me though I've had it on our T2 and U4.
I believe it's a wonky (USB) driver sucking up the memory.
I defend against it now in my enigma2 pre-start script - viewtopic.php?f=47&t=13169#p178593

Ahh, awesome Geoff (and adoxa)! I'll give that a go.

Tim.

[Grumpy_Geoff]

Well, lookie here...
I thought I'd take a look and see if any "no framebuffer" situations had occured recently, and look what I see for yesterday morning:

Code: Select all

In pre-start: 06/09/19 06:50:03
*** no framebuffer available (/dev/fb0).  Rebooting
In pre-start: 06/09/19 06:50:50
    Invoking AutoVisit.sh

As detected by this snippet from my /usr/bin/enigma2_pre_start.sh script -

Code: Select all

   
    echo "In pre-start: $(date +'%d/%m/%y %H:%M:%S')"

    # check for "no framebuffer available" error.  Ensure device file is present, else reboot.
    test -c /dev/fb0 || (echo '*** no framebuffer available (/dev/fb0).  Rebooting'; /sbin/reboot)

[Grumpy_Geoff]

Hi all,
Three weeks ago I was interstate for a week, and came back to find my U4 running but non-responsive. Looking at the recordings, this seems to have happened on (I think) the Wednesday evening. Unfortunately I didn't think to look at the logs to see what had happened (it was a long week). I have debug logging on, but they automatically get wiped after a few days (using the inbuilt log cleaning mechanism).

I thought the "functioning" log manager was fixed/introduced in the 19.3 series firmware. Are you sure the logs were wiped?

[prl]

I thought the "functioning" log manager was fixed/introduced in the 19.3 series firmware. Are you sure the logs were wiped?

That's what I thought, too. The log auto-cleanup appears to have been removed in 2012. It was added back into the Beyonwiz firmware repository in May. The most recent USB upgrade available for 17.3 firmware was released in Feb.

[Grumpy_Geoff]

I thought the "functioning" log manager was fixed/introduced in the 19.3 series firmware. Are you sure the logs were wiped?

That's what I thought, too. The log auto-cleanup appears to have been removed in 2012. It was added back into the Beyonwiz firmware repository in May. The most recent USB upgrade available for 17.3 firmware was released in Feb.

I think it's this commit from June, which the T/U-series didn't get until 1-Jul -
https://bitbucket.org/beyonwiz/easy-ui- ... 50345a878b
That appears to me to be the one that restores the invocation of LogManager.

[gtwundke]

I thought the "functioning" log manager was fixed/introduced in the 19.3 series firmware. Are you sure the logs were wiped?

The code was all there, just not being called, so I added the calls myself locally. I assume that's all the fix in 19.3 did as well.

So yeah, the logs are indeed gone.

Tim.

[Grumpy_Geoff]

I thought the "functioning" log manager was fixed/introduced in the 19.3 series firmware. Are you sure the logs were wiped?

The code was all there, just not being called, so I added the calls myself locally. I assume that's all the fix in 19.3 did as well.

Initially yes, but later adoxa extended the directory sizing limits and fixed some truncing and description issues -
viewtopic.php?f=47&t=13500#p180549

[prl]

I thought the "functioning" log manager was fixed/introduced in the 19.3 series firmware. Are you sure the logs were wiped?

That's what I thought, too. The log auto-cleanup appears to have been removed in 2012. It was added back into the Beyonwiz firmware repository in May. The most recent USB upgrade available for 17.3 firmware was released in Feb.

I think it's this commit from June, which the T/U-series didn't get until 1-Jul -
https://bitbucket.org/beyonwiz/easy-ui- ... 50345a878b

Yes, that's the one.