Jump to content


Photo

Annoying Pli bug


  • Please log in to reply
49 replies to this topic

Re: Annoying Pli bug #21 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 28 April 2015 - 14:48

No OOM killers or kernel OOPSes.

In that case probably the memory is just fragmented.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Annoying Pli bug #22 sonic1

  • Senior Member
  • 62 posts

+3
Neutral

Posted 2 May 2015 - 17:14

root@vuduo2:~# [VID]: VIDEO_SET_STREAMTYPE 1
FE tune
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_FREEZE 6498576  0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_PLAY 6498576  5 2
-sh: [VID]:: not found
[AUD]: AUDIO_SET_BYPASS_MODE 0
 
root@vuduo2:~# [VID]: VIDEO_SLOWMOTION 0    1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_FAST_FORWARD 0    1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_CONTINUE 6498576  1
-sh: [VID]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE 6498576 1 aph=0xce25a480
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: Mute : 0
-sh: [AUD]:: not found
root@vuduo2:~# [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_GET_SIZE aspect: 1 0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_STOP 1  1
-sh: [VID]:: not found
root@vuduo2:~# [AUD]: AUDIO_STOP 6498576
[AUD]: AUDIO_CONTINUE 6498576 1 aph=0xcf7eef80
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE 6498576 0 aph=0x0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE aph=0 0 0
-sh: [AUD]:: not found
root@vuduo2:~# FE tune
-sh: FE: not found
root@vuduo2:~# [AUD]: AUDIO_SELECT_SOURCE 0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_SET_BYPASS_MODE 0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AC3 downmix 0  state : 0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_PAUSE 6498576
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_PLAY 6498576 decoder start : 0
-sh: [AUD]:: not found
root@vuduo2:~# [VID]: VIDEO_SELECT_SOURCE 0  0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_SET_STREAMTYPE 1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_FREEZE 6498576  0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_PLAY 6498576  5 2
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_SLOWMOTION 0    1
[AUD]: downmix 0 state : 0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_FAST_FORWARD 0    1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_CONTINUE 6498576  1
-sh: [VID]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE 6498576 1 aph=0xce293a00
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: Mute : 0
-sh: [AUD]:: not found
root@vuduo2:~# [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_GET_SIZE aspect: 1 0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_STOP 1  1
-sh: [VID]:: not found
root@vuduo2:~# [AUD]: AUDIO_STOP 6498576
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE 6498576 0 aph=0x0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE aph=0 0 0
-sh: [AUD]:: not found
root@vuduo2:~# FE tune
-sh: FE: not found
root@vuduo2:~# [AUD]: AUDIO_SELECT_SOURCE 0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_SET_BYPASS_MODE 0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AC3 downmix 0  state : 0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_PAUSE 6498576
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_PLAY 6498576 decoder start : 0
-sh: [AUD]:: not found
root@vuduo2:~# [VID]: VIDEO_SELECT_SOURCE 0  0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_SET_STREAMTYPE 1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_FREEZE 6498576  0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_PLAY 6498576  5 2
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_SLOWMOTION 0    1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_FAST_FORWARD 0    1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_CONTINUE 6498576  1
-sh: [VID]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE 6498576 1 aph=0xcf7eef80
[VID]: VIDEO_SELECT_SOURCE 0  0
[VID]: VIDEO_SET_STREAMTYPE 0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: Mute : 0
-sh: [AUD]:: not found
root@vuduo2:~# [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_GET_SIZE aspect: 1 0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_STOP 1  1
-sh: [VID]:: not found
root@vuduo2:~# [AUD]: AUDIO_STOP 6498576
-sh: [AUD]:: not found
 
root@vuduo2:~# [AUD]: AUDIO_CONTINUE 6498576 0 aph=0x0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE aph=0 0 0
[VID]: VIDEO_CONTINUE 6498576  1
-sh: [AUD]:: not found
root@vuduo2:~# FE tune
-sh: [AUD]: AUDIO_CONTINUE 6498576 1 aph=0xb309cd00
FE: not found
root@vuduo2:~# FE tune
-sh: FE: not found
root@vuduo2:~# [AUD]: AUDIO_SELECT_SOURCE 0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_SET_BYPASS_MODE 1
-sh: [VID]: VIDEO_GET_SIZE aspect: 0 0[AUD]:: not found
root@vuduo2:~# [AUD]: downmix 0 state : 0
-sh:
[VID]: VIDEO_STOP 1  1
[AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_PAUSE 6498576
-sh: [AUD]:: not found[AUD]: AUDIO_STOP 6498576
 
root@vuduo2:~# [AUD]: AUDIO_PLAY 6498576 decoder start : 0
-sh: [AUD]:: not found
root@vuduo2:~# [VID]: VIDEO_SELECT_SOURCE 0  0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_SET_STREAMTYPE 0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_FREEZE 6498576  0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_PLAY 6498576  2 2
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_SLOWMOTION 0    1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_FAST_FORWARD 0    1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_CONTINUE 6498576  1
-sh: [VID]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE 6498576 1 aph=0xcf7feb80
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: Mute : 0
-sh: [AUD]:: not found
root@vuduo2:~# [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_GET_SIZE aspect: 1 0
-sh: [VID]:: not found
root@vuduo2:~# FE tune
-sh: FE: not found
root@vuduo2:~# FE tune
-sh: FE: not found
root@vuduo2:~# FE tune
-sh: FE: not found
root@vuduo2:~# FE tune
-sh: FE: not found
root@vuduo2:~# FE tune
-sh: FE: not found
root@vuduo2:~# FE tune
-sh: FE: not found
root@vuduo2:~# [VID]: VIDEO_STOP 1  1
-sh: [VID]:: not found
root@vuduo2:~# [AUD]: AUDIO_STOP 6498576
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE 6498576 0 aph=0x0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE aph=0 0 0
-sh: [AUD]:: not found
root@vuduo2:~# FE tune
-sh: FE: not found
root@vuduo2:~# [AUD]: AUDIO_SELECT_SOURCE 0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_SET_BYPASS_MODE 1
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: downmix 0 state : 0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_PAUSE 6498576
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_PLAY 6498576 decoder start : 0
-sh: [AUD]:: not found
root@vuduo2:~# [VID]: VIDEO_SELECT_SOURCE 0  0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_SET_STREAMTYPE 0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_FREEZE 6498576  0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_PLAY 6498576  2 2
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_SLOWMOTION 0    1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_FAST_FORWARD 0    1
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_CONTINUE 6498576  1
-sh: [VID]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE 6498576 1 aph=0xb309cd00
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: Mute : 0
-sh: [AUD]:: not found
root@vuduo2:~# [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_GET_SIZE aspect: 0 0
-sh: [VID]:: not found
root@vuduo2:~# [VID]: VIDEO_STOP 1  1
-sh: [VID]:: not found
root@vuduo2:~# [AUD]: AUDIO_STOP 6498576
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE 6498576 0 aph=0x0
-sh: [AUD]:: not found
root@vuduo2:~# [AUD]: AUDIO_CONTINUE aph=0 0 0
-sh: [AUD]:: not found


Re: Annoying Pli bug #23 ian1095

  • Senior Member
  • 462 posts

+6
Neutral

Posted 3 May 2015 - 08:56

Any news on a fix for this issue ?

 

Its not massively important but it is really really annoying !

 

If I had to guess,and its only a guess,I would say this issue started at the time Pli introduced the restart counter,so maybe the code that was added to log the number of restarts a user has performed would be a good place to start to look for whats causing this.

 

Ian.



Re: Annoying Pli bug #24 WanWizard

  • PLi® Core member
  • 69,910 posts

+1,787
Excellent

Posted 3 May 2015 - 09:36

If that was the case, everyone would have this problem, and for now nobody else has reported this.

 

Problems like this, with no log info, and no way to reproduce it, are notoriously difficult to fix.


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: Annoying Pli bug #25 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 3 May 2015 - 09:48

As long as the source of this kind of problems is in the drivers, there is no chance for a fix.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Annoying Pli bug #26 saintomer1866

  • Senior Member
  • 48 posts

+2
Neutral

Posted 3 May 2015 - 10:37

I also have this problem on my solo2 (external usb HDD),

one thing I will add is I can guarantee that the the first reboot or enigma2 restart of the day will  result in the constant spinner for me,

solvable only by telneting into the box or the power switch.

After the first restart/reboot this can then happen randomly or not at all until the next day when the cycle starts again

 

This has got nothing to do with any restarts after updating as I don't have a problem with that

 

St.O



Re: Annoying Pli bug #27 Trial

  • Senior Member
  • 1,127 posts

+34
Good

Posted 3 May 2015 - 11:33

Hi,

do you have the problem also with fresh flash without restore? If no then it is not PLi then it must be a plugin or setting you installed/made.

 

If you are so sure that you can reproduce then its an easy test.

 

ciao



Re: Annoying Pli bug #28 ian1095

  • Senior Member
  • 462 posts

+6
Neutral

Posted 3 May 2015 - 11:36

Yep

 

The problem remains even after a clean install,without using any restore settings at all.

 

Ian.



Re: Annoying Pli bug #29 ian1095

  • Senior Member
  • 462 posts

+6
Neutral

Posted 23 May 2015 - 08:23

Ok after loads of testing Ive got to the bottom of this.

 

Its caused by the EPG cache,it doesnt matter if this is obtained by Crossepg or EPG Import,the problem is the same.

 

The failure to restart causing the box to hang and give constant spinner only happens on the very first restart after the EPG data has been updated.

 

This is the debug from Enigma2

 

< 36295.867924> [eventData] EPG Cache is corrupt (eventData::~eventData), you should restart Enigma!

 

This is after the EPG has been updated and obtained from debug mode using telnet.

 

Every subsequent restart after this is then perfectly fine,until the EPG data is again updated,then the problem returns on the first restart.

 

Ian.


Edited by ian1095, 23 May 2015 - 08:26.


Re: Annoying Pli bug #30 littlesat

  • PLi® Core member
  • 56,954 posts

+695
Excellent

Posted 23 May 2015 - 09:32

How do you updat epg data?

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


Re: Annoying Pli bug #31 ian1095

  • Senior Member
  • 462 posts

+6
Neutral

Posted 23 May 2015 - 10:31

I usually use Crossepg Opentv, but it doesnt matter because the problem remains even if I use EPG Import and Rytec sources as well.

 

Ian.



Re: Annoying Pli bug #32 Pr2

  • PLi® Contributor
  • 6,154 posts

+261
Excellent

Posted 23 May 2015 - 10:39

Since it only happens on VU+ isn't still the old bug of the date?

When this occurs, please telnet to the box and type:

 

date

 

And check if the date is in the past or not.

 

Pr2


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 


Re: Annoying Pli bug #33 ian1095

  • Senior Member
  • 462 posts

+6
Neutral

Posted 23 May 2015 - 10:54

Now we know how to trigger the bug its easy to test.

 

I will update my EPG then restart E2 for you then telnet in and type date

 

Ian.



Re: Annoying Pli bug #34 ian1095

  • Senior Member
  • 462 posts

+6
Neutral

Posted 23 May 2015 - 10:58

Im afraid its not that.

 

I updated the EPG then with the remote tried to restart.

 

Constant spinner as expected.

 

I then telneted in and typed in date as shown bellow

 

root@vusolo:~# date
Sat May 23 10:57:59 IST 2015

 

At this point as usual, I had to again issue the killall -9 enigma2 command to get the box to restart.

 

Ian.


Edited by ian1095, 23 May 2015 - 11:03.


Re: Annoying Pli bug #35 ian1095

  • Senior Member
  • 462 posts

+6
Neutral

Posted 23 May 2015 - 11:18

It maybe worth mentioning too that this bug has been passed on to the new alpha Open BH image which is using Pli OE as its base,but of course is not present in their existing BH image that uses the VU OE core as its base.

 

Of course this is not your problem,but I just thought it prudent to mention that the bug does effect all other images using Pli as their base.

 

Ian.


Edited by ian1095, 23 May 2015 - 11:21.


Re: Annoying Pli bug #36 WanWizard

  • PLi® Core member
  • 69,910 posts

+1,787
Excellent

Posted 23 May 2015 - 11:36

Still very curious to know what the actual cause is. I've never had a corrupt EPG on any of my boxes, and I'm a rytec user from day 1.


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: Annoying Pli bug #37 ian1095

  • Senior Member
  • 462 posts

+6
Neutral

Posted 23 May 2015 - 11:47

I'm not even sure the EPG data is actually corrupted,because after the failed restart attempt,the EPG performs perfectly (as do all new box restarts) until the next time the EPG is updated,and as stated after this,only the very first restart or reboot is effected,and the EPG is fine for the 7 day duration of the data.

 

Ian.


Edited by ian1095, 23 May 2015 - 11:49.


Re: Annoying Pli bug #38 WanWizard

  • PLi® Core member
  • 69,910 posts

+1,787
Excellent

Posted 23 May 2015 - 14:29

Double weird, because a corrupted EPG should not cause the box to hang, a race condition somewhere that causes a loop if that particular corruption occurs?

 

But that would mean a freak event (for example depending on the data), but you say you can reproduce it.

And if it's reproducable, why only on your box? Enigma and the import code is exactly the same on all other boxes.

 

Still very puzzled by this...


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: Annoying Pli bug #39 ian1095

  • Senior Member
  • 462 posts

+6
Neutral

Posted 23 May 2015 - 14:31

Its not just on my box,its all VU boxes.

 

Not sure if thats what you meant when you said "on your box"

 

Ian.



Re: Annoying Pli bug #40 WanWizard

  • PLi® Core member
  • 69,910 posts

+1,787
Excellent

Posted 23 May 2015 - 16:24

See my sig... :) (with the remark that the Solo is in it's box atm).


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.



2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users