From owner-freebsd-hackers Tue Jan 18 14:30:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 60F7714F69 for ; Tue, 18 Jan 2000 14:30:54 -0800 (PST) (envelope-from spork@super-g.com) Received: by super-g.com (Postfix, from userid 1000) id A71F910E61; Tue, 18 Jan 2000 17:30:52 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id 8ED2210E60; Tue, 18 Jan 2000 17:30:52 -0500 (EST) Date: Tue, 18 Jan 2000 17:30:52 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Dan Nelson Cc: freebsd-hackers@FreeBSD.ORG, noc@inch.com Subject: Re: high load, nothing happening? (LONG) In-Reply-To: <20000118130250.A97656@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Dan Nelson wrote: > > That's another thing, the box is idle as we've yet to move it into > > production. Out of curiousity, how does one make a machine panic > > manually? > > CTRL-ALT-ESC, and at the prompt type in 'panic'. You'll need DDB > compiled into the kernel, and crashdumps enabled. By now, you should know my next question... What am I looking at? I built a kernel with "config -g" and the debugger option and made it panic while sitting at a load of 3.0... Following the handbook instructions, I see this: (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xc014f085 in panic (fmt=0xc0225638 "from debugger") at ../../kern/kern_shutdown.c:446 #2 0xc0129565 in db_panic (addr=-1071629621, have_addr=0, count=-1, modif=0xc023f7b4 "") at ../../ddb/db_command.c:432 #3 0xc0129505 in db_command (last_cmdp=0xc0242128, cmd_table=0xc0241f88, aux_cmd_tablep=0xc0255d28) at ../../ddb/db_command.c:332 #4 0xc01295ca in db_command_loop () at ../../ddb/db_command.c:454 #5 0xc012ba43 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xc02038a6 in kdb_trap (type=3, code=0, regs=0xc023f8a4) at ../../i386/i386/db_interface.c:157 #7 0xc020e058 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -1071682944, tf_esi = 134, tf_ebp = -1071384344, tf_isp = -1071384372, tf_ebx = 0, tf_edx = -1071414972, tf_ecx = -1072984320, tf_eax = 38, tf_trapno = 3, tf_err = 0, tf_eip = -1071629621, tf_cs = 8, tf_eflags = 582, tf_esp = -1071414988, tf_ss = -1071426239}) at ../../i386/i386/trap.c:548 #8 0xc0203acb in Debugger (msg=0xc0235541 "manual escape to debugger") at ../../i386/i386/db_interface.c:317 #9 0xc01ff03c in scgetc (kbd=0xc026739c, flags=2) at ../../dev/syscons/syscons.c:3947 #10 0xc01f9ff0 in sckbdevent (thiskbd=0xc026739c, event=0, arg=0x0) at ../../dev/syscons/syscons.c:844 where do I go from here? What's this telling me? I assume this procedure was to see what the three "waiting" processes were and what they were doing at the time? Thanks, Charles > -- > Dan Nelson > dnelson@emsphone.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message