From owner-freebsd-current@FreeBSD.ORG Fri Apr 30 23:12:43 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 90CFF106564A for ; Fri, 30 Apr 2010 23:12:43 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nskntmtas04p.mx.bigpond.com (nskntmtas04p.mx.bigpond.com [61.9.168.146]) by mx1.freebsd.org (Postfix) with ESMTP id 28FC38FC08 for ; Fri, 30 Apr 2010 23:12:42 +0000 (UTC) Received: from nskntotgx03p.mx.bigpond.com ([124.188.161.100]) by nskntmtas04p.mx.bigpond.com with ESMTP id <20100430231241.ZQKK25277.nskntmtas04p.mx.bigpond.com@nskntotgx03p.mx.bigpond.com>; Fri, 30 Apr 2010 23:12:41 +0000 Received: from duncan.reilly.home ([124.188.161.100]) by nskntotgx03p.mx.bigpond.com with ESMTP id <20100430231241.YWMA1978.nskntotgx03p.mx.bigpond.com@duncan.reilly.home>; Fri, 30 Apr 2010 23:12:41 +0000 Date: Sat, 1 May 2010 09:12:41 +1000 From: Andrew Reilly To: David Wolfskill , current@freebsd.org Message-ID: <20100430231240.GA28805@duncan.reilly.home> References: <20100430161953.GW96847@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100430161953.GW96847@bunrab.catwhisker.org> User-Agent: Mutt/1.4.2.3i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at nskntotgx03p.mx.bigpond.com from [124.188.161.100] using ID areilly@bigpond.net.au at Fri, 30 Apr 2010 23:12:41 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150203.4BDB63E9.0095,ss=1,fgs=0 X-SIH-MSG-ID: rRgzEtX7TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rVMfpRsM6kxD1MJhiGNGAiaajlTY3Rs9mK Cc: Subject: Re: Panic @r207433: "System call fork returning with the following locks held" 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: Fri, 30 Apr 2010 23:12:43 -0000 Hi all, I'm not sure if it's related (I get my src via csup, so I don't have svn reveision numbers), but I upgraded about 16 hours ago again a few hours after that, and my two-core AMD64 system has been (seemingly) quite unstable. I've had a few boot cycles that have failed and dumped me out into kdb, rebooting through single-user (to check file systems) seems to get me "up", but my logs are completely full of: Calling uiomove() with the following non-sleepable locks held: exclusive sleep mutex vm page queue mutex (vm page queue mutex) r = 0 (0xffffffff80e60a00) locked @ /nb/src/sys/vm/vm_pageout.c:452 exclusive sleep mutex page lock (page lock) r = 0 (0xffffffff80e59e00) locked @ /nb/src/sys/vm/vm_pageout.c:451 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_warn() at witness_warn+0x2c2 uiomove() at uiomove+0x52 ffs_write() at ffs_write+0x32d VOP_WRITE_APV() at VOP_WRITE_APV+0x103 vnode_pager_generic_putpages() at vnode_pager_generic_putpages+0x1c5 vnode_pager_putpages() at vnode_pager_putpages+0x97 vm_pageout_flush() at vm_pageout_flush+0x1ad vm_object_page_collect_flush() at vm_object_page_collect_flush+0x470 vm_object_page_clean() at vm_object_page_clean+0x408 vfs_msync() at vfs_msync+0xef sync_fsync() at sync_fsync+0x12a sync_vnode() at sync_vnode+0x157 sched_sync() at sched_sync+0x1d1 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff803ebbad30, rbp = 0 --- or this slightly different version: uma_zalloc_arg: zone "g_bio" with the following non-sleepable locks held: exclusive sleep mutex vm page queue mutex (vm page queue mutex) r = 0 (0xffffffff80e60a00) locked @ /nb/src/sys/kern/vfs_bio.c:3571 exclusive sleep mutex page lock (page lock) r = 0 (0xffffffff80e5fb80) locked @ /nb/src/sys/vm/vm_pageout.c:451 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_warn() at witness_warn+0x2c2 uma_zalloc_arg() at uma_zalloc_arg+0x335 g_vfs_strategy() at g_vfs_strategy+0x28 ufs_strategy() at ufs_strategy+0x45 bufstrategy() at bufstrategy+0x43 bufwrite() at bufwrite+0x108 cluster_wbuild() at cluster_wbuild+0x1cd cluster_write() at cluster_write+0x2f5 ffs_write() at ffs_write+0x66b VOP_WRITE_APV() at VOP_WRITE_APV+0x103 vnode_pager_generic_putpages() at vnode_pager_generic_putpages+0x1c5 vnode_pager_putpages() at vnode_pager_putpages+0x97 vm_pageout_flush() at vm_pageout_flush+0x1ad vm_object_page_collect_flush() at vm_object_page_collect_flush+0x470 vm_object_page_clean() at vm_object_page_clean+0x19d vfs_msync() at vfs_msync+0xef sync_fsync() at sync_fsync+0x12a sync_vnode() at sync_vnode+0x157 sched_sync() at sched_sync+0x1d1 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff803ebbad30, rbp = 0 --- I'll be doing another csup/rebuild ASAP, in the hope of picking up the fixes mentioned here. Just thought I'd add another "me too" and a bit of data. Cheers, -- Andrew