From owner-freebsd-current@FreeBSD.ORG Fri Sep 25 22:18:07 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 6F7A8106566C for ; Fri, 25 Sep 2009 22:18:07 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 2CD118FC15 for ; Fri, 25 Sep 2009 22:18:06 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n8PMI5Dt008028; Fri, 25 Sep 2009 18:18:05 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.2.2 (mail.netplex.net [204.213.176.10]); Fri, 25 Sep 2009 18:18:05 -0400 (EDT) Date: Fri, 25 Sep 2009 18:18:05 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Joe Marcus Clarke In-Reply-To: <1253916251.1274.25.camel@shumai.marcuscom.com> Message-ID: References: <426bed110909250623j44c25ba8o97ded8393f5297a9@mail.gmail.com> <20090925153212.67247375@ernst.jennejohn.org> <426bed110909251459p50ca5564mee568e14bd26d8cd@mail.gmail.com> <1253916251.1274.25.camel@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: hald spins in a poll/read loop against /dev/usb with CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2009 22:18:07 -0000 On Fri, 25 Sep 2009, Joe Marcus Clarke wrote: >> >> I've rebuilt hald (hal-0.5.11_26) after checking out 8/stable under >> /usr/src/sys. Same problem. A spin loop of poll/read, with /dev/usb >> responding to poll() but not to read(). > > Insufficient. You need to be running on a world/kernel which are in > sync with each other. You also need to make sure the libusb port is no > longer installed, and that you have run "make delete-old" after the > upgrade. Then rebuild hal. With regard to the libusb port problems, shouldn't the ports prefer/configure to use libusb20 when it is present, so that it wouldn't matter if libusb was installed or not? -- DE