From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 10 00:26:38 2006 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90E0D16A420; Fri, 10 Feb 2006 00:26:38 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ADAA43D45; Fri, 10 Feb 2006 00:26:38 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 3539172DDD; Thu, 9 Feb 2006 16:26:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2D62E72DCB; Thu, 9 Feb 2006 16:26:38 -0800 (PST) Date: Thu, 9 Feb 2006 16:26:38 -0800 (PST) From: Doug White To: Steve Rieger In-Reply-To: <200602072247.k17MlPES015846@www.freebsd.org> Message-ID: <20060209162213.I10921@carver.gumbysoft.com> References: <200602072247.k17MlPES015846@www.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/93002: amd64 (6.0) coredumps at unpredictable times X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2006 00:26:38 -0000 On Tue, 7 Feb 2006, Steve Rieger wrote: > Fatal trap 1: privileged instruction fault while in kernel mode > instruction pointer = 0x8:0xffffffff8040d5ea > stack pointer = 0x10:0xffffffffb54df6d0 > frame pointer = 0x10:0xffffffffa5171000 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 60492 (as) > trap number = 1 > panic: privileged instruction fault This is a very atypical trap. If you were running -CURRENT it'd indicate a bug, but the location of the trap isn't around any sort of privilieged instruction which leads me to believe you have a hardware issue. To check, can you please load this dump back into gdb and run: disass 0xffffffff8040d5ea This will print a disassembly of the function at that point. Please post the output of the first screen or so. That may help us identify what the faulting instruction was. If that instruction can't throw that type of exception then we can eliminate a software bug. > pcib0: port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 > pci_link29: BIOS IRQ 12 for -2145774616.1.INTA is invalid > pci_link23: BIOS IRQ 10 for -2145774616.2.INTA is invalid > pci_link24: BIOS IRQ 10 for -2145774616.2.INTB is invalid > pci_link30: BIOS IRQ 10 for -2145774616.2.INTC is invalid This is additionally scary, as it looks like there is bad bugs in the ACPI tables in the BIOS. If you haven't already, please upgrade the BIOS on your system to the latest, and verify that the memory installed in the system is the type specified by the board vendor. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org