From owner-freebsd-gnome@FreeBSD.ORG Thu Jul 8 19:19:49 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 1577D16A4CE for ; Thu, 8 Jul 2004 19:19:49 +0000 (GMT) Received: from bittern.mail.pas.earthlink.net (bittern.mail.pas.earthlink.net [207.217.120.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F95B43D5A for ; Thu, 8 Jul 2004 19:19:48 +0000 (GMT) (envelope-from mike@inbox.lv) Received: from pool0158.cvx37-bradley.dialup.earthlink.net ([216.244.24.158] helo=ringworm.mojavegreen.com) by bittern.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1BieQs-0002bh-00; Thu, 08 Jul 2004 12:19:47 -0700 Received: by ringworm.mojavegreen.com (Postfix, from userid 1000) id DC2B68630; Thu, 8 Jul 2004 11:44:37 -0700 (PDT) From: "Michael C. Shultz" Organization: Mojave Green Software co. To: conrads@cox.net Date: Thu, 8 Jul 2004 11:44:33 -0700 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407081144.35453.ringworm@inbox.lv> cc: freebsd-gnome@freebsd.org Subject: Re: Any way to debug a hard lockup? X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2004 19:19:49 -0000 On Wednesday 07 July 2004 12: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. > > 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. I had a lock up a few days ago, the first time in ages that has happened. I had just done a complete buildworld the day before. The lockup occured while I was cvsupping. Only, after rebooting and trying again everything worked fine and I have had no problems since. Note: I run 4.10 stable and I was running kde when the lockup occured. Both Gnome and KDE seem to be working fine afterwards. -Mike