Re: USB suspend problem with kernel 2.6.17

On Thu, 13 Sep 2007, Tiago Salem Herrmann wrote:

> It seems that the USB devices were virtually unplugged and then 
> reattached. It only happens if there is an external *and self-powered 
> USB device plugged, and due to this situation, the mass storage devices 
> are renamed. Considering the sda device contains the root partition, and 
> after the resume it is renamed to sdc, the system crashes.

In the log it appears that much the same thing happened without the 
external self-powered device -- except that it worked!

> > For testing purposes you can always try reverting the "usb persist" 
> > patch.
> >   
> We can't revert the usb_persist patch since the root partition is in the 
> usb mass storage.
> Without usb_persist patch, we can't even resume the system.
> Searching for information we found this thread, and it seems to be 
> related to our problem.
> http://lkml.org/lkml/2007/3/27/149
> Do you still have that patch you made which manages "virtual replugging"?

I'm not sure what you mean.  There never was such a patch, AFAICR.

> > You should post a dmesg log showing what happens during a resume with 
> > only bus-powered devices attached; maybe it will contain some clues.
> >   
> I've uploaded the dmesg to
> http://users.mandriva.com.br/~salem/dmesg_suspend.txt
> 
> The only way to get it was using netconsole.

It's good, but not good enough.  To tell what's really happening you 
need to enable CONFIG_USB_DEBUG.

Alan Stern


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel