From owner-freebsd-current Thu Aug 23 14: 9:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (dsl092-013-169.sfo1.dsl.speakeasy.net [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 3675737B40A for ; Thu, 23 Aug 2001 14:09:19 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f7NL9I317806 for current@freebsd.org; Thu, 23 Aug 2001 14:09:19 -0700 (PDT) (envelope-from obrien) Date: Thu, 23 Aug 2001 14:09:18 -0700 From: "David O'Brien" To: current@freebsd.org Subject: how to debug the crashdump of my locked up system? Message-ID: <20010823140918.A17795@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I finally got a crashdump by C-A-Esc and doing `call dumpsys'. In the past I have done a C-A-Esc and `panic' and had the writing to dumpdev hang. Not sure why it worked this time. Anyway, what should I do with the crashdump to figure out what is going on with my system disk hanging? Also is `ps' still supose to work on crashdumps? # ps -M vmcore.0 -N kernel.0.debug ps: Undefined error: 0 -- -- David (obrien@FreeBSD.org) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message