From owner-freebsd-current Sat May 19 11:38:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CDC9437B422 for ; Sat, 19 May 2001 11:38:24 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f4JIcN027680 for ; Sat, 19 May 2001 11:38:23 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f4JIcMg98239; Sat, 19 May 2001 11:38:22 -0700 (PDT) (envelope-from jdp) Date: Sat, 19 May 2001 11:38:22 -0700 (PDT) Message-Id: <200105191838.f4JIcMg98239@vashon.polstra.com> To: current@freebsd.org From: John Polstra Subject: Re: GENERIC kernel hangs at boot (uhci-related) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , John Polstra wrote: > > I have a strong suspicion that backing out "sys/pci/uhci_pci.c" > revision 1.32 will make this problem go away. I'll test that next. Yep, I reverted that file to revision 1.31 and the hangs went away even with the USB IRQ disabled in the BIOS. The change in revison 1.32 apparently assumes that if no IRQ is assigned to the uhci device, the only possible reason is because PNP OS is turned on. But in my case the actual reason is different -- the IRQ is disabled in the BIOS. Is it feasible for the attach routine to distinguish between these two cases? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message