From owner-freebsd-stable@FreeBSD.ORG Tue Jan 26 18:38:01 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3549B106566C; Tue, 26 Jan 2010 18:38:01 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 9A24A8FC26; Tue, 26 Jan 2010 18:38:00 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id o0QIbug7042165; Tue, 26 Jan 2010 19:37:56 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id o0QIbuRV042164; Tue, 26 Jan 2010 19:37:56 +0100 (CET) (envelope-from marius) Date: Tue, 26 Jan 2010 19:37:56 +0100 From: Marius Strobl To: Peter Jeremy Message-ID: <20100126183756.GA40779@alchemy.franken.de> References: <20100126073336.GA1955@server.vk2pj.dyndns.org> <201001260946.44977.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201001260946.44977.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: rmacklem@freebsd.org, dfr@freebsd.org, freebsd-stable@freebsd.org, John Baldwin Subject: Re: uma_zalloc_arg complaining about non-sleepable locks X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2010 18:38:01 -0000 On Tue, Jan 26, 2010 at 09:46:44AM -0500, John Baldwin wrote: > On Tuesday 26 January 2010 2:33:37 am Peter Jeremy wrote: > > I have just upgraded to 8-STABLE/amd64 from about 18 hours ago and am > > now getting regular (the following pair of messages about every > > minute) compaints as follows: > > > > kernel: uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks held: > > kernel: exclusive sleep mutex sp_lock (sp_lock) r = 0 (0xffffff000460bb00) locked @ /usr/src/sys/rpc/svc.c:1098 > > kernel: KDB: stack backtrace: > > kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > kernel: _witness_debugger() at _witness_debugger+0x2c > > kernel: witness_warn() at witness_warn+0x2c2 > > kernel: uma_zalloc_arg() at uma_zalloc_arg+0x29d > > kernel: nfs_realign() at nfs_realign+0x5f > > kernel: fha_assign() at fha_assign+0x2d8 > > kernel: svc_run_internal() at svc_run_internal+0x1ee > > kernel: svc_thread_start() at svc_thread_start+0xb > > kernel: fork_exit() at fork_exit+0x112 > > kernel: fork_trampoline() at fork_trampoline+0xe > > kernel: --- trap 0xc, rip = 0x80069e04c, rsp = 0x7fffffffe6d8, rbp = 0x5 --- > > kernel: uma_zalloc_arg: zone "mbuf" with the following non-sleepable locks held: > > kernel: exclusive sleep mutex sp_lock (sp_lock) r = 0 (0xffffff000460bb00) locked @ /usr/src/sys/rpc/svc.c:1098 > > kernel: KDB: stack backtrace: > > kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > kernel: _witness_debugger() at _witness_debugger+0x2c > > kernel: witness_warn() at witness_warn+0x2c2 > > kernel: uma_zalloc_arg() at uma_zalloc_arg+0x29d > > kernel: nfs_realign() at nfs_realign+0x5f > > kernel: fha_assign() at fha_assign+0x2d8 > > kernel: svc_run_internal() at svc_run_internal+0x1ee > > kernel: svc_thread_start() at svc_thread_start+0xb > > kernel: fork_exit() at fork_exit+0x112 > > kernel: fork_trampoline() at fork_trampoline+0xe > > kernel: --- trap 0xc, rip = 0x80069e04c, rsp = 0x7fffffffe6d8, rbp = 0x5 --- > > > > It looks like NFS is missing some lock/unlock pairs. Has anyone else > > seen this? And does anyone have a fix? > > I suspect this was caused by the recent alignment fixes to NFS. I've cc'd > Marius. > Could you please give the following patch a try? http://people.freebsd.org/~marius/fha_extract_info_realign2.diff It would also be great if one of the NFS gurus could have a look at the whole issue. Unfortunately, I hadn't received a reply regarding the original patch. Marius