Hi Alan,
CONFIG_USB_SUSPEND is not set.
Should I try to set it ?
I thought it is for something else from its attached
help, that's why I left it unset.
Thanks,
Paul
--- Alan Stern <[EMAIL PROTECTED]> wrote:
> Very interesting indeed. This indicates that the
> problem isn't with the
> uhci-hcd driver but higher up in the USB stack.
> It's also not an IRQ
> problem, as you have already realized. In brief,
> uhci-hcd resumed
> correctly and received the appropriate interrupt
> when you plugged in the
> device. But then the hub driver never got a
> corresponding status change
> event. (Or else the khubd thread had died, which is
> quite possible.)
>
> Can you build the USB drivers with
> CONFIG_USB_DEBUG=y, and post the
> dmesg log showing what happens following the
> suspend/resume + plug in a
> device? Also, can you say whether or not
> CONFIG_USB_SUSPEND is set?
> Finally, after plugging in the device, can you get
> the Alt-SysRq-T stack
> trace for the khubd process? (This may work out
> better if you switch to
> single-user mode and kill unnecessary daemons before
> doing the swsusp.)
>
> Alan Stern
>
>
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
