From owner-freebsd-fs@FreeBSD.ORG Tue Feb 19 07:08:36 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CCF6D7D4; Tue, 19 Feb 2013 07:08:36 +0000 (UTC) (envelope-from alfred@ixsystems.com) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) by mx1.freebsd.org (Postfix) with ESMTP id 8E9DF99; Tue, 19 Feb 2013 07:08:36 +0000 (UTC) Received: from localhost (mail.ixsystems.com [10.2.55.1]) by mail.iXsystems.com (Postfix) with ESMTP id DB4BF80FF; Mon, 18 Feb 2013 23:08:35 -0800 (PST) Received: from mail.iXsystems.com ([10.2.55.1]) by localhost (mail.ixsystems.com [10.2.55.1]) (maiad, port 10024) with ESMTP id 90308-08; Mon, 18 Feb 2013 23:08:35 -0800 (PST) Received: from Alfreds-MacBook-Pro-9.local (unknown [10.8.0.26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id 617B280EC; Mon, 18 Feb 2013 23:08:35 -0800 (PST) Message-ID: <512324F2.4060707@ixsystems.com> Date: Mon, 18 Feb 2013 23:08:34 -0800 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Konstantin Belousov , Doug Rabson , Xin Li , fs@freebsd.org Subject: Advisory lock crashes. Content-Type: multipart/mixed; boundary="------------080502030802070307030108" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2013 07:08:36 -0000 This is a multi-part message in MIME format. --------------080502030802070307030108 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello Konstantin & Doug, We're getting a few crashes in what looks to be kern_lockf.c: fault address here is 0x360 which appears to mean that the "sx" owner thread is NULL db> bt Tracing pid 5099 tid 101614 td 0xfffffe005d54e8c0 _sx_xlock_hard() at _sx_xlock_hard+0xb3 lf_advlockasync() at lf_advlockasync+0x5d7 lf_advlock() at lf_advlock+0x47 vop_stdadvlock() at vop_stdadvlock+0xb3 VOP_ADVLOCK_APV() at VOP_ADVLOCK_APV+0x4a closef() at closef+0x352 kern_close() at kern_close+0x172 amd64_syscall() at amd64_syscall+0x58a Xfast_syscall() at Xfast_syscall+0xf7 --- syscall (6, FreeBSD ELF64, sys_close), rip = 0x8011651fc, rsp = 0x7fffffbfdd58, rbp = 0x807c3d6c0 --- (kgdb) list *(_sx_xlock_hard+0xb3) 0xffffffff806242c3 is in _sx_xlock_hard (/usr/home/jpaetzel/9.0.6-RELEASE-p1/FreeBSD/src/sys/kern/kern_sx.c:514). 509 x = sx->sx_lock; 510 if ((sx->lock_object.lo_flags & SX_NOADAPTIVE) == 0) { 511 if ((x & SX_LOCK_SHARED) == 0) { 512 x = SX_OWNER(x); 513 owner = (struct thread *)x; 514 if (TD_IS_RUNNING(owner)) { 515 if (LOCK_LOG_TEST(&sx->lock_object, 0)) 516 CTR3(KTR_LOCK, 517 "%s: spinning on %p held by %p", 518 __func__, sx, owner); Another panic here, which we have less information is attached as an image. We're looking at using some INVARIANTS and WITNESS kernels, but was wondering if y'all had any other suggestions to use please? thank you, -Alfred --------------080502030802070307030108--