From owner-freebsd-threads@FreeBSD.ORG Sat Aug 16 16:29:14 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B4A837B401 for ; Sat, 16 Aug 2003 16:29:14 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CDC843F3F for ; Sat, 16 Aug 2003 16:29:13 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h7GNTCuN022392; Sat, 16 Aug 2003 19:29:12 -0400 (EDT) Date: Sat, 16 Aug 2003 19:29:12 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Marcel Moolenaar In-Reply-To: <20030816161332.GA39823@dhcp42.pn.xcllnt.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org Subject: Re: KSE/ia64: NULL thread pointer in _thr_sig_add() X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Aug 2003 23:29:14 -0000 On Sat, 16 Aug 2003, Marcel Moolenaar wrote: > On Sat, Aug 16, 2003 at 06:13:36AM -0400, Daniel Eischen wrote: > > On Mon, 11 Aug 2003, Marcel Moolenaar wrote: > > > > > On Mon, Aug 11, 2003 at 02:34:08PM +0800, David Xu wrote: > > > > > > > > I have a patch trying to fix the problem, I haven't tested it, > > > > http://people.freebsd.org/~davidxu/kse/thr_kern.c.diff > > > > I think some calls of kse_set_curthread is bogus, Dan might need to > > > > rethink it. > > > > > > I think this is it. I now get sig 11, but it looks like a faulty > > > use of random(). It appears random() is not thread safe and this > > > particular test program uses random. > > > > > > I'll continue to run tests, but so far it looks like the patch is > > > fixing KSE/ia64. > > > > So as of now, where do we stand for KSE on ia64? Do ACE tests > > pass? > > Good question. I don't know. I wanted to try it at home in case I > ran into other kernel panics, but I cannot compile. > > There's at least a problem with the mutex_d test, so I suspect that > we still have some lingering issues. This does not look to be > related to thread pointers. I don't know to what extend it will affect > ACE. One question. When you call (the syscall) setcontext() from _ia64_break_setcontext(), do you ignore the signal mask (uc.uc_sigmask)? -- Dan Eischen