From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 21:09:21 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 8FF7416A4CF; Mon, 19 Jul 2004 21:09:21 +0000 (GMT) Received: from lakermmtao11.cox.net (lakermmtao11.cox.net [68.230.240.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id E971843D2F; Mon, 19 Jul 2004 21:09:20 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao11.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040719210918.CVPA6910.lakermmtao11.cox.net@dolphin.local.net>; Mon, 19 Jul 2004 17:09:18 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6JL9J5U012070; Mon, 19 Jul 2004 16:09:19 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6JL9JbB012069; Mon, 19 Jul 2004 16:09:19 -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 In-Reply-To: <20040719202802.8E8C35D08@ptavv.es.net> Date: Mon, 19 Jul 2004 16:09:19 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Kevin Oberman cc: freebsd-current@freebsd.org cc: freebsd-gnome@freebsd.org Subject: [amd64] System lockups still continuing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2004 21:09:21 -0000 On 19-Jul-2004 Kevin Oberman wrote: >> >> 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. Hmm, you may be right. Is there any workaround for this? I've tried both SCHED_ULE and SCHED_4BSD, both producing the same results. What's strange is that this only seems to occur when either running a full-blown GNOME desktop or using some GNOME-related app under another environment. I'm currently working under KDE, just for comparison, and no such problems have occurred, unless I try using, say, Mozilla or Firefox. I'll Cc: this to current and see what they think. -- Conrad J. Sabatier -- "In Unix veritas"