I've added some debug info into the ehci code:
When I shut down the kernel I get following function calls:
ehci_stop ehci_work timer_action_done scan_async scan_periodic
I can't quite make sense of what you're saying. After ehci_stop() returns, ehci_work() should never again be called.
What do the driver's normal diagnostics say? (That is, CONFIG_USB_DEBUG.)
If you modify ehci_stop() to del_timer_sync() only after ehci_reset() is called, does that make things better?
[ Note I've updated the Subject: to stop implying this is related to the recent patch, since you also said it happened without that patch ... ]
- Dave
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
