Jump to content


Photo

Crash when more timers start at the same time


  • Please log in to reply
22 replies to this topic

#1 HWTest

  • Senior Member
  • 67 posts

+1
Neutral

Posted 7 January 2019 - 15:03

I've encountered a crash (without a crash log) on my new Ultimo 4k running OpenPLi 6.2.

I was watching a recording, one recording was already running a three were starting. At this moment the playback stopped and I got a no free tuner warning, then the spinner and a reboot (probably just enigma restart). After the reboot, again no free tuner warning but all 4 recording successfully restarted. Sadly after this, Oscam was in some strange state and the new recordings were scrambled.

Is this "normal" (as expected) and I should check that recording don't start at the same time?

 

PS: I remember on VTI there was a choice "don't allow recordings start at the same time" or something like that. I've never set it to on and never had problems with multiple recordings starting at the same time - but that was on the Duo2 with regular (non FBC) tuners. Maybe it's a FBC tuners specific problem.



Re: Crash when more timers start at the same time #2 WanWizard

  • Forum Moderator
    PLi® Core member
  • 46,712 posts

+766
Excellent

Posted 7 January 2019 - 15:34

I know it has been worked on for OpenPLi 7, but I can't remember if it was completely fixed or not.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

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

note: I do not provide support via PM !

 


Re: Crash when more timers start at the same time #3 ccs

  • Senior Member
  • 80 posts

+2
Neutral

Posted 7 January 2019 - 15:52

The issue was discussed in this very long thread....

 

https://forums.openp...ous-recordings/



Re: Crash when more timers start at the same time #4 littlesat

  • PLi® Core member
  • 47,871 posts

+500
Excellent

Posted 7 January 2019 - 16:31

In openpli 7.0 we have a work-a-round included that solved this topic... (when someone did not revert it)... it does solve the diseqc switch issue and also exact this one...

Edited by littlesat, 7 January 2019 - 16:32.

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


Re: Crash when more timers start at the same time #5 Rob van der Does

  • Senior Member
  • 7,731 posts

+184
Excellent

Posted 7 January 2019 - 16:51

That 'long thread' was not about a crash, but about failing (zero length) recordings.

Re: Crash when more timers start at the same time #6 littlesat

  • PLi® Core member
  • 47,871 posts

+500
Excellent

Posted 7 January 2019 - 16:53

I speculate this is what here is meant with crash without crashlog ;)

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


Re: Crash when more timers start at the same time #7 ccs

  • Senior Member
  • 80 posts

+2
Neutral

Posted 7 January 2019 - 17:03

That 'long thread' was not about a crash, but about failing (zero length) recordings.

But a workaround for timers starting at the same time was discussed.



Re: Crash when more timers start at the same time #8 HWTest

  • Senior Member
  • 67 posts

+1
Neutral

Posted 7 January 2019 - 17:10

I don't know about the "first" recordings (before the crash), because the box crashed immediately after they started, so I deleted them without checking.

The "second" recordings (after the crash) had normal sizes but were scrambled because Oscam didn't survive the crash and I wasn't able to offline decode them afterwards (a day later).

 

Starting to read the very long thread ...



Re: Crash when more timers start at the same time #9 Rob van der Does

  • Senior Member
  • 7,731 posts

+184
Excellent

Posted 8 January 2019 - 14:57

That 'long thread' was not about a crash, but about failing (zero length) recordings.

 
 

I speculate this is what here is meant with crash without crashlog ;)


I don't think so. OP mentions 'no free tuner', which was absolutely no issue in the mentioned 'long thread & work-around'.

Re: Crash when more timers start at the same time #10 anudanan

  • Senior Member
  • 976 posts

+14
Neutral

Posted 8 January 2019 - 15:03

I often have different timers with the same start time most at prime time and that works on 7.0rc

Sometimes in the past I have seen a driver crash by starting timers with the same start time on 6.1

Box is uno4kse

I‘ve no driver crashes seen on 7.0 since today and my wife make very much recordings

Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: Crash when more timers start at the same time #11 Erik Slagter

  • PLi® Core member
  • 45,158 posts

+495
Excellent

Posted 8 January 2019 - 19:58

The issue discussed in the other thread was for a very specific case, with multiple FBC tuners having SCR tuners assigned. I don't think that is the case here.

 

The next time this issue plays, I suggest you login, type "dmesg" and at the bottom you'll see something like "kernel OOPS" or "null pointer reference" and then a stack trace.

 

Which means the drivers have crashed. Only solution is to reboot.


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
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: Crash when more timers start at the same time #12 ccs

  • Senior Member
  • 80 posts

+2
Neutral

Posted 8 January 2019 - 20:08

I only mentioned the other thread because of this comment....

 

 

Are you sure this works... I also have issues with timers starting on the same time (without jess/unicable).... and this ‘work a round’ looks really simple

 



Re: Crash when more timers start at the same time #13 HWTest

  • Senior Member
  • 67 posts

+1
Neutral

Posted 9 January 2019 - 08:03

Hmmm, so what should I do?

 

Check that no timers start at the same time and take it as normal?

Wait for OpenPLi 7?

Try to reproduce the problem and post the dmesg output?



Re: Crash when more timers start at the same time #14 anudanan

  • Senior Member
  • 976 posts

+14
Neutral

Posted 9 January 2019 - 09:04

From m point of view take openpli7.0rc. There are new driver included and for me the driver are better with fixed crashed. With my uno4kse I have a same FBC tuner as you in your ultimo4k


Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: Crash when more timers start at the same time #15 ColinB

  • Senior Member
  • 707 posts

+28
Good

Posted 9 January 2019 - 10:48

Hmmm, so what should I do?

 

Check that no timers start at the same time and take it as normal?

Wait for OpenPLi 7?

Try to reproduce the problem and post the dmesg output?

 

Move to OpenPLi 7.0-rc

 

No point in waisting time on old image.


Xtrend et8000 7.0-Release

2 x 8/1 DiSEqC  30w 13e 19e 23e 28e   

Astrometa USB Tuner Working DVB-T2 now on Kernel 4.10 ;)

WD10EARX 1TB

Sandisk 32GB USB for AFB, EPG, Picons & Timeshift

 

ZGemma Star S (6.2) Testing 7.0-RC

4/1 DiSEqC  30w 13e 19e 28e

Sandisk 8GB USB for AFB, EPG, Picons & Timeshift

 

LG 49UH610V UHD-HDR

UHF/Cable/Sat

 

E-Channelizer

 

 

 


Re: Crash when more timers start at the same time #16 anudanan

  • Senior Member
  • 976 posts

+14
Neutral

Posted 9 January 2019 - 20:12

Today my uno4kse start four timer at 20:04 and four timer at 20:05 with no crashes.
I think 7.0rc is more stable than 6.x on VU+

Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: Crash when more timers start at the same time #17 anudanan

  • Senior Member
  • 976 posts

+14
Neutral

Posted 9 January 2019 - 20:23

I don‘t know if they started with seconds delay. But maybe

Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: Crash when more timers start at the same time #18 anudanan

  • Senior Member
  • 976 posts

+14
Neutral

Posted 9 January 2019 - 20:31

I‘ve startet 3 more timer at the same timer and saw in the timerlist they start with a second delay timer1, delay , timer2, delay , timer3

So you are right

Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: Crash when more timers start at the same time #19 ccs

  • Senior Member
  • 80 posts

+2
Neutral

Posted 9 January 2019 - 20:47

I deleted my last post because I could only see timers at the hour and minute level, no detail of seconds that I could find.



Re: Crash when more timers start at the same time #20 HWTest

  • Senior Member
  • 67 posts

+1
Neutral

Posted 10 January 2019 - 21:36

OK, is the 7.0 RC stable enough for daily use?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users