[pvrusb2] Suspend related issues with pvrusb2

[Mike Isely]

Going through old messages...

This one is probably that same kernel oops problem found earlier today, 
but I'm sure you already suspect as much.

  -Mike


On Thu, 1 Apr 2010, devsk wrote:

> Mike,
> 
> Any ideas about the garbage problem?
> 
> > [ 1193.215000] usbcore: deregistering interface driver pvrusb2
> > [ 1193.215000] pvrusb2: Device being rendered inoperable
> > [ 
> 1193.215000] pvrusb2: unregistered device 
> x¼<96>Ý^A<88>ÿÿstats [mpeg]
> > [ 1193.215000] pvrusb2: 
> unregistered device ¨¼<96>Ý^A<88>ÿÿradio0 [mpeg]
> > [ 
> 1193.215000] tuner-simple 1-0061: destroying instance
> > [ 
> 1193.215000] tda9887 1-0043: destroying instance
> 
> And why is it unregistering two devices?
> 
> -devsk
> 
> 
> 
> 
> ________________________________
> From: Mike Isely <isely at isely.net>
> To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> Sent: Tue, March 30, 2010 5:34:58 PM
> Subject: Re: [pvrusb2] Suspend related issues with pvrusb2
> 
> On Tue, 30 Mar 2010, devsk wrote:
> 
> > But it works in Windows...I am just kidding...:-D
> > 
> > I think what you mean is that you did not do anything specifically to 
> > handle the suspend-resume events by providing callbacks.
> 
> That is correct.  I'm not doing anything special here.  But that's not 
> to say that something 'special' might be needed; I just don't know 
> enough about that (and there really hasn't been any demand for it) to 
> get that right.
> 
> > 
> > I think that's fine, as long as we know that's how it is. I can just 
> > remove the module and add it after resume.
> 
> OK.
> 
> 
> 

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8