From owner-freebsd-bugs@FreeBSD.ORG Tue Apr 1 21:40:05 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEC24106566B for ; Tue, 1 Apr 2008 21:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9F1D78FC13 for ; Tue, 1 Apr 2008 21:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m31Le54v058449 for ; Tue, 1 Apr 2008 21:40:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m31Le5f4058448; Tue, 1 Apr 2008 21:40:05 GMT (envelope-from gnats) Date: Tue, 1 Apr 2008 21:40:05 GMT Message-Id: <200804012140.m31Le5f4058448@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Volker Werth Cc: Subject: Re: kern/122126: [ed] [panic] panic when using WD-8013 with ed(4) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Volker Werth List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2008 21:40:05 -0000 The following reply was made to PR kern/122126; it has been noted by GNATS. From: Volker Werth To: Peter Much Cc: bug-followup@FreeBSD.org Subject: Re: kern/122126: [ed] [panic] panic when using WD-8013 with ed(4) Date: Tue, 01 Apr 2008 23:38:46 +0200 Dear Peter, thanks for all the requested infos. As running currently running a bit low on time, I'm unable to fully diagnose this issue really deep but I do have some first shots: I'm pretty sure, it's an interrupt handling problem My best hint for you for now is to update your BIOS. Please check your vendor site for an updated BIOS. If you really can't find one, we need to manually create an AML bugfix for your system as your AML code seems to be broken: > acpi_bus_number: root bus has no _BBN, assuming 0 As you wrote, you're able to panic your box even w/o ACPI enabled, this may not relate to your problem but my experience shows, when running with a good ACPI implementation, the box will not show much strange behaviour. These lines: pcib0: slot 4 INTD routed to irq 9 via \\_SB_.LNKD pcib0: slot 9 INTA routed to irq 9 via \\_SB_.LNKD pcib0: slot 10 INTA routed to irq 9 via \\_SB_.LNKC pcib0: slot 10 INTB routed to irq 9 via \\_SB_.LNKD seem to indicate, the PCI slots aren't routed to IRQs nicely. Please try if you can fix this in the BIOS settings. Now, a bit for the real issue: Your box is receiving a packet from the network (ed0). ed0 fires an IRQ which is handled by the kernel. While the kernel tries to dispatch the IRQ to the right handler (the ed0 driver in this case), the box panics - for whatever reason but the "fault virtual address" is looking suspicious. With everything I've now checked on your issue, I'm always coming to the point, there's something wrong with the ithread dispatcher. Volker