I've found that the ohci-hcd driver may crash if there is a problem while it is initializing.
In the implementation(s) I'm looking at, the probe code will call the usb_hcd_x_remove function if there is a problem with the driver starting. The remove call will attempt to dereference ohci->regs which, at this point, is still zero. Thus, a page fault. The reason I've seen this is, what I believe, a change to the DMA page allocation code which requires a coherent_dma_mask field to be set in the device structure. My guess is that we'll need to check for an uninitialized driver when removing in case the register field has not yet been set. Comments? ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
