From owner-freebsd-current@FreeBSD.ORG  Mon Oct 18 19:36:01 2004
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 6C37216A4CE; Mon, 18 Oct 2004 19:36:01 +0000 (GMT)
Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 00CEA43D49; Mon, 18 Oct 2004 19:36:01 +0000 (GMT)
	(envelope-from nate@root.org)
Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net
	[67.119.74.222])
	by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i9IJZwFp032523
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 18 Oct 2004 12:35:59 -0700
Message-ID: <41741B1D.5010800@root.org>
Date: Mon, 18 Oct 2004 12:35:57 -0700
From: Nate Lawson <nate@root.org>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Anish Mistry <mistry.7@osu.edu>
References: <48908.1096571186@critter.freebsd.dk>
	<200410181514.05861.mistry.7@osu.edu>
In-Reply-To: <200410181514.05861.mistry.7@osu.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: Poul-Henning Kamp <phk@phk.freebsd.dk>
cc: freebsd-current@freebsd.org
Subject: Re: RELENG_5 panic: mtx_lock() with ACPI
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: Mon, 18 Oct 2004 19:36:01 -0000

Anish Mistry wrote:
> On Thursday 30 September 2004 03:06 pm, Poul-Henning Kamp wrote:
> 
>>In message <415C4F5A.2080701@root.org>, Nate Lawson writes:
>>
>>>I assume phk would be handling this since it's in the tty code.  If not,
>>>please let us know so one of us can address this before the release.
>>>
>>>
>>>>>>struct tty *
>>>>>>ttymalloc(struct tty *tp)
>>>>>>{
>>>>>>       static int once;
>>>>>>
>>>>>>       if (!once) {
>>>>>>               mtx_init(&tty_list_mutex, "ttylist", NULL, MTX_DEF);
>>>>>>               once++;
>>>>>>       }
>>>>>>
>>>>>>This code is not MP safe as multiple processors could attempt to call
>>>>>>mtx_init() twice.
>>
>>We have no calls to ttymalloc() which are not protected by Giant,
>>so this theory doesn't explain the problem.
> 
> Any progress, I'd hate to have to disable ACPI for the release.  Is there any 
> way I could provide more info?

I'll try to look at it on the bus tonight.  See if you can narrow down 
if one ACPI component is contributing to this, i.e. 
debug.acpi.disabled="cpu" or whatever (see acpi.4 for the full list). 
The sysctl run from the rc scripts to get entropy is what triggers the 
panic.

I have no idea how acpi can affect the tty mutex.

-- 
Nate