Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 May 2003 15:54:22 -0700 (PDT)
From:      Julian Elischer <julian@elischer.org>
To:        Glenn Johnson <glennpj@charter.net>
Cc:        Dan Nelson <dnelson@allantgroup.com>
Subject:   Re: Libthr stable enough for testing
Message-ID:  <Pine.BSF.4.21.0305291553570.47588-100000@InterJet.elischer.org>
In-Reply-To: <20030529223915.GA1025@gforce.johnson.home>

next in thread | previous in thread | raw e-mail | index | archive | help


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
> > <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.  

what about kernel debugger?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0305291553570.47588-100000>