From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 20:31:06 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE11316A4B3 for ; Thu, 25 Sep 2003 20:31:06 -0700 (PDT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A3FC44003 for ; Thu, 25 Sep 2003 20:31:05 -0700 (PDT) (envelope-from bfoz@terrandev.com) Received: from terrandev.com (12-234-26-98.client.attbi.com[12.234.26.98]) by comcast.net (sccrmhc12) with SMTP id <2003092603310401200p793ve> (Authid: bfoz); Fri, 26 Sep 2003 03:31:04 +0000 Message-ID: <3F73B467.5080500@terrandev.com> Date: Thu, 25 Sep 2003 20:37:11 -0700 From: Brandon Fosdick User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030706 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ian Dowse References: <200309251850.aa69426@salmon.maths.tcd.ie> In-Reply-To: <200309251850.aa69426@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: stable@freebsd.org cc: Andrew Atrens Subject: Re: fix/workaround for usb probe lockups on nForce2 mbs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2003 03:31:06 -0000 Ian Dowse wrote: > In message <3F72659E.8090809@nortelnetworks.com>, Andrew Atrens writes: > >>The attached patch fixes the boot lockups I've been experiencing on my >>nForce2 (A7N8X-Deluxe) motherboards when usb devices are on the bus at >>boot time. >> >>Looks like something in usb_explore is (inadvertently?) enabling >>interrupts if it detects a device on a port. The fix is, during hub >>attach, to not assume that interrupts are off when we access the hub in >>'polling' mode. > > > Great, thanks for tracking it down! It sounds very similar to a > problem people were having before with FAST_IPSEC where interrupts > were being enabled and confusing the USB code. You have a "uhci" > rather than an "ohci" controller I assume? If so, coould you try > the following patch instead? Unfortunately I don't have anything > to test this on, but it in theory it should work around this class > of problems by backporting from -CURRENT some logic for avoiding > interrupts in polling mode. My A7N8X-Deluxe has an ohci, not a uhci. I haven't tried either patch yet, but I will in a minute.