From owner-freebsd-current Wed Dec 6 15:37:23 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 15:37:20 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (dhcp245.osd.bsdi.com [204.216.28.245]) by hub.freebsd.org (Postfix) with ESMTP id 416C937B402; Wed, 6 Dec 2000 15:37:18 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB6NkVF00891; Wed, 6 Dec 2000 15:46:31 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012062346.eB6NkVF00891@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Poul-Henning Kamp , 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:35:42 PST." <200012062335.eB6NZgF00739@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 15:46:31 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > 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. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message