From owner-freebsd-current@FreeBSD.ORG Sat Aug 8 20:08:00 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E93BC1065673 for ; Sat, 8 Aug 2009 20:08:00 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id C3BE38FC1A for ; Sat, 8 Aug 2009 20:07:59 +0000 (UTC) Received: from ice.local ([10.0.0.115]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n78K7xGo048582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Aug 2009 13:07:59 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <4A7DDB1F.5020709@errno.com> Date: Sat, 08 Aug 2009 13:07:59 -0700 From: Sam Leffler User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: Greg Rivers References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Misty-Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: hald broken with USB drives since 8.0-BETA2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 08 Aug 2009 20:08:01 -0000 Greg Rivers wrote: > I've had to disable hald on my Acer One netbook since 8.0-BETA2. Now > hald seems to work only the first time a USB drive is attached. The > drive is detected and mounted, and can be unmounted and remounted via > kde3's media interface. > > But if I unmount the drive and detach it, hald wedges the USB buss. No > further USB connections (any device, not just disks) are detected, and > hald becomes unkillable. > > Has anyone else experienced this? Any suggestions for troubleshooting? > It is my understanding there is an outstanding bug in the usb code handling device enumeration for umass devices (and some others). This manifests itself by the symptoms you see. I believe the explorer thread is blocked so device detection stops. I have personally seen this bug. Unfortunately the person that was going to fix this has been away for awhile and will not return for another month so unless someone else fixes it 8.0 will ship with the bug. Sam