> > This is consistent with Ben's comments.
> 
> I don't read PPC assembly ... what's that mean in "C"?  :)

What I posted David, didn't you see my post ? In fact you did as you
also replied :)
> 
> > I can try sleeping it with the mouse disconnected over the next couple
> > of days. It seems to me that the oops is more likely to occur when
> > sleeping for a long period, such as overnight, or during the day when I
> > am at work. So far, long sleeps have always resulted in the oops,
> > whereas short sleeps have given an oops only once out of maybe seven or
> > eight tries.
> 
> And the device stayed connected the entire time?

Maybe it hit the "can't suspend" case and got disconnected at sleep time
or something like that, and the driver didn't go all the way through
disconnection before actual machine sleep ?
> 
> > CONFIG_USB_SUSPEND was NOT set.
> 
> Might be interesting to see what happens if you do use it.
> It strikes me that maybe disconnection is mis-handled if
> that's not set...

Yah, especially if it's asynchronous ...
> 
> > By the way, I tried to use ksymoops to get some better information
> > yesterday, but I don't have a /proc/ksyms. Is that normal, or is there a
> > configuration switch somewhere I should turn on?
> 
> On 2.6 kernels you don't need ksymoops any more.
> 
> - Dave



-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to