From owner-freebsd-gnome@FreeBSD.ORG Mon Jul 19 20:28:03 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 840A316A4CE for ; Mon, 19 Jul 2004 20:28:03 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67B0B43D48 for ; Mon, 19 Jul 2004 20:28:03 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Mon, 19 Jul 2004 13:28:02 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 8E8C35D08; Mon, 19 Jul 2004 13:28:02 -0700 (PDT) To: conrads@cox.net In-reply-to: Your message of "Mon, 19 Jul 2004 15:16:20 CDT." Date: Mon, 19 Jul 2004 13:28:02 -0700 From: "Kevin Oberman" Message-Id: <20040719202802.8E8C35D08@ptavv.es.net> cc: freebsd-gnome@freebsd.org Subject: Re: It appears I was mistaken (re: lockups) 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: Mon, 19 Jul 2004 20:28:03 -0000 > Date: Mon, 19 Jul 2004 15:16:20 -0500 (CDT) > From: "Conrad J. Sabatier" > Sender: owner-freebsd-gnome@freebsd.org > > > On 18-Jul-2004 Conrad J. Sabatier wrote: > > I had posted several weeks ago about constant hard lockups of my > > amd64 box. At first, I attributed the problem to GNOME, then to my > > kernel config, but now it appears to me that the problem really lies > > with Mozilla/Firefox. > > Well, another theory bites the dust. I tried running GNOME yesterday, > never touched Mozilla or Firefox, and the system locked up while doing > some file management chores in Nautilus. > > It must be something low-level in GNOME, some shared library, probably, > but I have yet to track it down. I have lost track of the full thread and this mail list is not tracked by google :-(, so this may have been ruled out. Are you sure that it's not the preemption problem that is biting you? This applies to CURRENT systems only, so may not be applicable to what you are seeing, the symptoms are a match. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634