Date: Wed, 8 Dec 2004 18:52:53 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-current@freebsd.org Subject: Re: sio / puc wedging on both -current and -stable Message-ID: <20041208184326.W1740@epsplex.bde.org> In-Reply-To: <6.0.3.0.0.20040603220621.045655e0@64.7.153.2> References: <6.0.3.0.0.20040517154946.06d23d60@64.7.153.2> <6.0.3.0.0.20040603220621.045655e0@64.7.153.2>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <Intel 82801DB (ICH4) USB controller USB-C> 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: <Intel 82801DB (ICH4) USB controller USB-C> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041208184326.W1740>