From owner-freebsd-current@FreeBSD.ORG Sun Sep 26 12:14:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44F9616A4CE for ; Sun, 26 Sep 2004 12:14:49 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 270A043D39 for ; Sun, 26 Sep 2004 12:14:48 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail 26224 invoked by uid 65534); 26 Sep 2004 12:14:47 -0000 Received: from p5089EAA9.dip.t-dialin.net (EHLO ms.homeip.net) (80.137.234.169) by mail.gmx.net (mp009) with SMTP; 26 Sep 2004 14:14:47 +0200 X-Authenticated: #15946415 Received: from [10.0.0.100] (helo=[10.0.0.100]) by ms.homeip.net with asmtp (TLSv1:AES256-SHA:256) id 1CBXvj-000FPs-O4 for freebsd-current@freebsd.org; Sun, 26 Sep 2004 14:15:03 +0200 Message-ID: <4156B2AF.9020305@gmx.de> Date: Sun, 26 Sep 2004 14:14:39 +0200 From: Jochen Gensch User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re:Detaching USB stick crashes BETA4/BETA5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Sep 2004 12:14:49 -0000 > Ian Dowse also is having problems in this area. He suggested the > following patch to me. I have some concerns about the patch, but they > are theoretical (what does it mean when a parent is detached, but all > its children are attached?), but given the current state of the newbus > code it will fix the problem for you. Apparently this patch really stops the kernel panic. BUT there seems to be a problem with devfs, when reattaching the usb hub / devices. Permissions set in /etc/devfs.conf do not take effect any more. Even worse, if you do a ls -l /dev, then all devices show permissions like '0'. My System is a 5.3-BETA6 built yesterday. So maybe your concern is right in some way... hopefully this is gonna be fixed in 5.3-RELEASE!? Jochen