In message: <20040719145745.GH57678_at_darkness.comp.waw.pl> Pawel Jakub Dawidek <pjd_at_freebsd.org> writes: : Hello. : : Could someone investigate what's going on for the situation from the : subject? This panic is trivial to reproduce: : : # kldload umass.ko : <plug in your USB bar> : # kldunload umass : # kldload umass : <panic> : : It is not umass related! I think this problem is in our USB implementation. : : One more note with could be helpful. : When device is already inserted and I load USB driver, <drvname>_match : isn't called, but when driver was unloaded while device was in and it is : loaded again (as in my example) <drvname>_match is called and we have : a problem, because there are some stale data, I think (not everything : is cleaned up on kldunload?). : Ok, one more note. : You can also set 'break <drvname>_match' in DDB and try to compare : backtraces when device is removed while driver is loaded and when you : unload USB driver. I do know that loading the driver won't attach umass unless you remove and insert it again. WarnerReceived on Mon Jul 19 2004 - 20:35:47 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:02 UTC