From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 07:52:58 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 03BE716A4CE for ; Wed, 8 Dec 2004 07:52:58 +0000 (GMT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5028043D4C for ; Wed, 8 Dec 2004 07:52:57 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])iB87qtKP008863; Wed, 8 Dec 2004 18:52:55 +1100 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) iB87qrcH022387; Wed, 8 Dec 2004 18:52:54 +1100 Date: Wed, 8 Dec 2004 18:52:53 +1100 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Mike Tancsa In-Reply-To: <6.0.3.0.0.20040603220621.045655e0@64.7.153.2> Message-ID: <20041208184326.W1740@epsplex.bde.org> References: <6.0.3.0.0.20040517154946.06d23d60@64.7.153.2> <6.0.3.0.0.20040603220621.045655e0@64.7.153.2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 08 Dec 2004 12:53:08 +0000 cc: freebsd-current@freebsd.org 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: Wed, 08 Dec 2004 07:52:58 -0000 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. Bruce