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 same 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: > > # 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. > > -- > [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message
msg52003/pgp00000.pgp
Description: PGP signature
