[VU+ Ultimo4K] 5.3.030 crashing. Fixed in 5.3 032

[adm]

Nasty looking crash after couch flashing 5.3.030 and restoring settings from 5.3.029

The box boots up ok until the programme info bar appears and then crashes before live tv is shown.

The GUI restarts and the box is ok, but if I reboot it crashes again with the same sequence. Same crash starting from deep standby.

ET10K couch flashed ok.

Tried re-flashing, no better.

ET10K
Software update from 29 to 30 - no crashes

Couch flash from 29 to 30 with settings and plugin restore from 29 - no crashes (My own manual 29 backup and not one produced as a result upgrade/flash)

 

[twol]

Is this commit a pure coincidence, or......

https://github.com/OpenPLi/enigma2/commit/e1923b7c0d0304fe76218a13bf2d968fc2960bcd

No we don‘t have it on ViX.... but it kind of fits - but why does 019 work?

 

[BrianTheTechieSnail]

I'm assuming @BrianTheTechHead's box is a zgemma

Correct, Zgemma H7S.

 

[ccs]

ET10K
Software update from 29 to 30 - no crashes

Couch flash from 29 to 30 with settings and plugin restore from 29 - no crashes (My own manual 29 backup and not one produced as a result upgrade/flash)

I know, just like mine, mentioned in post #1.

Any Ultimo4k owners (or H7S's) out there now running 5.3.030?

 

[Willo3092]

I've just software updated a H7C from 5.3.027 to 5.3.030.

 

[abu baniaz]

Is this commit a pure coincidence, or......

https://github.com/OpenPLi/enigma2/commit/e1923b7c0d0304fe76218a13bf2d968fc2960bcd

That commit was added to fix this crash reported by IMS, which seems to be the same as the one being reported.

Backtrace:
/usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0xA4DDC]
/lib/libc.so.6(__default_rt_sa_restorer) [0xB6C4FC60]
/lib/libc.so.6(gsignal) [0xB6C4E94C]
/lib/libc.so.6(abort) [0xB6C4FDC4]
-------FATAL SIGNAL

Reason was

This issue appears with the new "speedup" from netifaces.

Parsing the output from ip/ifconfig commands didn't show that issue.

Why it appears now? I have no idea, but the flow is now the same as before, now we are starting some services earlier / faster.

If creating an std::string and passing the const c_str to enigma fixes the issue that is enough for me.

 

[thecaretaker]

Same problem here. Here is my log...

View attachment Enigma2_crash_2020-05-19_04-50-51.log

 

[ccs]

That commit was added to fix this crash reported by IMS, which seems to be the same as the one being reported.

Backtrace:
/usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0xA4DDC]
/lib/libc.so.6(__default_rt_sa_restorer) [0xB6C4FC60]
/lib/libc.so.6(gsignal) [0xB6C4E94C]
/lib/libc.so.6(abort) [0xB6C4FDC4]
-------FATAL SIGNAL

Reason was

This issue appears with the new "speedup" from netifaces.

Parsing the output from ip/ifconfig commands didn't show that issue.

Why it appears now? I have no idea, but the flow is now the same as before, now we are starting some services earlier / faster.

If creating an std::string and passing the const c_str to enigma fixes the issue that is enough for me.

So you reckon this commit may well fix my (and other posters) crashes?

EDIT:

The PLi discussion mentioned this....

Before we never had the chance to see that error, simply because we where starting OWIF toooooooooo late.

Now OWIF starts tooooooooo fast

so I deleted OWIF and the box no longer crashes.

 

[ccs]

so I deleted OWIF and the box no longer crashes.

This is NOT a solution, I was just testing out a theory.

 

[twol]

This is NOT a solution, I was just testing out a theory.

Well the OpenPli change has been added to ViX so next build ..............................

 

[ccs]

Well the OpenPli change has been added to ViX so next build ..............................

Good to hear, I enjoy the PLi forum, probably for the wrong reasons , but it's also a good memory test, and that commit somehow rang the proverbial bell.

 

[db49er]

VU+Solo and Uno

View attachment Enigma2_crash_2020-05-19_15-38-53.logView attachment Enigma2_crash_2020-05-18_20-13-00.log

Hope these may be helpful

 

[daz450]

I am having issues with box booting then restarting a few times before I can even change the channel after a few restarts it works ok , I am using 0.29

 

[rte]

Updating to 5.3.030 caused crashing with log when starting but continued starting and seemed to work alright with settings from 5.3.029. Updating showed a warning at first and so it is. Crash but goes on starting alright.
I flashed back to 5.3.029 with settings from 5.3.029, no crashing. I keep that, so far.
Will there be any remedy in the future updates?

 

[abu baniaz]

Of course there will be a fix. We have just run a Dev image to test the "fix". Once that is confirmed fine, the 5.3 031 Release image will be run. Not all boxes have this issue.

Sorry for the inconvenience.

 

[lincsat]

I noticed my Ultimo4K did the same when I updated to 30, I've not rebooted since so haven't noticed any further GUI restarts. If you still need logs, I can try a reboot but can't do it until later in the Day.

 

[ccs]

There are plenty of logs submitted, all exactly the same, so I wouldn't bother unless you think your crash is different.

A fix should be in the next release.

 

[Sicilian]

Build 5.3.031 is running, most likely be completed tomorrow.

 

[BrianTheTechieSnail]

I updated to 5.3.031 and it still seems broken to me.
It crashed on first boot after upgrade but not on a second (manually requested) one but it did crash on a third.
Maybe I upgraded too soon?
View attachment Enigma2_crash_2020-05-20_15-34-54.log
View attachment Enigma2_crash_2020-05-20_15-37-36.log

 

[Sicilian]

I updated to 5.3.031 and it still seems broken to me.
It crashed on first boot after upgrade but not on a second (manually requested) one but it did crash on a third.
Maybe I upgraded too soon?

No idea what you have upgraded to! 5.3.031 hasn't even completed building and has not even been uploaded! You must be on a different timezone ahead of us mere mortals