[linux-dvb] Re: cinergyT2: which kernel/usb module to use?

[Holger Waechtler <holger@qanu.de>]

Stefan Lucke wrote:

> On Samstag, 4. Dezember 2004 13:58, Holger Waechtler wrote:
>  
> > Hi,
> >
> > Stefan Lucke wrote:
> >
> >    
> > > That was a bit too early. Now the error is back ;-( .
> > >
> > > Dec  3 23:22:18 jarada kernel: ff HAS LOCK :-)
> > > Dec  3 23:22:42 jarada last message repeated 72 times
> > > Dec  3 23:22:42 jarada vdr[4342]: switching to channel 7
> > > Dec  3 23:22:42 jarada kernel: ff HAS LOCK :-)
> > > Dec  3 23:22:42 jarada vdr[4351]: transfer thread ended (pid=4351, tid=131078)
> > > Dec  3 23:22:42 jarada vdr[4342]: buffer stats: 253309 (24%) used
> > > Dec  3 23:22:43 jarada vdr[4354]: TS buffer on device 1 thread ended (pid=4354, tid=180233)
> > > Dec  3 23:22:43 jarada vdr[4352]: buffer stats: 74260 (3%) used
> > > Dec  3 23:22:43 jarada vdr[4352]: receiver on device 1 thread ended (pid=4352, tid=147463)
> > > Dec  3 23:22:43 jarada vdr[4342]: buffer stats: 74636 (3%) used
> > >
> > >
> > >      
> > what means "thread ended"? Does this means the file descriptor is closed 
> > and the device is put into suspend mode?
> >    
> I don't know exact what vdr does. I should issue some printk's upon
> open/close suspend/resume and SET_FRONTEND too.
>
>  
> > > Dec  3 23:22:43 jarada kernel: 00 HAS NOO LOCK :-(
> > > Dec  3 23:22:48 jarada last message repeated 15 times
> > > Dec  3 23:22:48 jarada vdr[4342]: ERROR: device 1 has no lock, can't attach receiver!
> > >
> > >
> > >      
> > I can't see new tuning requests above this message in the log, did you 
> > cutted them away?
> >    
> No, that was a contigous block of messages. "LOCK" messages are reported from
> driver's view and I didn't issue a message during "SET_FRONTEND" .
>
>  
> > If not, what exactly did you do, why are all transfers 
> > suspended but no new tuning request issued?
> >    
> Transfer thread from previous tuned channel 8  ended.
>
> Meanwhile I tested all my 3 devices. Erronous behaviour is shown only by
> 1 out of 3. This probably buggy one, shows this after around 15 to 20 minutes
> of running. The other 2 run stable for more than 1 hour without problems.
> I should test ok-time for a longer period.
>  
Would you be so kind and please lend me this device for a few days so 
that I can do some tests? Up to now we had no reports regarding heat 
problems...

Holger