Forums

Hi

After upgrading my Vu+Duo to OpenPLi 4 on 2013-12-28 I had a number of crashes, mostly when timer recording one channel and viewing another channel at the same time.

Software updating the receiver seems to have reduced these crashes.

I also had a bunch of empty enigma crash log files, not attached.

All segfaults. Is this a VU+ Duo with a repaired power supply?

I have replaced the failing capacitor, yes.

But it was running without these problems on OpenPLi 3 before upgrade.

Did you upgrade recently before you flashed OpenPLi 4?

No, but I updated OpenPLi 3 some time (days, or a week or so) before the upgrade.

Another crash attached (10 minutes ago), recording on one HD channel and viewing another HD channel.

Segfault.

I have crash when swap PiP. same thing on yellow button or with 0

Action -> ColorActions yellow
Traceback (most recent call last):
File "/usr/lib/enigma2/python/mytest.py", line 191, in processDelay
callback(*retval)
File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1800, in extensionCallback
File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 1928, in swapPiP
File "/usr/lib/enigma2/python/Screens/ChannelSelection.py", line 1700, in setCurrentServicePath
TypeError: hew_setHistoryPath() takes exactly 1 argument (2 given)
(PyObject_CallObject(<bound method Session.processDelay of <__main__.Session instance at 0x1b76e90>>,()) failed)
getResolvedKey config.plugins.crashlogautosubmit.sendAnonCrashlog failed !! (Typo??)
getResolvedKey config.plugins.crashlogautosubmit.addNetwork failed !! (Typo??)
getResolvedKey config.plugins.crashlogautosubmit.addWlan failed !! (Typo??)
]]>
</enigma2crashlog>

This might have been resolved one of the last days. Please update and try again.

No.

plugin SoftcamSetup(autocam mod),delete this plugin.

thanks, now works ok! any image or plugin fix for this?

Sorry did not understand exactly what you are interested in?

I did a complete reflash with the latest nightly today, and had a crash when restarting the receiver.

Also noticed something peculiar with udhcpd running the command 'ps', see attached image.

Earlier when I upgraded from OpenPLi 3 to OpenPLi 4 I noticed something similiar, but for smbd. (see attached image 2)

PC: 76b08b10
00000000 00000001 df3dbe82 df3dbe82
0094ce28 0000000a 00000000 756ac62a
ff716e6d 769a83e8 00000001 00000000
7a20656c 65707061 6f6c2072 72656461
7f8710e0 7f871158 007a4550 00001e04
000001e9 0000000a 005c0b9c 0094ccf4
00000000 76b08b04 fffffffd 00000000
00644860 7f871080 ffffffff 0048b278

???

That's a segfault. I thought you'd recognise it.

My Vu+Duo is not playing nice now, I had some timer recordings set up for yesterday evening and this afternoon, but

at 23:21 yesterday it crashed an left a more or less empty log file. (attached file 1)

This afternoon it crashed again close to the end of a recording (attached file 2).

As a bonus I found some more peculiar stuff running the command 'ps' (attached image).

What to do now, try to go back to OpenPLi 3?

I had several crashes with Open PLi 4.0 on my Duo aswell, so I went back to PLi 3.0 which sees to be stable right now.

I tested the 4.0 builds from 2nd and 1st january and the build from 25th december, of which all crashed at some point.

One incomplete crashlog and one segfault.

Is there no information to get from the stack trace (I think it's a trace)?

Neither of the crashlogs above contain a backtrace.

Ok, thank's for the explanation, I'm back at OpenPLi 3.0 now.