Jump to content


Adblock Plus
Advertising seems to be blocked by your browser.

Please notice that advertising helps us to cover the cost of hosting the project.

If you find these ads displayed intrusive or inappropriate, please contact the webmaster.
Photo

Crash logs

crash log

  • Please log in to reply
9 replies to this topic

#1 stefan1983

  • Member
  • 23 posts

0
Neutral

Posted 5 September 2020 - 02:00

Hi everyone,

 

attached some crash logs to analyse.

 

Regards,

Stefan

Attached Files



Re: Crash logs #2 littlesat

  • PLi® Core member
  • 57,537 posts

+709
Excellent

Posted 5 September 2020 - 05:58



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

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Crash logs #3 littlesat

  • PLi® Core member
  • 57,537 posts

+709
Excellent

Posted 5 September 2020 - 05:59

What is logger ‘AT’?

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Crash logs #4 Dimitrij

  • PLi® Core member
  • 10,388 posts

+354
Excellent

Posted 5 September 2020 - 07:42

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


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Crash logs #5 mcfly82

  • Senior Member
  • 32 posts

+2
Neutral

Posted 2 October 2020 - 20:44

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.


Re: Crash logs #6 s3n0

  • Senior Member
  • 675 posts

+62
Good

Posted 3 October 2020 - 14:50

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



Re: Crash logs #7 WanWizard

  • PLi® Core member
  • 71,159 posts

+1,841
Excellent

Posted 3 October 2020 - 17:16

What details do you miss at the moment?

 

And PR's are always welcome... ;)


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Crash logs #8 s3n0

  • Senior Member
  • 675 posts

+62
Good

Posted 4 October 2020 - 14:10

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 :P .



Re: Crash logs #9 littlesat

  • PLi® Core member
  • 57,537 posts

+709
Excellent

Posted 5 October 2020 - 09:02

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.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Crash logs #10 s3n0

  • Senior Member
  • 675 posts

+62
Good

Posted 5 October 2020 - 21:42

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 :-/ .





Also tagged with one or more of these keywords: crash log

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users