From owner-freebsd-current@FreeBSD.ORG Wed Jul 7 19:18:36 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 0765E16A4CE; Wed, 7 Jul 2004 19:18:36 +0000 (GMT) Received: from creme-brulee.marcuscom.com (rrcs-midsouth-24-172-16-118.biz.rr.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B1FB43D46; Wed, 7 Jul 2004 19:18:35 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.4] (vpn-client-4.marcuscom.com [10.2.1.4]) i67JFuWp056488; Wed, 7 Jul 2004 15:15:56 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: conrads@cox.net In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-kCvbOx8tq2z5wQ42exsi" Organization: MarcusCom, Inc. Message-Id: <1089227975.854.57.camel@gyros> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 07 Jul 2004 15:19:35 -0400 X-Spam-Status: No, hits=-2.3 required=5.0 tests=BAYES_00,SUSPICIOUS_RECIPS autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on creme-brulee.marcuscom.com cc: freebsd-x11@freebsd.org cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org cc: freebsd-gnome@freebsd.org Subject: Re: Any way to debug a hard lockup? 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: Wed, 07 Jul 2004 19:18:36 -0000 --=-kCvbOx8tq2z5wQ42exsi Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-07-07 at 15:03, Conrad J. Sabatier wrote: > For the last few days, my amd64 box (Athlon 64 3200+, 5.2-CURRENT, > updating just about daily lately) has been locking up hard fairly > often, and I have no clue as to why. >=20 > Checking the logs after rebooting reveals nothing at all out of the > ordinary. The box just "seizes up" and that's that. Only thing to do > is a power-down and restart. >=20 > Changing from SCHED_ULE to SCHED_4BSD appears to make no difference at > all. >=20 > My other box, an older (32-bit) Athlon, has been rock stable. I've > been keeping both machines updated simultaneously to exactly the same > revisions, using as near-identical system settings as possible also, > the main difference being I'm running X.org/GNOME on the amd64 box and > no X on the i386 box. >=20 > Any suggestions? Instinct tells me it may be a problem with some of > the ports I'm running (X.org/GNOME, hence the Cc:s), but how to verify? > Sure, I could run without X a while and see how it goes, but that still > won't help to isolate the problem, if it is, in fact, port-related. You'll need to use a serial console and DDB to debug these problems.=20 See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-set= up.html on setting that up. Once the machine breaks into the debugger, you= 'll be able to get a stack trace. Joe >=20 > Thanks. --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-kCvbOx8tq2z5wQ42exsi Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA7EzHb2iPiv4Uz4cRAkh9AJ955YzXu8nDbmbS851GzBv1ShOfkQCfYAUc lyfa4l812nBMFBSqVwCYcvk= =4hh7 -----END PGP SIGNATURE----- --=-kCvbOx8tq2z5wQ42exsi--