Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vdr] GRAB frezes the SVDRP channel



Hi,

While doing remote testing (over ssh) of the new 1.3.2 I've tried to grab
images from the currently shown channel using SVDRP. It somehow just
freezes when I at the SVDRP prompt type something like:

grab /tmp/file.jpg

or:

grab foo.jpg

lste
.... <lots of output>
215-e
215-c
215 End of EPG data
chan 1
250 1 YLE TV1
grab /tmp/test.jpg

Connection closed by foreign host.
%

So VDR apparently crashes doing the GRAB command? The log says this (a
freshly restarted VDR):

11:09:26 vdr[9479]: setting watchdog timer to 60 seconds
11:09:33 vdr[9479]: max. latency time 1 seconds
11:09:37 vdr[9484]: CAM: Conax 4.00e, 01, 0B00, 04B1
11:09:49 vdr[9479]: connect from 127.0.0.1, port 33136 - accepted
11:09:52 vdr[9479]: switching to channel 2
11:09:54 vdr[9485]: changing id of channel 1 from 0-0-17-0 to 15-3-17-0
11:09:54 vdr[9485]: changing id of channel 2 from 0-0-33-0 to 15-3-33-0
11:09:54 vdr[9485]: changing id of channel 3 from 0-0-81-0 to 15-3-81-0
11:09:54 vdr[9485]: changing id of channel 5 from 0-0-193-0 to 15-3-193-0
11:09:54 vdr[9485]: changing id of channel 4 from 0-0-209-0 to 15-3-209-0
11:09:54 vdr[9485]: changing id of channel 19 from 0-0-289-0 to 15-3-289-0
11:09:54 vdr[9485]: changing id of channel 15 from 0-0-272-0 to 15-3-272-0
11:09:54 vdr[9485]: changing id of channel 16 from 0-0-274-0 to 15-3-274-0
11:09:54 vdr[9485]: changing id of channel 17 from 0-0-275-0 to 15-3-275-0
11:09:54 vdr[9485]: changing id of channel 18 from 0-0-276-0 to 15-3-276-0
11:09:54 vdr[9485]: creating new channel 'test' on C transponder 162 with
id 15-3-8212-0
11:09:55 vdr[9485]: changing transponder data of channel 1 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing transponder data of channel 2 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing transponder data of channel 3 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing transponder data of channel 4 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing transponder data of channel 5 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing transponder data of channel 15 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing transponder data of channel 16 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing transponder data of channel 17 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing transponder data of channel 18 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing transponder data of channel 19 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing transponder data of channel 83 from
C:162:4:6900:9 to C:162000:4:6900:0
11:09:55 vdr[9485]: changing pids of channel 83 from 0+0:0,0;0,0:0 to
2221+2221:2231,2232;0,0:768
11:09:55 vdr[9485]: changing caids of channel 83 from 0 to B00
11:09:55 vdr[9479]: retuning due to modification of channel 2
11:09:55 vdr[9479]: switching to channel 2
11:10:10 vdr[9479]: switching to channel 1
11:11:23 vdr[9479]: PANIC: watchdog timer expired - exiting!

This is with 1.3.2 and the recommended drivers. A one card system with a
full Hauppauge DVB-c. 1.2.6pre4 did exactly the same, ie crashed when I
did the GRAB. I've actually never seen GRAB work, when it hasn't crashed
it has given me an image of correct size but always one solid color (gray,
I think).

Is this expected behaviour, ie a known bug? I haven't seen anything
related to this on the list for ages, so I assume others don't have this
problem.

Hm, after a restart VDR finds no channels at all... Interesting.

-- 

        Most gods find it hard to walk and think at the same time.
                                             -- Terry Pratchett, Small Gods


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



Home | Main Index | Thread Index