From owner-freebsd-current@FreeBSD.ORG  Wed Jun  2 17:57:22 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B08A4106566B
	for <current@freebsd.org>; Wed,  2 Jun 2010 17:57:22 +0000 (UTC)
	(envelope-from bruce@cran.org.uk)
Received: from muon.cran.org.uk (muon.cran.org.uk [204.109.60.94])
	by mx1.freebsd.org (Postfix) with ESMTP id 964B78FC15
	for <current@freebsd.org>; Wed,  2 Jun 2010 17:57:22 +0000 (UTC)
Received: from unknown (87-194-158-129.bethere.co.uk [87.194.158.129])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	by muon.cran.org.uk (Postfix) with ESMTPSA id 20E266504
	for <current@freebsd.org>; Wed,  2 Jun 2010 17:57:23 +0000 (UTC)
Date: Wed, 2 Jun 2010 18:57:14 +0100
From: Bruce Cran <bruce@cran.org.uk>
To: current@freebsd.org
Message-ID: <20100602185714.000069be@unknown>
X-Mailer: Claws Mail 3.7.4cvs1 (GTK+ 2.16.0; i586-pc-mingw32msvc)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: 
Subject: ata panic: "mtx_lock of destroyed mutex"
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Wed, 02 Jun 2010 17:57:22 -0000

I've been setting up an amd64 VirtualBox machine with the latest
9-CURRENT and got the following panic when booting it (another machine
updated and booting at the same time didn't panic):

ata1: WARNING - READ_TOC read data overrun 18>12
panic: mtx_lock of destroyed mutex @ /usr/src/sys/kern/kern_sema.c:79
cpuid = 0

with the following stack trace:

kdb_enter
panic
_mtx_lock_flags
_sema_post
ata_completed
taskqueue_run
intr_event_execute_handlers
ithread_loop
fork_exit
fork_trampoline

-- 
Bruce Cran