27 replies to this topic

[ghuss]

OpenPLi 9.1 Crash

 

Crash Log

 

" stbmodel=duo2

stbmodel=dm8000

kernelcmdline=libata.force=1:1.5Gbps bmem=192M@64M bmem=384M@512M memc1=788M ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw rootflags=sync

nimsockets=NIM Socket 0:

imageissue=openpli 9.1-release %h

 

 

PC: 0049cfa4

    00000000 00000001 00000000 00000001

    00000000 7f8f8468 00000000 7f8f83bc

    71e86b90 58ac43e7 00000004 75f89fb3

    76ced498 ffffffff 0000000c 00700000

    00e44f00 00e41988 00e29668 00000000

    00780288 746883e8 76ce27fc 76cf06f4

    0000001c 76794b00 00000000 00000000

    76ec7af0 7f8f8300 00000000 0049cfa0

Backtrace:

/usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x46D3B0]

/usr/bin/enigma2(_ZN11eDVBService10isPlayableERK17eServiceReferenceS2_ [0x49CFA4]

/usr/bin/enigma2(n/a) [0x5C3DC8]

/usr/lib/libpython3.9.so.1.0(n/a) [0x76CF07D0]

-------FATAL SIGNAL 11"

 

 

 

[WanWizard]

That looks like something in your channel list that isn't UTF8.

[ghuss]

Thanks

 

When the receiver wakes up from standby or deep standby for timer recording it crashes and continues to restart and crashes until the time of the timer is over, then it restarts normaly. "See crash log up"

[WanWizard]

A developer will have to look at this.

[littlesat]

Can you confirm which box you’re using and on which device (interval harddisk or mounted drive?) you try to put the recoding on..?
It looks like vu+ duo2… old box, maybe out of memory ?

Edited by littlesat, 1 January 2025 - 18:17.

[ghuss]

Thanks

 

yes vu+ duo2, I am trying find  VU+ Duo 4K SE  DVB-S2X FBC / DVB-T2. 

 

Recording on internal SSD drive for many years, never had such problem

 

[ghuss]

My box is: Vu+ Duo 2 

VUplus Duo2 With  two tuners DVB-S 

Edited by ghuss, 5 January 2025 - 23:59.

[ricki]

OpenPLi 9.1 release crash when the box recorded I tried to do an update.

Attached Files

•  enigma2_crash_1736152032.log   19.99KB   4 downloads
•  enigma2_crash_1736152055.log   767bytes   3 downloads

Edited by ricki, Yesterday, 11:48.

[WanWizard]

OpenPLi 9.1 release crash when the box recorded I tried to do an update.

 

Known issue, not a solution as of yet, it is being looked into.

[WanWizard]

Was this a record from deep standy, standby, or while the box was on?

[ricki]

The box was on.

[WanWizard]

Thanks. Trying to reproduce it, but sofar no luck.

[ricki]

It was a scheduled timer recording, I didn't notice it and tried to do an update

[WanWizard]

Ok, so it didn't crash when the recording started, but when enigma closed down for an update?

 

Was the recording made correctly? Or didn't it start or about when the crash happened?

[ricki]

The (recording) file is empty, nothing recorded.

Edited by ricki, Yesterday, 16:04.

[WanWizard]

Ok, so it crashes as soon as the recording starts.

 

But you don't see the crash until you shutdown or restart Enigma, at which time you see the green screen?

[littlesat]

Do you record on a hdd... or a mount?

[ricki]

Ok, so it crashes as soon as the recording starts.

 

But you don't see the crash until you shutdown or restart Enigma, at which time you see the green screen?

After the warning that recording is starting, I press exit then i see the crash.

[ricki]

Do you record on a hdd... or a mount?

on a hdd.

[ghuss]

In my case

 

Timer recoding works well when the box is on.

 

It crashes when the box is on standby or deep standby.

 

So what i am doing is setting timer to zap without recording one minute before the recording timer, then the box wakes up and in on, and timer recording starts normaly.