From owner-freebsd-current@FreeBSD.ORG Sat Aug 11 20:10:09 2007 Return-Path: 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 34C2016A419 for ; Sat, 11 Aug 2007 20:10:09 +0000 (UTC) (envelope-from kirk@ba23.org) Received: from mail-07.primus.ca (mail.tor.primus.ca [216.254.136.21]) by mx1.freebsd.org (Postfix) with ESMTP id E1E5E13C46B for ; Sat, 11 Aug 2007 20:10:08 +0000 (UTC) (envelope-from kirk@ba23.org) Received: from ottawa-hs-64-26-155-235.s-ip.magma.ca ([64.26.155.235]) by mail-07.primus.ca with esmtp (Exim 4.63) (envelope-from ) id 1IJxHk-0001C9-2A for current@freebsd.org; Sat, 11 Aug 2007 16:10:08 -0400 Received: from greyhawk (greyhawk [192.168.1.201]) by ottawa-hs-64-26-155-235.s-ip.magma.ca (8.13.5.20060308/8.13.5) with ESMTP id l7BKA625014608; Sat, 11 Aug 2007 16:10:06 -0400 (EDT) Date: Sat, 11 Aug 2007 16:10:06 -0400 (EDT) From: Kirk Russell To: Kostik Belousov In-Reply-To: <20070809034842.GN2738@deviant.kiev.zoral.com.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: current@freebsd.org Subject: Re: panic: lock "aiomtx" already initialized 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: Sat, 11 Aug 2007 20:10:09 -0000 On Thu, 9 Aug 2007, Kostik Belousov wrote: > > This patch should fix the problem: > > diff --git a/sys/kern/vfs_aio.c b/sys/kern/vfs_aio.c > index 7610da8..47580b6 100644 > --- a/sys/kern/vfs_aio.c > +++ b/sys/kern/vfs_aio.c > @@ -719,6 +719,7 @@ restart: > } > AIO_UNLOCK(ki); > taskqueue_drain(taskqueue_aiod_bio, &ki->kaio_task); > + mtx_destroy(&ki->kaio_mtx); > uma_zfree(kaio_zone, ki); > p->p_aioinfo = NULL; > } > > It seems that you shall use a lot of quickly exit()ing processes all of > them using aio to reliable reproduce the problem. I merged your patch into 7.0-CURRENT-200706. I can no longer reproduce the kern/114216 panic using the dt AIO client script. -- Kirk Russell http://www.ba23.org/