Date: Thu, 29 May 2003 02:20:02 -0400 From: Mike Makonnen <mtm@identd.net> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-current@freebsd.org Subject: Re: Libthr stable enough for testing Message-ID: <20030529062003.XSUI13328.out002.verizon.net@kokeb.ambesa.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 May 2003 00:35:32 -0500 Dan Nelson <dnelson@allantgroup.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030529062003.XSUI13328.out002.verizon.net>