Date: Thu, 29 May 2003 17:39:15 -0500 From: Glenn Johnson <glennpj@charter.net> To: Mike Makonnen <mtm@identd.net> Cc: Dan Nelson <dnelson@allantgroup.com> Subject: Re: Libthr stable enough for testing Message-ID: <20030529223915.GA1025@gforce.johnson.home> In-Reply-To: <20030529062003.XSUI13328.out002.verizon.net@kokeb.ambesa.net> 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> <20030529062003.XSUI13328.out002.verizon.net@kokeb.ambesa.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 29, 2003 at 02:20:02AM -0400, Mike Makonnen wrote: > 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. 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. -- Glenn Johnson glennpj@charter.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030529223915.GA1025>