Date: Fri, 19 Nov 2004 15:59:46 -0500 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-acpi@FreeBSD.org Cc: Ruslan Ermilov <ru@FreeBSD.org> Subject: Re: New ACPI PCI Link Routing code Message-ID: <200411191559.46209.jhb@FreeBSD.org> In-Reply-To: <20041118084627.GA72018@ip.net.ua> References: <200411111737.00537.jhb@FreeBSD.org> <20041118001947.GA53060@ip.net.ua> <20041118084627.GA72018@ip.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 18 November 2004 03:46 am, Ruslan Ermilov wrote: > On Thu, Nov 18, 2004 at 02:19:47AM +0200, Ruslan Ermilov wrote: > > On Wed, Nov 17, 2004 at 05:44:53PM -0500, John Baldwin wrote: > > [...] > > > > > Erm, unless I've got a logic bug I don't run the KASSERT() for zero > > > interrupts. Oh darn, I left a bogus KASSERT() in in the function that > > > does the actual routing. The assertion's on lines 497 and 511 can be > > > dropped. I'll update the patch in a second. > > > > With an updated patch, I no longer get panic on boot, and there > > are no more interrupt storms, but the latter is probably at the > > cost of old bug re-introduced. My dc(4) PCCard doesn't get a > > correct IRQ, "dc0: watchdog timeout". > > I've put a verbose boot output here, as requested: > > http://people.freebsd.org/~ru/dmesg.boot Looks like it hung everything off of IRQ 9 since the BIOS didn't preset any device IRQs. What was the behavior prior to this patch? -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200411191559.46209.jhb>