From owner-freebsd-current@FreeBSD.ORG Sun May 2 01:11:07 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C100E106567C for ; Sun, 2 May 2010 01:11:07 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id A0A6A8FC0C for ; Sun, 2 May 2010 01:11:07 +0000 (UTC) Received: by pwi9 with SMTP id 9so816514pwi.13 for ; Sat, 01 May 2010 18:10:57 -0700 (PDT) Received: by 10.115.20.18 with SMTP id x18mr1618304wai.50.1272762657538; Sat, 01 May 2010 18:10:57 -0700 (PDT) Received: from [10.0.1.198] (udp022762uds.hawaiiantel.net [72.234.79.107]) by mx.google.com with ESMTPS id r20sm16545231wam.17.2010.05.01.18.10.56 (version=SSLv3 cipher=RC4-MD5); Sat, 01 May 2010 18:10:57 -0700 (PDT) Date: Sat, 1 May 2010 15:10:57 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: Bruce Cran In-Reply-To: <20100501222130.GA25044@muon.cran.org.uk> Message-ID: References: <20100501222130.GA25044@muon.cran.org.uk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: SUJ update 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: Sun, 02 May 2010 01:11:07 -0000 On Sat, 1 May 2010, Bruce Cran wrote: > On Thu, Apr 29, 2010 at 06:37:00PM -1000, Jeff Roberson wrote: > >> I fixed a few SUJ bugs. If those of you who reported one of the >> following bugs could re-test I would greatly appreciate it. >> > > I've started seeing a panic "Sleeping thread owns a non-sleepable lock", > though it seems to be occurring both with and without journaling. The > back trace when journaling is disabled is: Can you tell me what the lock is? This may be related to recent vm work which went in at the same time. > > sched_switch > mi_switch > sleepq_wait > _sleep > bwait > bufwait > bufwrite > ffs_balloc_ufs2 > ffs_write > VOP_WRITE_APV > vnode_pager_generic_putpages > VOP_PUTPAGES > vnode_pager_putpages > vm_pageout_flush > vm_object_page_collect_flush > vm_object_page_clean > vfs_msync > sync_fsync > VOP_FSYNC_APV > sync_vnode > sched_sync > fork_exit > fork_trampoline > > I've also noticed that since disabling journaling a full fsck seems to > be occurring on boot; background fsck seems to have been disabled. When you disable journaling it also disables soft-updates. You need to re-enable it. I could decouple this. It's hard to say which is the POLA. Thanks, Jeff > > -- > Bruce Cran >