From owner-freebsd-usb@FreeBSD.ORG Sat Apr 5 22:11:28 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 618FF1065675; Sat, 5 Apr 2008 22:11:28 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 157D08FC13; Sat, 5 Apr 2008 22:11:28 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m35M9KLx090205; Sat, 5 Apr 2008 16:09:20 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 05 Apr 2008 16:10:10 -0600 (MDT) Message-Id: <20080405.161010.1169637862.imp@bsdimp.com> To: koitsu@freebsd.org From: "M. Warner Losh" 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> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: USB to RS232 converter problem (prolific chip) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Apr 2008 22:11:28 -0000 In message: <20080405215838.GA27195@eos.sc1.parodius.com> Jeremy Chadwick 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