On x86, there is no OOps, it just freezes. On ia64, I get a nice MCA
and from that we can infer that a USB host controller read from
address 0xf0000000 caused the problem but since this is asynchronous
to the kernel's code path, the instruction pointer etc. in the MCA
state dump isn't terribly helpful.
Does that 0xf0000000 (on ia64) match any obvious address mapping of the null pointer -- like a dma mapping? I'm not sure that if the HID driver were to pass a null buffer pointer, it would be caught anywhere.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
