Date: Thu, 27 Sep 2001 20:58:24 +0200 (CEST) From: Søren Schmidt <sos@freebsd.dk> To: John Baldwin <jhb@FreeBSD.ORG> Cc: Maxim Sobolev <sobomax@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: panic: inthand_add: Can't initialize ICU Message-ID: <200109271858.f8RIwOH70250@freebsd.dk> In-Reply-To: <XFMail.010927111302.jhb@FreeBSD.org> "from John Baldwin at Sep 27, 2001 11:13:02 am"
next in thread | previous in thread | raw e-mail | index | archive | help
It seems John Baldwin wrote:
> > I found that I am no longer able to boot -current kernel on my machine. The
> > system panices right after initialising ed0 driver:
> >
> > [...]
> > ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xe800-0xe81f irq 9 at device
> > 9.0 on pci0
> > panic: inthand_add: can't initialize ICU
> >
> > Attached please find verbose kernel bootup messages obtained from the last
> > good kernel from about a week ago.
> >
> > Please fix.
>
> Could you, say, add a printf to icu_set() to print out the passed in interrupt
> number before it returns EINVAL? Also, adding a call to debugger
> (Debugger("foo");) and getting a stack trace would be very helpful.
I see the same thing here on my latitude, the passed irq is 0xb, I dont
have the stack trace written down (too damn long) but its when it attaches
the pcic controller..
-Søren
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?200109271858.f8RIwOH70250>