From owner-freebsd-gnome@FreeBSD.ORG Wed Jul 7 19:03:33 2004 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 324A516A4CE; Wed, 7 Jul 2004 19:03:33 +0000 (GMT) Received: from lakermmtao11.cox.net (lakermmtao11.cox.net [68.230.240.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76AC943D39; Wed, 7 Jul 2004 19:03:32 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.localnet.net ([68.11.71.51]) by lakermmtao11.cox.net ESMTP <20040707190331.UVDW25349.lakermmtao11.cox.net@dolphin.localnet.net>; Wed, 7 Jul 2004 15:03:31 -0400 Received: from dolphin.localnet.net (localhost.localnet.net [127.0.0.1]) i67J3VZF029986; Wed, 7 Jul 2004 14:03:31 -0500 (CDT) (envelope-from conrads@dolphin.localnet.net) Received: (from conrads@localhost) by dolphin.localnet.net (8.12.11/8.12.11/Submit) id i67J3VAI029985; Wed, 7 Jul 2004 14:03:31 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 07 Jul 2004 14:03:31 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org cc: freebsd-x11@freebsd.org cc: freebsd-gnome@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Any way to debug a hard lockup? X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2004 19:03:33 -0000 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. 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. Changing from SCHED_ULE to SCHED_4BSD appears to make no difference at all. 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. 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. Thanks. -- Conrad J. Sabatier -- "In Unix veritas"