[vdr] Re: Emergency exit after timer finishes (vdr-1.1.21)

[Gregor Lawatscheck <gpel@mpex.net>]

At 11:33 25/01/2003, you wrote:
> Jan 25 13:06:31 meetugate vdr[341]: emergency exit requested - shutting down
> Jan 25 13:06:34 meetugate vdr[341]: ERROR: thread 350 won't end (waited 3
> seconds) - cancelling it...
> Jan 25 13:06:34 meetugate vdr[351]: receiver thread ended on device 1
> (pid=351)
> Jan 25 13:06:34 meetugate vdr[341]: buffer stats: 166916 (15%) used
> Does this happen to someone else too?
Hi Teemu,
this could be in connection to your "handle oversized TS" patch, I've had 
this a couple of times after appyling your patch but blamed it on the if 
r=0 --> usleep(1) CPU saving.

There appears to be very rare deadlock situation with the patch, that can 
freeze the picture. You then have to switch channels, for the stream to 
come back, if you don't vdr will exit with "broken stream". I'm not quite 
sure why the deadlock happens, and have been trying to watch the error. It 
only happens once or twice a day, so it's fairly hard to track down.

What's the reasoning behind the CPU saving thing. What exactly happens when 
r=0  or why would it be ? Is this when vdr has gone to idle mode?

- Gregor 


--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.