On Mon, May 29, 2000 at 04:31:16PM +0300, Aki M Laukkanen wrote:
> On Sun, 28 May 2000, Greg KH wrote:
> > When the Visor completes whatever it was told to do, it disconnects from
> > the usb bus, this causes the attached oops which looks suspiciously like a
> > slab poisoning error.
>
> I don't see any other choice. At the time usb_disconnect is called someone
> has already freed the hub.
That's all I can think of too, but I can't see where it is happening either.
> o Sleeps. At this point someone could call usb_disconnect()
> or rather usb_free_dev() for the hub. The question is how? The occurences
> of these in usb-ohci seem to jive with usb-uhci usage and seem highly
> unlikely. You weren't resuming or rmmod:ing usb-ohci at the time I assume.
No I'm not. But what is different is that the Visor does a disconnect
from the bus when it is finished. That is when this oops happens.
Does anyone else see this if they yank out a device while it is open
doing things on OHCI? All my other usb devices are packed away in a box
somewhere, so all I have to test this with is a Visor.
thanks,
greg k-h
greg@(kroah|wirex).com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
