From owner-freebsd-threads@FreeBSD.ORG  Wed Aug 20 23:57:33 2003
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 AFA2416A4BF; Wed, 20 Aug 2003 23:57:33 -0700 (PDT)
Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za
	[196.31.7.201])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B9CC843F93; Wed, 20 Aug 2003 23:57:31 -0700 (PDT)
	(envelope-from sheldonh@starjuice.net)
Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.21)
	id 19pjNx-0001P9-Rg; Thu, 21 Aug 2003 08:57:29 +0200
Date: Thu, 21 Aug 2003 08:57:29 +0200
From: Sheldon Hearn <sheldonh@starjuice.net>
To: deischen@freebsd.org, freebsd-java@freebsd.org,
	threads@freebsd.org
Message-ID: <20030821065729.GC5288@starjuice.net>
Mail-Followup-To: deischen@freebsd.org, freebsd-java@freebsd.org,
	threads@freebsd.org
References: <20030820065729.GL736@starjuice.net>
	<Pine.GSO.4.10.10308200914310.6461-100000@pcnet5.pcnet.com>
	<20030820141128.GG736@starjuice.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030820141128.GG736@starjuice.net>
User-Agent: Mutt/1.5.4i
Sender: Sheldon Hearn <sheldonh@starjuice.net>
Subject: Re: vmark hangs with libthr and libkse
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Aug 2003 06:57:34 -0000

On (2003/08/20 16:11), Sheldon Hearn wrote:

> > Any messages on the console or break-to-debugger info?  Are you using
> > SCHED_4BSD or SCHED_ULE?
> 
> I think it was SCHED_4BSD.  I scribbled the panic down on a piece of
> paper, but can't find it now.  *sigh*

Nope, it's SCHED_ULE.

> > > I just do what my old man told me when I complained that banging my head
> > > against the wall hurt...  "Don't do that, then". :-)
> > 
> > No, please do that and give us some more info.  We claim there
> > are no bugs in libkse, so it's up to you to prove us wrong :-)
> 
> Okay, let me finish my work, sync my disks and give it another whirl
> this afternoon. :-)

I tried with libkse and now I don't even get a useful panic.  Just "page
fault" and disk sync!

I've found my scrap of paper, though.  Here's what I got last week:

Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0x0
code			= supervisor write, page not present
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 4 (g_down)

I don't have DDB in my kernel

I could reinstall a kernel with DDB enabled.  But then what do I do when
I get my "page fault" followed by disk sync?

I realize that the person seeing the problem is usually the person who
should diagnose it, but I'm under hard pressure on a deadline for work.

Perhaps someone else with a bit more free time could try this out?

Ciao,
Sheldon.