From owner-freebsd-current@FreeBSD.ORG Wed Apr 26 10:31:17 2006 Return-Path: X-Original-To: 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 31C9F16A404; Wed, 26 Apr 2006 10:31:17 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB2A543D6D; Wed, 26 Apr 2006 10:31:08 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k3QAV64g089663; Wed, 26 Apr 2006 04:31:06 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <444F4BE4.2070004@samsco.org> Date: Wed, 26 Apr 2006 04:31:00 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <200604260045.32557.mistry.7@osu.edu> <20060426093356.V93543@fledge.watson.org> In-Reply-To: <20060426093356.V93543@fledge.watson.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: panic: mutex Giant not owned at /usr/src/sys/cam/cam_xpt.c:4837 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2006 10:31:17 -0000 Robert Watson wrote: > > On Wed, 26 Apr 2006, Anish Mistry wrote: > >> #10 0xc04cc002 in panic (fmt=0xc06284f9 "mutex %s not owned at %s:%d") >> at /usr/src/sys/kern/kern_shutdown.c:549 >> #11 0xc04c3b43 in _mtx_assert (m=0xc06286ff, what=-1056878592, >> file=0xc06181c9 "/usr/src/sys/cam/cam_xpt.c", line=4837) >> at /usr/src/sys/kern/kern_mutex.c:768 >> ---Type to continue, or q to quit--- >> #12 0xc0432c65 in xpt_release_devq (path=0x0, count=1, run_queue=1) >> at /usr/src/sys/cam/cam_xpt.c:4837 >> #13 0xc043420e in xpt_action (start_ccb=0xc22f9530) >> at /usr/src/sys/cam/cam_xpt.c:3580 >> #14 0xc051091b in kern_sendit (td=0xc28f7870, s=4, mp=0xcca4bc6c, >> flags=0, >> control=0x0, segflg=3227694719) >> at /usr/src/sys/kern/uipc_syscalls.c:775 >> #15 0xc0511965 in sendit (td=0xc28f7870, s=4, mp=0xcca4bc6c, flags=0) >> at /usr/src/sys/kern/uipc_syscalls.c:715 > > > Something really nasty happened to the stack between frame 14 and frame > 13. The above code path Should Never Happen. The CAM bit is consistent > with itself, and with the panic message, and the socket bit is > consistent with itself. That leaves a question about what happened in > between. Did you try running 'trace' under DDB? If so, can you use > dmesg on the core dump to see if the DDB trace differs from the gdb trace? > > Robert N M Watson There are quite a few missing frames from CAM-land. Scott