On Wed, 14 Jan 2004, Stavros Markou wrote: > Alan Stern wrote: > > >Do you know why usb_disconnect() is getting called at all? Is it > >happening inside your call to usb_reset_device()? Or is it happening > >sometime later? Can you post the stack trace from your system panic? > > > > > > > Disconnect is called when I unplug the wlan card. In the case of a > dataflash device when device_del is called dev->parent is not NULL > but in the case of eeprom device dev->parent is NULL. My opinion is that > the use of __usb_reset_device (ex usb_physical_reset_device) by the one > type of device and not the other has nothing to do with the fact that > when I unplug those devices I get two distinct results.
Well, when is dev->parent getting set to NULL? It should have a non-zero value at the time your probe() routine is called. Presumably something in the __usb_reset_device() routine is erasing that value. You can try putting printk statements around your call to reset_device to see if that is really the case. You should also put a printk in your driver's disconnect routine, to see when it is called and make sure it isn't getting called twice. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
