From owner-freebsd-current Sat Feb 8 9:35:14 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF74737B401 for ; Sat, 8 Feb 2003 09:35:13 -0800 (PST) Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [62.212.105.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 369DA43F85 for ; Sat, 8 Feb 2003 09:35:13 -0800 (PST) (envelope-from thomas@FreeBSD.ORG) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id EFF492C3D2; Sat, 8 Feb 2003 18:35:11 +0100 (CET) Date: Sat, 8 Feb 2003 18:35:11 +0100 From: Thomas Quinot To: current@freebsd.org Subject: Corrupted crashdump? Message-ID: <20030208173511.GA2625@melusine.cuivre.fr.eu.org> Reply-To: Thomas Quinot Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-message-flag: WARNING! Using Outlook can damage your computer. 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 On a Dell Inspiron 8200 laptop, with ACPI disabled, 5.0-REL rebooted while the system was quiescent. gdb appears to be unable to make sense of the produced crash dump: # gdb -k /usr/obj/usr/src/sys/MALEVIL/kernel.debug vmcore.1 GNU gdb 5.2.1 (FreeBSD) [...] This GDB was configured as "i386-undermydesk-freebsd"... can not access 0xc03a4a2c, invalid address (c03a4a2c) can not access 0xc03a4a2c, invalid address (c03a4a2c) panic messages: --- dmesg: kvm_read: invalid address (c03bf6bc) --- can not access 0xc03d6d40, invalid address (c03d6d40) can not access 0xc03d6d40, invalid address (c03d6d40) #0 0x00000000 in ?? () (kgdb) bt #0 0x00000000 in ?? () (kgdb) Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message