[vdr] Re: caught signal 2

[Harald Milz <hm@seneca.muc.de>]

On Mon, Dec 13, 2004 at 07:59:02AM +0100, hm@seneca.muc.de wrote:
> Hi,
> 
> for a couple of days now I've got a strange problem with vdr-1.3.16.
> Soon after starting my VDR up, vdr will report "caught signal 2" to syslog
> and die, like so: 

Normally I don't like to followup on myself but in this case... 

I tried two things to get rid of the problem, although I know for sure I
did not change anything since the vdr worked stably for the last time. 

1. I switched the av7110 firmware back to 11/17/2004 (I was using Werner's
recent version) - no change. 

2. I suspected it was the NFS file share mounted on /video, tried Samba and
NFS over TCP, no change. 

What else could the problem be? Last night it looked as if it worked fine
with Samba for about half an hour when suddenly the signal 2 came along
again. 

Please... ! 

Again, the setup is: 

Epia5000 board, FSC v1.3 card, vdr-1.3.16 with Werner's AC3overDVB patches,
linux-dvb-1117204. Plus some modules but the problem occurs also if no
modules are loaded at all. 


> Dec 12 20:35:39 linvdr vdr[3498]: setting watchdog timer to 60 seconds
> Dec 12 20:35:39 linvdr vdr[3498]: retuning due to modification of channel 2
> Dec 12 20:35:39 linvdr vdr[3498]: switching to channel 2
> Dec 12 20:35:39 linvdr vdr[3506]: transfer thread started (pid=3506, tid=81926)
> Dec 12 20:35:39 linvdr vdr[3507]: receiver on device 1 thread started (pid=3507, tid=98311)
> Dec 12 20:35:39 linvdr vdr[3508]: TS buffer on device 1 thread started (pid=3508 , tid=114696)
> Dec 12 20:35:40 linvdr vdr[3498]: caught signal 2
> Dec 12 20:35:40 linvdr vdr[3506]: transfer thread ended (pid=3506, tid=81926)
> Dec 12 20:35:41 linvdr vdr[3508]: TS buffer on device 1 thread ended (pid=3508, tid=114696)
> Dec 12 20:35:41 linvdr vdr[3507]: buffer stats: 70312 (3%) used
> Dec 12 20:35:41 linvdr vdr[3507]: receiver on device 1 thread ended (pid=3507, tid=98311)
> Dec 12 20:35:41 linvdr vdr[3498]: buffer stats: 182736 (8%) used
> Dec 12 20:35:41 linvdr vdr[3504]: KBD remote control thread ended (pid=3504, tid =65541)
> 
> Strange thing is, the machine was working all day long yesterday, and this
> happened only in the evening. I had to restart the box because it wouldn't
> react to the remote any more (using the remote module with the av7110 IR). 
> 
> It is always the master thread that reports signal 2. All other threads
> keep running, strangely. And after a warm restart, "./av7110_loadkeys
> /video/my.rc5" will hang and not continue. It needs a reboot... 
> 
> Any idea who or what sends a SIGINT to vdr in the first place? 
> 
> -- 
> The only problem with being a man of leisure is that you can never stop
> and take a rest.
> 

-- 
"To Be or Not To Be"
	-- Hamlet
"Doo Be Doo Be Doo"
	-- Frank Sinatra