From owner-freebsd-current Wed Dec 6 15:44:10 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 15:44:08 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 8AB7A37B401; Wed, 6 Dec 2000 15:44:07 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eB6Ni6L55310; Thu, 7 Dec 2000 00:44:06 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: current@freebsd.org, nsayer@freebsd.org Subject: Re: USB related commit leads to hung systems if USB-IRQ=Disabled in BIOS In-Reply-To: Your message of "Wed, 06 Dec 2000 15:46:31 PST." <200012062346.eB6NkVF00891@mass.osd.bsdi.com> Date: Thu, 07 Dec 2000 00:44:06 +0100 Message-ID: <55308.976146246@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200012062346.eB6NkVF00891@mass.osd.bsdi.com>, Mike Smith writes: >> > >> > In my bios I have PnPOS=NO, USB-IRQ=Disabled. >> > >> > The commit below results in a PCI interrupt storm and a terminally >> > wedged system right after interrupts are enabled. >> >> This would be a bug in the UHCI or OHCI driver then. You can avoid it by >> not running the driver. > >I should have mentioned; you can probably also avoid it by letting your >BIOS give the USB controller an IRQ, since it'll almost certainly also >perform whatever initialisation the driver is currently missing out on. Right, that is what I did once I realized that this particular commit was the culprit. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message