Date: Sat, 05 Apr 2008 16:10:10 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: koitsu@freebsd.org Cc: antik@bsd.ee, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: USB to RS232 converter problem (prolific chip) Message-ID: <20080405.161010.1169637862.imp@bsdimp.com> In-Reply-To: <20080405215838.GA27195@eos.sc1.parodius.com> References: <200804060024.39019.antik@bsd.ee> <200804060033.50609.antik@bsd.ee> <20080405215838.GA27195@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20080405215838.GA27195@eos.sc1.parodius.com>
Jeremy Chadwick <koitsu@freebsd.org> writes:
: Bottom line: the current FreeBSD USB stack is very fragile and
: unreliable. You may want to try the usb4bsd kernel patches (I think
: that's what it's called), some have had better luck with those. Search
: the web.
This crash has nothing to do with the usb stack. The root cause is
the device deletion code nulls out a pointer. There's a routine that
is sleeping which is woken up and the null pointer gets dereferenced
leading to the crash.
The current usb stack isn't as fragile as it was in the 5.x days.
While there are problems, this one isn't due to that. The same thing
happens when you eject a PC Card 16550 COM device, due to the same
bug.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080405.161010.1169637862.imp>