From owner-freebsd-current@FreeBSD.ORG  Thu Jun  5 05:22:06 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 C432C37B401
	for <current@freebsd.org>; Thu,  5 Jun 2003 05:22:06 -0700 (PDT)
Received: from gravy.homeunix.net (pool-151-197-48-53.phil.east.verizon.net
	[151.197.48.53])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F32ED43FBD
	for <current@freebsd.org>; Thu,  5 Jun 2003 05:22:05 -0700 (PDT)
	(envelope-from bleez@verizon.net)
Received: from gravy.homeunix.net (gravy.homeunix.net [192.168.1.2])
	by gravy.homeunix.net (8.12.9/8.12.9) with ESMTP id h55CM2eC000499;
	Thu, 5 Jun 2003 08:22:02 -0400 (EDT)
	(envelope-from bleez@verizon.net)
Date: Thu, 5 Jun 2003 08:22:02 -0400 (EDT)
From: Bryan Liesner <bleez@verizon.net>
To: Terry Lambert <tlambert2@mindspring.com>
In-Reply-To: <3EDF250C.F79876F7@mindspring.com>
Message-ID: <20030605073853.Y453@gravy.homeunix.net>
References: <20030604021752.Y69975-100000@mail.chesapeake.net>
 <3EDF250C.F79876F7@mindspring.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Jeff Roberson <jroberson@chesapeake.net>
cc: current@freebsd.org
cc: Bryan Liesner <bleez@verizon.net>
Subject: Re: umtx/libthr SMP fixes.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2003 12:22:07 -0000

On Thu, 5 Jun 2003, Terry Lambert wrote:

> As I said: I still think there is a lost serialization here
> that's at the root of the problem.  I can't really dedicate
> the equipment I have here to reproducing the issue at this
> time, or I'd track down the race I think may be happening.
>
> -- Terry

The original panic in kern/52718 is no longer reproduceable for me at
this time.  After Jeff's latest changes, the panic moved from boot time to
panicking when I did an init 6.  I could _not_ reproduce the new panic
if I built a kernel with DDB, but a DDBless kernel would panic every time
after init 6. Needles to say, that makes things really tough to track
down...

After shit-canning the acpi module, it doesn't panic at all.  I'm sure
the race conditions are still lying in wait, but due to a lack of
interest and the incredulous attitude of most on the mailing list, I'm
going to forget about it for the time being.

ACPI has always worked fine on my system, and I'm probably masking
problems by not loading the module.  Since I'm running a desktop
system here, acpi doesn't really buy me anything, so apm is back in my
kernel.

-Bryan