Re: Crash dumps on current
On Tue, Jul 09, 2002 at 10:37:20AM -0700, Matthew Dillon wrote:
> Welcome to -current. I haven't been able to get crash dumps to
> work for a while :-(
>
> I usually set up a serial console between two machines and run
> gdb live to debug the kernel.
Crash dumps have been working oh so well for me recently. Seems like the
occasional panic resulting in a reboot will not leave a proper dump, but
here's one I got today:
blarf:/home/crash#gdb52 -k kernel.3 vmcore.3
GNU gdb 5.2 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-portbld-freebsd5.0"...
IdlePTD at phsyical address 0x0054f000
initial pcb at physical address 0x0043f8a0
panicstr: from debugger
panic messages:
---
panic: Most recently used by none
panic: from debugger
Uptime: 58m32s
Dumping 127 MB
ata0: resetting devices .. done
16 32 48 64 80 96 112
---
#0 doadump () at ../../../kern/kern_shutdown.c:213
213 dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:213
#1 0xc021ba80 in boot (howto=260) at ../../../kern/kern_shutdown.c:345
#2 0xc021bc24 in poweroff_wait (junk=0xc0376288, howto=-928630028)
at ../../../kern/kern_shutdown.c:489
#3 0xc016babd in db_panic () at ../../../ddb/db_command.c:449
#4 0xc016ba5f in db_command (last_cmdp=0xc03d3680, cmd_table=0xc0376288,
aux_cmd_tablep=0xc03ca120, aux_cmd_tablep_end=0x104)
at ../../../ddb/db_command.c:345
#5 0xc016bb28 in db_command_loop () at ../../../ddb/db_command.c:471
#6 0xc016de51 in db_trap (type=3, code=0) at ../../../ddb/db_trap.c:72
#7 0xc0339291 in kdb_trap (type=3, code=0, regs=0xc8a63b94)
at ../../../i386/i386/db_interface.c:161
#8 0xc03465c9 in trap (frame=
{tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = -1061660800, tf_esi = 256, t
f_ebp = -928629800, tf_isp = -928629824, tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_
eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1070361369, tf_cs = 8, tf_eflags
= 662, tf_esp = -1069828632, tf_ss = -928629780})
at ../../../i386/i386/trap.c:604
#9 0xc03394e7 in Debugger (msg=0xc039733c "panic") at cpufunc.h:68
#10 0xc021bc0f in panic (fmt=0xc03bb5e8 "Most recently used by %s\n")
at ../../../kern/kern_shutdown.c:476
#11 0xc0316702 in mtrash_ctor (mem=0xc1ebf000, size=0, arg=0x0)
at ../../../vm/uma_dbg.c:135
#12 0xc031676c in mtrash_fini (mem=0xc1ebf000, size=8192)
at ../../../vm/uma_dbg.c:186
#13 0xc0314a58 in zone_drain (zone=0xc0b85780) at ../../../vm/uma_core.c:646
#14 0xc031536e in zone_foreach (zfunc=0xc03147c2 )
at ../../../vm/uma_core.c:1167
#15 0xc031626a in uma_reclaim () at ../../../vm/uma_core.c:1980
#16 0xc031242a in vm_pageout_scan (pass=0) at ../../../vm/vm_pageout.c:652
#17 0xc031310a in vm_pageout () at ../../../vm/vm_pageout.c:1429
#18 0xc020ca80 in fork_exit (callout=0xc0312ee0 , arg=0x0,
frame=0xc8a63d48) at ../../../kern/kern_fork.c:863
(kgdb)
- alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Crash dumps on current
: :OK. How the * do I get a *!@#$@$#% crash dump on current? I :did a dumpon to enable the dumping, which appeared to work. I then :did a savecore after the system came back up (but before any swapping :happened) and that seemed to work. I then tried to use gdb to read :the core dump and got the following: Welcome to -current. I haven't been able to get crash dumps to work for a while :-( I usually set up a serial console between two machines and run gdb live to debug the kernel. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Crash dumps on current
On 09-Jul-2002 M. Warner Losh wrote: > OK. How the * do I get a *!@#$@$#% crash dump on current? I > did a dumpon to enable the dumping, which appeared to work. I then > did a savecore after the system came back up (but before any swapping > happened) and that seemed to work. I then tried to use gdb to read > the core dump and got the following: > > 9:58am hammer:/dell/crash[52]> sudo gdb -k *.2 > GNU gdb 4.18 (FreeBSD) > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > > "/dell/crash/info.2": not in executable format: File format not recognized > > > kgdb could not open the exec-file, please check the name you used ! > (kgdb) quit > sudo gdb -k ~/FreeBSD/src/sys/i386/compile/GENERIC/kernel.debug vmcore.2 > GNU gdb 4.18 (FreeBSD) > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read called at > /dell/imp/FreeBSD/src/contrib/gdb/gdb/dwarf2read.c line 3049 in dwarf2_read_section > > > Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. > > > kernel symbol `cpuhead' not found. > (kgdb) quit > > Needless to say, I'm somewhat frustrated as to what to do. Ideas? If you still want to use gdb 4.18, you have to build your kernel with DEBUG=-gstabs+ or some such. Either that or use gdb52 from ports or from a more recent system with your kernel and dump. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Crash dumps on current
On Tue, Jul 09, 2002 at 11:20:52AM -0500, Dan Nelson wrote: > In the last episode (Jul 09), M. Warner Losh said: > > OK. How the * do I get a *!@#$@$#% crash dump on current? I > > did a dumpon to enable the dumping, which appeared to work. I then > > did a savecore after the system came back up (but before any swapping > > happened) and that seemed to work. I then tried to use gdb to read > > the core dump and got the following: > > > > sudo gdb -k ~/FreeBSD/src/sys/i386/compile/GENERIC/kernel.debug vmcore.2 > > GNU gdb 4.18 (FreeBSD) > > Copyright 1998 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read called at >/dell/imp/FreeBSD/src/contrib/gdb/gdb/dwarf2read.c line 3049 in dwarf2_read_section > > > > > > Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. > > Don't you need to use gdb52 -k now, since the new GCC was turned on? gdb52 was imported into -current a week or two ago. It does look like he does either need to use the port or upgrade -current. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Crash dumps on current
In the last episode (Jul 09), M. Warner Losh said: > OK. How the * do I get a *!@#$@$#% crash dump on current? I > did a dumpon to enable the dumping, which appeared to work. I then > did a savecore after the system came back up (but before any swapping > happened) and that seemed to work. I then tried to use gdb to read > the core dump and got the following: > > sudo gdb -k ~/FreeBSD/src/sys/i386/compile/GENERIC/kernel.debug vmcore.2 > GNU gdb 4.18 (FreeBSD) > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read called at >/dell/imp/FreeBSD/src/contrib/gdb/gdb/dwarf2read.c line 3049 in dwarf2_read_section > > > Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. Don't you need to use gdb52 -k now, since the new GCC was turned on? -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Crash dumps on current
OK. How the * do I get a *!@#$@$#% crash dump on current? I did a dumpon to enable the dumping, which appeared to work. I then did a savecore after the system came back up (but before any swapping happened) and that seemed to work. I then tried to use gdb to read the core dump and got the following: 9:58am hammer:/dell/crash[52]> sudo gdb -k *.2 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... "/dell/crash/info.2": not in executable format: File format not recognized kgdb could not open the exec-file, please check the name you used ! (kgdb) quit sudo gdb -k ~/FreeBSD/src/sys/i386/compile/GENERIC/kernel.debug vmcore.2 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read called at /dell/imp/FreeBSD/src/contrib/gdb/gdb/dwarf2read.c line 3049 in dwarf2_read_section Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. kernel symbol `cpuhead' not found. (kgdb) quit Needless to say, I'm somewhat frustrated as to what to do. Ideas? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
