9 replies to this topic

[stefan1983]

Hi everyone,

 

attached some crash logs to analyse.

 

Regards,

Stefan

Attached Files

•  enigma2_crash_19.log   24.09KB   7 downloads
•  enigma2_crash_27.log   24.09KB   0 downloads
•  enigma2_crash_28.log   24.09KB   2 downloads
•  enigma2_crash_1597776195.log   23.62KB   0 downloads
•  enigma2_crash_1597776565.log   23.26KB   1 downloads
•  enigma2_crash_1598040505.log   80.41KB   1 downloads
•  enigma2_crash_1598041007.log   23.26KB   1 downloads
•  enigma2_crash_1598045000.log   23.26KB   0 downloads
•  enigma2_crash_1598045730.log   23.26KB   1 downloads
•  enigma2_crash_1598045856.log   23.67KB   1 downloads
•  enigma2_crash_1599160839.log   24.09KB   4 downloads

[littlesat]

No handlers could be found for logger "AT"
Backtrace:
/usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x72AF4]
/lib/libc.so.6(__default_rt_sa_restorer) [0xB61FF3D0]
/lib/libc.so.6(gsignal) [0xB61FE1CC]
/lib/libc.so.6(abort) [0xB61FF530]
-------FATAL SIGNAL

[littlesat]

What is logger ‘AT’?

[Dimitrij]

What is logger ‘AT’?

This autotimer shell logger.

But this has nothing to do with crashes.

I also really want to correct this mistake, it often arises with me, but for this you need to learn how to read the output of the enigma2.
But I don't know how, I asked this question here https://forums.openp...dpost&p=1250170

[mcfly82]

Many times... the log is always the same.

This appears when I try to restart the box. Sometimes it attempts 3 or 4 times when success to boot.

Box: Zgemma h7s

 

 

OpenPLi Enigma2 crash log

 

crashdate=Thu Jan  1 01:05:36 1970

compiledate=Aug 31 2020

skin=GreenHexagonFHD/skin.xml

sourcedate=2020-08-29

branch=release-7.3

rev=6976b55

component=enigma2

 

kernelcmdline=root=/dev/mmcblk0p5 rw rootwait h7_4.boxmode=1 brcm_cma=440M@328M brcm_cma=192M@768M console=ttyS0,115200

imageissue=openpli 7.3-release %h

 

 

[gFBDC] no framebuffer available

 

 

dmesg

Edited by mcfly82, 2 October 2020 - 20:45.

[s3n0]

It would like to implement the same detailed debug-log in OpenPLi as used in the case of OpenATV.

[WanWizard]

What details do you miss at the moment?

 

And PR's are always welcome...

[s3n0]

I mean some details from a separate thread or process - "AutoTimer". Details of why the error was exception and what preceded the error.

 

If you've ever seen a debug-log in OpenATV then you know what I meant .

[littlesat]

Than show an example.... when debugging you have special toots to do this. On a normal run of enigma2 you do not want to log everything... you also can run e2 on a higher debut level to see more.

Edited by littlesat, 5 October 2020 - 09:02.

[s3n0]

During the development of plugins (not only Chocholousek Picons plugin, but also commercial plugins for money) I had to use OpenATV, because OpenPLi did not provide detailed debug-log entries for me.

 

I don't know how it is solved in the case of OpenATV. Contact the OpenATV development team and ask them. I don't care much about system programming (Enigma2). I am programming only plugins (Enigma2 / Python) :). OpenATV gives me detailed information in the debug-log, but OpenPLi does not.

 

I can't give you an debug-log file example at the moment. I have connected other set-top boxes, which are not used for plugin development, and I will not disconnect them until a week later. Many examples for a detailed debug-log file can be found on the discussion forum www.opena.tv. Look there. I have no free time for this purpose... I'm sorry :-/ .