From owner-freebsd-current Sat Apr 13 22:39:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA27282 for current-outgoing; Sat, 13 Apr 1996 22:39:24 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA27272 for ; Sat, 13 Apr 1996 22:39:22 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.4/8.7.4) with SMTP id BAA09948 for ; Sun, 14 Apr 1996 01:39:22 -0400 (EDT) Date: Sun, 14 Apr 1996 01:39:20 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org Subject: System Hang, got core dump...now what? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Tonight I got a system hang (no panic, and not SCSI related) using the newest kernel sources. When I hung, I popped down into DDB, did a panic...and actually got a core dump. Since I got into DDB using CTL-ALT-ESC, and the only panic is what I forced on it...I haven't got a clue what to do with this core, if anything. This one isn't in the docs, to the best of my knowledge, so can someone tell me what I can do with this core (if anything?) to look for the problem? Or does this get dropped under hardware problems too? :( Thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org