From owner-freebsd-current@FreeBSD.ORG  Mon Mar 29 13:21:52 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 5749716A4D1; Mon, 29 Mar 2004 13:21:52 -0800 (PST)
Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU
	[128.205.32.2])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E930643D1D; Mon, 29 Mar 2004 13:21:51 -0800 (PST)
	(envelope-from kensmith@cse.Buffalo.EDU)
Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1])
	i2TLLp8o010514;	Mon, 29 Mar 2004 16:21:51 -0500 (EST)
Received: (from kensmith@localhost)
	by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i2TLLpIS010513;
	Mon, 29 Mar 2004 16:21:51 -0500 (EST)
Date: Mon, 29 Mar 2004 16:21:51 -0500
From: Ken Smith <kensmith@cse.Buffalo.EDU>
To: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org
Message-ID: <20040329212151.GA10421@electra.cse.Buffalo.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Subject: -current panic
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, 29 Mar 2004 21:21:52 -0000


Is this one a known issue on alpha or is it something new?  While
someone was using gdb on beast (alpha cluster ref machine) to trace
a program beast crashes with this:

panic: mutex process lock not owned at ../../../kern/kern_mutex.c:277
at line 719 in file ../../../kern/kern_mutex.c
cpuid = 1;
Stack backtrace:
db_print_backtrace() at db_print_backtrace+0x18
backtrace() at backtrace+0x2c
__panic() at __panic+0x210
_mtx_assert() at _mtx_assert+0xec
_mtx_unlock_flags() at _mtx_unlock_flags+0xa4
ptrace_single_step() at ptrace_single_step+0x6c
kern_ptrace() at kern_ptrace+0x3c4
ptrace() at ptrace+0xe8
syscall() at syscall+0x37c
XentSys() at XentSys+0x64
--- syscall (26) ---
--- user mode ---
boot() called on cpu#1

It seems to be reproducible...

-- 
						Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |