From owner-freebsd-current@FreeBSD.ORG Thu May 29 17:31:37 2003 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 4282137B401 for ; Thu, 29 May 2003 17:31:37 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id B641D43F3F for ; Thu, 29 May 2003 17:31:36 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by attbi.com (rwcrmhc52) with ESMTP id <2003053000313605200r3rrme>; Fri, 30 May 2003 00:31:36 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA49056; Thu, 29 May 2003 17:31:34 -0700 (PDT) Date: Thu, 29 May 2003 17:31:32 -0700 (PDT) From: Julian Elischer To: Glenn Johnson In-Reply-To: <20030529230020.GA24085@gforce.johnson.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: Dan Nelson Subject: Re: Libthr stable enough for testing 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: Fri, 30 May 2003 00:31:37 -0000 On Thu, 29 May 2003, Glenn Johnson wrote: > On Thu, May 29, 2003 at 03:54:22PM -0700, Julian Elischer wrote: > > > > On Thu, 29 May 2003, Glenn Johnson wrote: > > > > > On Thu, May 29, 2003 at 02:20:02AM -0400, Mike Makonnen wrote: > > > > > > > On Thu, 29 May 2003 00:35:32 -0500 Dan Nelson > > > > wrote: > > > > > > > > > > > > > The real problem is in the kernel, though. A userland non-root > > > > > process should not be able to hard lock the system. One of the > > > > > threads people will probably have to get an SMP machine to be > > > > > able to debug it. > > > > > > > > > > > > Upon first reading it I had assumed he meant gnome locked up. Can > > > > you confirm this Glenn? Is the machine itself locked solid (no > > > > ping, no ssh, not vtys, etc)? However, even if that is the case a > > > > bug in the kernel does not preclude a bug in libthr. > > > > > > The machine locks up solid. I can not do anything with it except > > > hit the reset button. I mentioned gnome because gnome will trigger > > > the lock up. I would imagine I would see the same thing with kde > > > however. > > > > what about kernel debugger? > > I do not have the debugger enabled on the SMP box. I can set that up > but probably not until next week. Will the debugger work if the machine > locks up? that depends.. when it locked up, did it still respond to pings? >