Date: Mon, 21 May 2001 12:24:52 +0100 (BST) From: Nick Hibma <n_hibma@qubesoft.com> To: Mike Smith <msmith@FreeBSD.ORG> Cc: John Polstra <jdp@polstra.com>, <current@FreeBSD.ORG> Subject: Re: GENERIC kernel hangs at boot (uhci-related) Message-ID: <20010521122024.O94091-100000@henny.webweaving.org> In-Reply-To: <200105191902.f4JJ2tK01471@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010521122024.O94091-100000>