From owner-freebsd-current@FreeBSD.ORG Mon Dec 27 22:11:13 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 9D26816A53C for ; Mon, 27 Dec 2004 22:11:11 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46D2543D1D for ; Mon, 27 Dec 2004 22:11:11 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 5975 invoked from network); 27 Dec 2004 22:11:11 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 27 Dec 2004 22:11:10 -0000 Received: from [10.50.41.243] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iBRMArTN089244; Mon, 27 Dec 2004 17:11:05 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 27 Dec 2004 16:41:51 -0500 User-Agent: KMail/1.6.2 References: <6.0.3.0.0.20040517154946.06d23d60@64.7.153.2> <6.0.3.0.0.20040603220621.045655e0@64.7.153.2> <20041208184326.W1740@epsplex.bde.org> In-Reply-To: <20041208184326.W1740@epsplex.bde.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412271641.51744.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Bruce Evans cc: Mike Tancsa Subject: Re: sio / puc wedging on both -current and -stable 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: Mon, 27 Dec 2004 22:11:13 -0000 On Wednesday 08 December 2004 02:52 am, Bruce Evans wrote: > Long ago, On Thu, 3 Jun 2004, Mike Tancsa wrote: > > Just a quick recap. I can fairly easily trigger an interrupt storm on > > these machines with USB enabled in the BIOS. If I disable it, I dont > > have a problem and all works well.... However, what I accidently came > > across today, was that if I load the USB drivers as a kld, I can *not* > > wedge the machine. Note the bottom of the following diff > > I can now explain this. When usb is in the kernel proper, it normally > gets the interrupt first and exposes bugs in sio (see other mail -- > there is a conflict but sio ignores the error). When usb is in a > module, sio normally gets the interrupt first. There is again a > conflict but usb doesn't ignore the error. > > > diff dmesg.kld dmesg.static > > > > < uhci2: port 0xb400-0xb41f > > irq 12 at device 29.2 on pci0 > > < uhci2: Could not allocate irq > > < device_probe_and_attach: uhci2 attach returned 6 > > < uhci2: port 0xb400-0xb41f > > irq 12 at device 29.2 on pci0 > > < uhci2: Could not allocate irq > > < device_probe_and_attach: uhci2 attach returned 6 > > This shows uhci2 not ignoring the error. I'd like to force sio(4) devices attached via PCI to just always share the interrupt and not use INTR_FAST for now. That would allow sio and usb to play well in both situations. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org