[pvrusb2] OOPs with latest standalone driver in 2.6.33.2

[devsk]

ahh....that explains it. Let me run it for a while. I will update u if I hit it again.

Thanks!
-devsk





________________________________
From: Mike Isely <isely at isely.net>
To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
Sent: Sat, May 15, 2010 12:55:16 PM
Subject: Re: [pvrusb2] OOPs with latest standalone driver in 2.6.33.2

On Sat, 15 May 2010, devsk wrote:

> It looks like you came up with 25th Apr version. Let me try that.
> 
> -devsk
> 

Yes, in fact if you look at the change history for the 25-Apr version, 
the first item listed I believe is the fix for the oops that you got.

What had happened was that I had found and fix several nasty bugs on the 
24th and wanted to get that snapshot out right away.  Then afterwards 
yet more problems were found, which caused the extra snapshop on the 
very next day.

  -Mike


> 
> 
> 
> ________________________________
> From: devsk <funtoos at yahoo.com>
> To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> Sent: Sat, May 15, 2010 11:18:31 AM
> Subject: Re: [pvrusb2] OOPs with latest standalone driver in 2.6.33.2
> 
> This is after the fresh boot.
> 
> [    8.966000] pvrusb2: Hardware description: WinTV PVR USB2 Model 24xxx
> [    8.966000] usbcore: registered new interface driver pvrusb2
> [    8.966000] pvrusb2: 20100424 (from www.isely.net):Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
> [    8.966000] pvrusb2: Debug mask is 31 (0x1f)
> 
> Isn't that the latest?
> 
> This OOPs was a sort of hard lockup for me in the sense that everything (all FS read/write/umount operations e.g.) stopped in 'D' state after this. I had to sysrq my way out of it.
> 
> -devsk
> 
> 
> 
> 
> 
> ________________________________
> From: Mike Isely <isely at isely.net>
> To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
> Sent: Sat, May 15, 2010 9:48:26 AM
> Subject: Re: [pvrusb2] OOPs with latest standalone driver in 2.6.33.2
> 
> On Sat, 15 May 2010, devsk wrote:
> 
> > Mike,
> > 
> > I experienced the OOPs again during removal of the module.
> > 
>    [...]
> 
> > 
> > I think we haven't gotten all the races sorted as yet. Any ideas?
> 
> Can you please verify that you are actually running the latest standlone 
> driver?  The driver version running is reported to the kernel log but 
> you didn't include that in your clip (it's one of the *very* first 
> messages logged when the driver first loads).  The traceback looks an 
> awful lot like one of the problems that was already fixed.
> 
>   -Mike
> 
> 

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
_______________________________________________
pvrusb2 mailing list
pvrusb2 at isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2