From owner-freebsd-stable@FreeBSD.ORG Thu Jun 25 11:34:03 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2C7C106564A for ; Thu, 25 Jun 2009 11:34:03 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id A8E438FC0A for ; Thu, 25 Jun 2009 11:34:03 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 0ED60381C5F for ; Thu, 25 Jun 2009 07:34:03 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 25 Jun 2009 07:34:03 -0400 X-Sasl-enc: riBG2kSArQkKGx3XcweQtwiyou9ibcGF8vt452yFv929 1245929642 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 9A4CD3984B for ; Thu, 25 Jun 2009 07:34:02 -0400 (EDT) Message-ID: <4A4360A9.6000404@incunabulum.net> Date: Thu, 25 Jun 2009 12:34:01 +0100 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.21 (X11/20090412) MIME-Version: 1.0 To: FreeBSD stable X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: USB critically broken under RELENG_7 on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jun 2009 11:34:04 -0000 Hi, Since jhb@ committed the fixes for ULi SATA, I updated my kernel+world on my amd64 desktop machine. So far so good. I updated again Tuesday. Unfortunately I am now seeing USB warnings during boot: uhub1: device problem (TIMEOUT), disabling port 1 I get messages like this for any and all attempts to attach USB devices. ...It works just fine in Windows XP, and worked just fine in RELENG_7 before. What's going on? it doesn't appear to be a repeat of the HAL / libpciaccess saga from February as it happens from boot. This is an ALi OHCI + EHCI controller, fwiw. usbdevs -v spews a lot of 'addr 0 should never happen!'. Could this be an interrupt handling bug of some kind? cheers, BMS