[pvrusb2] Did pvrusb2 cause a kernel oops?

[Roger]

On Tue, 2009-06-02 at 19:33 -0500, Mike Isely wrote:
> Looks like a crash happened while the driver tied to tear down its sysfs 
> interface.  There isn't much else I can glean from this except to say 
> that the pvrusb2 driver and pretty much any form of Linux suspend have 
> never played well together.  Realize that the pvrusb2 hardware is 
> self-powered - it's going to stay on even if the PC turns off.  This 
> behavior is kind of out of scope for what one might expect when trying 
> to suspend a PC.  I would assume that in this case the suspend process 
> should try to force a hot-unplug of the USB connected devices first, but 
> I don't really know and in any case it's outside the control of the 
> pvrusb2 driver.  Admittedly the driver should never oops under any 
> circumstance, however I don't really follow what this circumstance is - 
> i.e. exactly what context is being used to force out the driver here.

Exactly.  And since I have usb compiled at modules, looks like suspend
tried to unload everything and this might have occurred do to lirc
locking up on stop.  (I tried hibernate once & it seemed to stop the
hibernation process after "/etc/init.d/lircd stop"... Invoking hibernate
again and it proceeded to hibernate & oops.  Likely lircd never *really*
did stop and locked up stopping -- or something similar to a timing
issue.

I'll keep an eye on this & post any additional I get -- or if I resolve
it.

-- 
Roger
http://rogerx.freeshell.org