David Brownell wrote: >Oopses normally dump me into KDB, and that's not happening. >So I don't think there's an oops involved. > When things get this bad, I hook up the serial console and insert a few widely spaced printk()'s into the suspect functions. Then I do a binary search until I pinpoint the exact point of failure. This works as long as something doesn't kill the system before the data can get out of the serial port. It usually gets you fairly close to the problem line, in any case. From my experience, I would be very suspicious of something going very wrong in your interrupt handler. -- Mark McClelland [EMAIL PROTECTED] _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
- Re: [linux-usb-devel] How to diagnose kernel hangs? Greg KH
- [linux-usb-devel] How to diagnose kernel hangs? David Brownell
- Re: [linux-usb-devel] How to diagnose kernel hangs? David Brownell
- Re: [linux-usb-devel] How to diagnose kernel hangs? Mark McClelland
- Re: [linux-usb-devel] How to diagnose kernel hangs? David Brownell
- Re: [linux-usb-devel] How to diagnose kernel han... Stephen Williams
- Re: [linux-usb-devel] How to diagnose kernel hangs? Matthew Dharm
- Re: [linux-usb-devel] How to diagnose kernel han... David Brownell
- Re: [linux-usb-devel] How to diagnose kernel hangs? David Brownell
- Re: [linux-usb-devel] How to diagnose kernel hangs? Matthew Dharm
- Re: [linux-usb-devel] How to diagnose kernel hangs? Sancho Dauskardt
- Re: [linux-usb-devel] How to diagnose kernel han... Matthew Dharm
- RE: [linux-usb-devel] How to diagnose kernel hangs? Nat Ersoz