From owner-freebsd-current  Sun Jun 30 23:20:35 2002
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 34DED37B4B1
	for <freebsd-current@freebsd.org>; Sun, 30 Jun 2002 23:20:30 -0700 (PDT)
Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8D44E43E13
	for <freebsd-current@freebsd.org>; Sun, 30 Jun 2002 23:20:26 -0700 (PDT)
	(envelope-from julian@elischer.org)
Received: from InterJet.elischer.org ([12.232.206.8])
          by sccrmhc02.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020701062025.ZOUE6023.sccrmhc02.attbi.com@InterJet.elischer.org>;
          Mon, 1 Jul 2002 06:20:25 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA88795;
	Sun, 30 Jun 2002 23:03:11 -0700 (PDT)
Date: Sun, 30 Jun 2002 23:03:09 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: Bill Huey <billh@gnuppy.monkey.org>
Cc: Michael Nottebrock <michaelnottebrock@gmx.net>,
	freebsd-current@freebsd.org
Subject: Re: Post-KSE desaster
In-Reply-To: <20020701053056.GA1907@gnuppy.monkey.org>
Message-ID: <Pine.BSF.4.21.0206302302200.88707-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

It COULD be related to KSE if I've broken some signal delivery types..

do we have a signal guru in the house that can run a diagnostic on
signals?


On Sun, 30 Jun 2002, Bill Huey wrote:

> On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5
> > (gdb) bt
> > #0  0x281cc918 in _thread_kern_sched_state_unlock () from 
> > /usr/lib/libc_r.so.5
> > #1  0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5
> > #2  0xd0d0d0d0 in ?? ()
> > #3  0x080570b0 in ?? ()
> 
> This is unlikely to be a KSE problem.
> 
> What do the rest of the threads look like ?
> 
> Try "info threads" in gdb and then progressively walking through the thread
> list with "thread N", N being the thread number. I ran into a funny
> create at thread start up time crash and I'm wondering if it could
> be the same thing.
> 
> bill
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message