From owner-freebsd-current  Sat Feb  8  9:49:45 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 94B5C37B401; Sat,  8 Feb 2003 09:49:43 -0800 (PST)
Received: from nebula.wanadoo.fr (ca-sqy-2-191.abo.wanadoo.fr [80.8.55.191])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id F032343F3F; Sat,  8 Feb 2003 09:49:41 -0800 (PST)
	(envelope-from dak@wanadoo.fr)
Received: from nebula.wanadoo.fr (localhost.wanadoo.fr [127.0.0.1])
	by nebula.wanadoo.fr (8.12.6/8.12.6) with ESMTP id h18HnajO000821;
	Sat, 8 Feb 2003 18:49:36 +0100 (CET)
	(envelope-from dak@nebula.wanadoo.fr)
Received: (from dak@localhost)
	by nebula.wanadoo.fr (8.12.6/8.12.6/Submit) id h18HnZoK000820;
	Sat, 8 Feb 2003 18:49:35 +0100 (CET)
Date: Sat, 8 Feb 2003 18:49:35 +0100
From: Aurelien Nephtali <aurelien.nephtali@wanadoo.fr>
To: Thomas Quinot <thomas@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
Subject: Re: Corrupted crashdump?
Message-ID: <20030208174935.GA754@nebula.wanadoo.fr>
References: <20030208173511.GA2625@melusine.cuivre.fr.eu.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6"
Content-Disposition: inline
In-Reply-To: <20030208173511.GA2625@melusine.cuivre.fr.eu.org>
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


--IJpNTDwzlM2Ie8A6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

I've got the same problem after a panic, the produced core dump was invalid.
I'm on -CURRENT and I think the reason of the core production isn't the sam=
e as
you, but the core dump problem is the same, I'm sure of it.
I'm also on a laptop (Compaq Presarion) but ACPI is enabled.

I have removed the core dump :/

-- Aurelien

On Sat, Feb 08, 2003 at 06:35:11PM +0100, Thomas Quinot wrote:
> 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:
>=20
> # 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)
>=20
> Thomas.
>=20
> --=20
>     Thomas.Quinot@Cuivre.FR.EU.ORG
>=20
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message

--IJpNTDwzlM2Ie8A6
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+RUMvDNsbHbt8ok8RAv0OAJ4/g3cSwpgu2c/t5n3mknFHUGUI3gCfY1Wq
687A7NgtwJdfSr3UNOgUUII=
=Sgq7
-----END PGP SIGNATURE-----

--IJpNTDwzlM2Ie8A6--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message