Sorry. Was a bit in a hurry.



David Brownell wrote:
Bernd Porr wrote:

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

static void ehci_work (struct ehci_hcd *ehci, struct pt_regs *regs)
{
printk("ehci_work\n");
printk("timer_action_done\n");
timer_action_done (ehci, TIMER_IO_WATCHDOG);
if (ehci->reclaim_ready) {
printk("end_unlink_async\n");
end_unlink_async (ehci, regs);
}
printk("scan_async\n");
scan_async (ehci, regs);
if (ehci->next_uframe != -1) {
printk("scan_periodic\n");
scan_periodic(ehci, regs);
}
/* the IO watchdog guards against hardware or driver bugs that
* misplace IRQs, and should let us run completely without IRQs.
*/
if ((ehci->async->qh_next.ptr != 0) || (ehci->periodic_sched != 0)) {
printk("timer_action\n");
timer_action (ehci, TIMER_IO_WATCHDOG);
}
}


If you modify ehci_stop() to del_timer_sync()
only after ehci_reset() is called, does that make
things better?
I'll try.


[ 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 ... ]
ok. I'll keep it.

- Dave
/Bernd



-------------------------------------------------------
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

Reply via email to