From owner-freebsd-current Mon May 21 4:24:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from henny.webweaving.org (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id C9B3237B43C; Mon, 21 May 2001 04:24:54 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.11.3/8.11.3) with ESMTP id f4LBOqu94489; Mon, 21 May 2001 12:24:53 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Mon, 21 May 2001 12:24:52 +0100 (BST) From: Nick Hibma X-X-Sender: To: Mike Smith Cc: John Polstra , Subject: Re: GENERIC kernel hangs at boot (uhci-related) In-Reply-To: <200105191902.f4JJ2tK01471@mass.dis.org> Message-ID: <20010521122024.O94091-100000@henny.webweaving.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 > > Could be, and I certainly don't know much about this code. But > > it seems like the driver is being given reason to assume it has a > > working device when it doesn't really have one. I assume the device > > is unusable without its interrupt, so shouldn't it fail at probe or > > attach time? > > Yes, it should. It's not bright enough to do that yet. 'It' in the second case refers to the PCI irq allocation code I presume? An irq that is 0 or 255 is invalid and should not be allocated to a PCI device. But speaking about rev1.32, how would you assign an interrupt as is stated in the log message for rev1.32? Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message