13 replies to this topic

[ntoni]

Hello,

 

can you help me understand why the receiver crashes, it only happens on Mediaset channels, I attach the report, I unfortunately do not understand the meaning.

 

Thank you

[littlesat]

No report attached...

[WanWizard]

Use the "More Reply Options" button to add attachments.

[ntoni]

 

Ciao,

 

potete aiutarmi a capire perché il ricevitore si blocca, succede solo sui canali Mediaset, vi allego la segnalazione, purtroppo non ne capisco il senso.

 

Grazie

 

 

Attached Files

•  enigma2_crash_1660739996.log   30.17KB   7 downloads

[WanWizard]

A difficult one:

PC: b6303edc
Fault Address: be9dd000
Error Code:: 23
Backtrace:
/usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x816DC]
/lib/libc.so.6(__default_rt_sa_restorer) [0xB62BD8F0]
-------FATAL SIGNAL

does it always happen at the same moment? And what exactly do you do when it crashes?
 

[ntoni]

does not happen at the same time or even in the same programme, a green screen appears and the receiver restarts as if nothing had happened.

[WanWizard]

It is probably a bug or issue in the low-level C code, which is extremely hard to debug due to the lack of debugging information.

[ntoni]

It is probably a bug or issue in the low-level C code, which is extremely hard to debug due to the lack of debugging information.

 

so difficult to solve? I posted in another forum, unfortunately without feedback on the solution, a user wrote perhaps a Pyton problem? I hope I get some advice ,thanks for any advice

[WanWizard]

No, it is a crash in the C code.

 

glibc error code 23 is ENFILE: Too many open files in system, which is very unlikely on an STB, unless you do VERY weird things...

[ntoni]

Muhhh... no nothing VERY strange, in the STB there's a USB stick attached and a hard disk, TVSat Card,...skin: Test skin PD1LOI-Full-HD (Mod skin PLi-FullNightHD) 1920x1080, ISetting ,EPG import that work the updates at night... patience I have to try again to delete everything and install the various plugins step by step to understand what could cause the crashes, Thank you for your patience...

excuse my English, I use translate

[WanWizard]

No worries, your English is clear enough.

 

I doubt it is something you do or have installed. Most likely, it is something that is being received that is unexpected, and causes the crash because the data isn't properly validated.

 

An example of that is a provider defining an incorrect characterset, or a correct characterset but the data isn't compliant.

 

Finding the cause without any crash information would require realtime debugging and tracing, I don't have the skills needed, so I can't tell you how.

[ntoni]

Thank you, if some progammers would be able to give me pointers on how to go about debugging I could try to do it, but probably the problem is single so of little interest... 

[4l3x2k]

According to your crash log and the fact that there are too many open files (as WanWizard found out) I would say it has something todo with your ISetting.

There is a flood of request to an ISetting URL in your crash log. Every request results in an open file descriptor which would perfectly match the error code 23 - too many open files.

 

1. You may try to disable ISetting.

 

2. You may show us the output of

sysctl fs.file-max

3. You may try to change the value with

sysctl fs.file-max <VALUE>

Choose a <VALUE> higher than the value reported by the command in 2.

[WanWizard]

Hmm, yeah, sounds logical. And that for a buyware plugin...