From owner-freebsd-current Thu Sep 27 11:58:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id B813037B40A; Thu, 27 Sep 2001 11:58:25 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.3/8.11.3) id f8RIwOH70250; Thu, 27 Sep 2001 20:58:24 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200109271858.f8RIwOH70250@freebsd.dk> Subject: Re: panic: inthand_add: Can't initialize ICU In-Reply-To: "from John Baldwin at Sep 27, 2001 11:13:02 am" To: John Baldwin Date: Thu, 27 Sep 2001 20:58:24 +0200 (CEST) Cc: Maxim Sobolev , current@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 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 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: 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