> Hook up a serial console, likely you'll see a kernel > oops trace appear on that console. Analyse it with > ksymoops on 2.4 kernels; 2.6 is easier to develop > with > since "kksymoops" is built in.
Thanks. I will follow your suggestion in the near future. Last night, I found the problem causing the trouble. In my completion handler, I called usb_clear_halt if urb->status<0. When the cable is unplugged, the completion handler is called with urb->status = -EOVERFLOW (why is it called before "disconnect"?), and the system hangs at usb_clear_halt. I thought there should be some protection around for this situation, as the system already knows some bad things happen. Btw, in which situation should I use usb_clear_halt and What is that for? Thanks Dan ===== ---------------------------------------------------------- Have fun! __________________________________________________________ __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
