From owner-freebsd-arch Mon Oct 14 10:10: 9 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AE7C37B401 for ; Mon, 14 Oct 2002 10:10:08 -0700 (PDT) Received: from genius.tao.org.uk (genius.tao.org.uk [212.135.162.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A3EC43EAC for ; Mon, 14 Oct 2002 10:10:07 -0700 (PDT) (envelope-from joe@genius.tao.org.uk) Received: by genius.tao.org.uk (Postfix, from userid 100) id 3FD264637; Mon, 14 Oct 2002 18:09:49 +0100 (BST) Date: Mon, 14 Oct 2002 18:09:49 +0100 From: Josef Karthauser To: John Birrell Cc: arch@freebsd.org Subject: Re: USB driver design issues Message-ID: <20021014170949.GB25180@genius.tao.org.uk> References: <20021014083622.G261@freebsd1.cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021014083622.G261@freebsd1.cimlogic.com.au> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 14, 2002 at 08:36:23AM +1000, John Birrell wrote: > I have a few problems with the design of the USB drivers in > FreeBSD. From the investigation I've done so far, the problems > appear to arise from the inability of the code to handle > kldload and kldunload. The result is that I can crash a > RELENG_4 kernel (and probably a -current one too since the USB > driver code is similar) simply by connecting or disconnecting > the USB cable. Sub-optimal. There are known bugs in -stable that I imagine won't ever get fixed. The stack has been reengineered in NetBSD though and ported to -current, but it remains to be seen whether anyone's got the time to port it to -stable. There was a chance that I was going to do it last month, but the sponsor pulled out at the last minute and I'm busy enough to not have the time to attempt this in my free-time. I don't know about the issue that you mention particularly, but it does appear that device disconnection is now very stable in -current. It may be worth trying to put a current box together to try it, or finding someone who can test your driver on a -current box. Joe. -- "As far as the laws of mathematics refer to reality, they are not certain; and as far as they are certain, they do not refer to reality." - Albert Einstein, 1921 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message