Aki M Laukkanen wrote:
>
> On Sat, 25 Mar 2000, David Brownell wrote:
>
> > Could someone who knows how it's _supposed_ to be working please
> > sumamrize the status of power management support and USB?
>
> Alan posted an interim fix to this some time ago:
> http://electricrain.com/lists/archive/linux-usb/2000/03/msg00628.html
Didn't seem to make a difference in my setup.
> > - When I shutdown the machine and power it back up,
> > USB doesn't seem to work at all. rmmod/modload
> > of usb-ohci makes it come alive again.
>
> Infact I got a nice oops.
With pre4-2 I get an Oops too -- a new behavior for me. The
'khubd' thread gets blown away. To recover I've got to reload
the 'usbcore' module (unmount/remount /proc/bus/usb, reload
other USB drivers). The failure was different before.
When it resumes, it's not re-enabling the connected device; in
fact, it's forcibly disconnecting it; after disconnect, Oops!
I suspect something ought to be doing a USB reset on resume, and
causing the bus (if not also the controller) to re-initialize.
It will be typical to unplug and rearrainge USB devices while a
laptop is is suspended, which seems the primary use case for
the suspend/resume code paths.
As it stands now it's trying to go along the other transition
from the SUSPEND state (fig. 6.1 of OHCI spec), which of course
ought to work in this particular test setup (same devices, so
no renumbering is needed) with no Oops.
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
