Date: Mon, 19 Jul 2004 16:57:45 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Unloading USB driver while device is attached. Message-ID: <20040719145745.GH57678@darkness.comp.waw.pl>
index | next in thread | raw e-mail
[-- Attachment #1 --] 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. -- Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA++FpForvXbEpPzQRAtk4AKCB8Y3dJ4lrK6DKCjyhl44nIftJJwCfaLSH PgDklVxfMdW8o9OfFhj7DUM= =ib6s -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040719145745.GH57678>