Date: Fri, 6 Apr 2012 11:19:10 -0500 From: Terence Telkamp <Terence_Telkamp@DELL.com> To: "freebsd-usb@freebsd.org" <freebsd-usb@freebsd.org> Subject: RE: Impact of changes made to umass.c at r232358 Message-ID: <975552A94CBC0F4DA60ED7B36C949CBA03DB0C8BB2@shandy.Beer.Town> In-Reply-To: <975552A94CBC0F4DA60ED7B36C949CBA03DB0C8BA5@shandy.Beer.Town> References: <975552A94CBC0F4DA60ED7B36C949CBA03DB0C8BA5@shandy.Beer.Town>
next in thread | previous in thread | raw e-mail | index | archive | help
One thing I forgot to mention is that I have a machine in the kernel debugg= er after the panic, so I can capture more information if any would be helpf= ul. -----Original Message----- From: owner-freebsd-usb@freebsd.org [mailto:owner-freebsd-usb@freebsd.org] = On Behalf Of Terence Telkamp Sent: Friday, April 06, 2012 11:17 AM To: freebsd-usb@freebsd.org Subject: Impact of changes made to umass.c at r232358 I am seeing a kernel panic in FreeBSD 8.1, which is reproduced after physic= ally attaching and detaching a USB device several times. The kernel debugg= er shows that the panic happens in camisr where the cam_sim and its associa= ted mutex are clearly destroyed. sim->refcount is 0, sim->softc is 1 (UMAS= S_GONE), and the sim->mtx is destroyed (mtx_lock =3D 6). This looks very similar to FreeBSD PR kern/153514, which is unfortunately u= nresolved. http://www.freebsd.org/cgi/query-pr.cgi?pr=3D153514 Is it possible that the changes made to umass.c at r232358 might fix this i= ssue? Terence Telkamp Storage Development Associate Engineer II Dell | Compellent _______________________________________________ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?975552A94CBC0F4DA60ED7B36C949CBA03DB0C8BB2>