From owner-freebsd-current@FreeBSD.ORG Sat Aug 14 21:54:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7E2D16A4CF for ; Sat, 14 Aug 2004 21:54:24 +0000 (GMT) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DB7043D2D for ; Sat, 14 Aug 2004 21:54:24 +0000 (GMT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id E448E2BD68 for ; Sun, 15 Aug 2004 07:54:21 +1000 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 0952651202; Sun, 15 Aug 2004 07:24:20 +0930 (CST) Date: Sun, 15 Aug 2004 07:24:19 +0930 From: Greg 'groggy' Lehey To: Eirik =?iso-8859-1?Q?=D8verby?= Message-ID: <20040814215419.GF19643@wantadilla.lemis.com> References: <26ECE35D-EDDB-11D8-945B-000D9335BCEC@anduin.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zEb7RLSLB1wmPVHT" Content-Disposition: inline In-Reply-To: <26ECE35D-EDDB-11D8-945B-000D9335BCEC@anduin.net> User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: current@freebsd.org Subject: Re: How to find the cause of a hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Aug 2004 21:54:24 -0000 --zEb7RLSLB1wmPVHT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Saturday, 14 August 2004 at 12:17:31 +0200, Eirik verby wrote: > Hi all, > > I'm currently experiencing frequent (about once per week) hangs of a > server that is about 1500 kilometers away from me. I have a serial > cable on the box, and using minicom on the neighbor box I am now in the > kernel debugger - but I'm at a complete loss as to what to do to figure > out what is, in fact, wrong. > > Calling panic or boot doesn't work - it just stops at "syncing > disks..." and never actually reboots. I suspect something fishy going > on with disk I/O, but I can't be certain of that. > The box responds to ping - until I call panic or boot - but no other > services are working. > > What can I do? I'm now at the db> prompt ... Help :) Well, one possibility would be to debug online. But dumping seems to be broken on recent versions of -CURRENT--see my message on the topic yesterday. Try 'call doadump' instead of 'panic'. Greg -- Note: I discard all HTML mail unseen. Finger grog@FreeBSD.org for PGP public key. See complete headers for address and phone numbers. --zEb7RLSLB1wmPVHT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFBHooLIubykFB6QiMRAgKLAKCyS+PPJTJkZ4Rp9q9PQbdrSjECFgCffG53 rzhh9MLfh7fTrItgLAO4Z4s= =caJD -----END PGP SIGNATURE----- --zEb7RLSLB1wmPVHT--