From owner-freebsd-current@FreeBSD.ORG Wed May 28 23:20:05 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 2DDF437B401 for ; Wed, 28 May 2003 23:20:05 -0700 (PDT) Received: from out002.verizon.net (out002pub.verizon.net [206.46.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4767943FAF for ; Wed, 28 May 2003 23:20:04 -0700 (PDT) (envelope-from mtm@identd.net) Received: from kokeb.ambesa.net ([138.88.45.55]) by out002.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030529062003.XSUI13328.out002.verizon.net@kokeb.ambesa.net>; Thu, 29 May 2003 01:20:03 -0500 Date: Thu, 29 May 2003 02:20:02 -0400 From: Mike Makonnen To: Dan Nelson In-Reply-To: <20030529053532.GD91945@dan.emsphone.com> References: <20030526225111.HVVN25800.out006.verizon.net@kokeb.ambesa.net> <20030529025735.GA2882@gforce.johnson.home> <20030529040251.ZKLF3199.pop016.verizon.net@kokeb.ambesa.net> <20030529053532.GD91945@dan.emsphone.com> X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [138.88.45.55] at Thu, 29 May 2003 01:20:03 -0500 Message-Id: <20030529062003.XSUI13328.out002.verizon.net@kokeb.ambesa.net> cc: glennpj@charter.net cc: freebsd-current@freebsd.org 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: Thu, 29 May 2003 06:20:05 -0000 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. Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc mtm@identd.net | D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 mtm@FreeBSD.Org| FreeBSD - The Power To Serve