NetBSD Problem Report #51215
From www@NetBSD.org Sat Jun 4 09:47:53 2016
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
by mollari.NetBSD.org (Postfix) with ESMTPS id A14427A214
for <gnats-bugs@gnats.NetBSD.org>; Sat, 4 Jun 2016 09:47:53 +0000 (UTC)
Message-Id: <20160604094752.79C647AAB9@mollari.NetBSD.org>
Date: Sat, 4 Jun 2016 09:47:52 +0000 (UTC)
From: 6bone@6bone.informatik.uni-leipzig.de
Reply-To: 6bone@6bone.informatik.uni-leipzig.de
To: gnats-bugs@NetBSD.org
Subject: nfs client kernel crash
X-Send-Pr-Version: www-1.0
>Number: 51215
>Category: kern
>Synopsis: nfs client kernel crash
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Jun 04 09:50:00 +0000 2016
>Last-Modified: Sat Jun 18 17:10:01 +0000 2016
>Originator: Uwe Toenjes
>Release: nfs client kernel crash
>Organization:
University of Leipzig
>Environment:
NetBSD 7.0_STABLE
>Description:
in rare cases, under high nfs load the kernel crashes
0xffffffff8068630f in cpu_reboot (howto=howto@entry=260,
bootstr=bootstr@entry=0x0) at
/usr/src/sys/arch/amd64/amd64/machdep.c:671
671 dumpsys();
(gdb) bt
#0 0xffffffff8068630f in cpu_reboot (howto=howto@entry=260,
bootstr=bootstr@entry=0x0) at
/usr/src/sys/arch/amd64/amd64/machdep.c:671
#1 0xffffffff808cbce4 in vpanic (fmt=fmt@entry=0xffffffff80dd3d3d "trap",
ap=ap@entry=0xfffffe8157920d18) at /usr/src/sys/kern/subr_prf.c:340
#2 0xffffffff808cbd9f in panic (fmt=fmt@entry=0xffffffff80dd3d3d "trap")
at /usr/src/sys/kern/subr_prf.c:256
#3 0xffffffff8091b001 in trap (frame=0xfffffe8157920e20)
at /usr/src/sys/arch/amd64/amd64/trap.c:298
#4 0xffffffff80100fde in alltraps ()
#5 0xffffffff8070605c in nfs_timer (arg=<optimized out>)
at /usr/src/sys/nfs/nfs_socket.c:770
#6 0xffffffff80622022 in callout_softclock (v=<optimized out>)
at /usr/src/sys/kern/kern_timeout.c:736
#7 0xffffffff80616bb8 in softint_execute (l=<optimized out>, s=2,
si=0xffff80035866a0c0) at /usr/src/sys/kern/kern_softint.c:589
#8 softint_dispatch (pinned=<optimized out>, s=2)
at /usr/src/sys/kern/kern_softint.c:871
#9 0xffffffff8011412f in Xsoftintr ()
>How-To-Repeat:
You cannot reproduce the crash. The crash occurs randomly and only at high nfs load.
>Fix:
>Audit-Trail:
From: Joerg Sonnenberger <joerg@bec.de>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/51215: nfs client kernel crash
Date: Sat, 4 Jun 2016 13:34:20 +0200
On Sat, Jun 04, 2016 at 09:50:00AM +0000, 6bone@6bone.informatik.uni-leipzig.de wrote:
> >Description:
> in rare cases, under high nfs load the kernel crashes
>
> 0xffffffff8068630f in cpu_reboot (howto=howto@entry=260,
> bootstr=bootstr@entry=0x0) at
> /usr/src/sys/arch/amd64/amd64/machdep.c:671
> 671 dumpsys();
> (gdb) bt
> #0 0xffffffff8068630f in cpu_reboot (howto=howto@entry=260,
> bootstr=bootstr@entry=0x0) at
> /usr/src/sys/arch/amd64/amd64/machdep.c:671
> #1 0xffffffff808cbce4 in vpanic (fmt=fmt@entry=0xffffffff80dd3d3d "trap",
> ap=ap@entry=0xfffffe8157920d18) at /usr/src/sys/kern/subr_prf.c:340
> #2 0xffffffff808cbd9f in panic (fmt=fmt@entry=0xffffffff80dd3d3d "trap")
> at /usr/src/sys/kern/subr_prf.c:256
> #3 0xffffffff8091b001 in trap (frame=0xfffffe8157920e20)
> at /usr/src/sys/arch/amd64/amd64/trap.c:298
> #4 0xffffffff80100fde in alltraps ()
> #5 0xffffffff8070605c in nfs_timer (arg=<optimized out>)
> at /usr/src/sys/nfs/nfs_socket.c:770
> #6 0xffffffff80622022 in callout_softclock (v=<optimized out>)
> at /usr/src/sys/kern/kern_timeout.c:736
> #7 0xffffffff80616bb8 in softint_execute (l=<optimized out>, s=2,
> si=0xffff80035866a0c0) at /usr/src/sys/kern/kern_softint.c:589
> #8 softint_dispatch (pinned=<optimized out>, s=2)
> at /usr/src/sys/kern/kern_softint.c:871
> #9 0xffffffff8011412f in Xsoftintr ()
For reference purposes, please include "indent src/sys/nfs/*.c", so that
the line numbers and specific revisions can be matched.
Joerg
From: christos@zoulas.com (Christos Zoulas)
To: gnats-bugs@NetBSD.org, kern-bug-people@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: kern/51215: nfs client kernel crash
Date: Sat, 4 Jun 2016 10:13:28 -0400
On Jun 4, 9:50am, 6bone@6bone.informatik.uni-leipzig.de (6bone@6bone.informatik.uni-leipzig.de) wrote:
-- Subject: kern/51215: nfs client kernel crash
This is related to 40491 and 50432
christos
From: 6bone@6bone.informatik.uni-leipzig.de
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/51215: nfs client kernel crash
Date: Sat, 4 Jun 2016 20:55:16 +0200 (CEST)
On Sat, 4 Jun 2016, Joerg Sonnenberger wrote:
> For reference purposes, please include "indent src/sys/nfs/*.c", so that
> the line numbers and specific revisions can be matched.
src/sys/nfs/krpc_subr.c:
$NetBSD: krpc_subr.c,v 1.37.38.2 2015/04/21 04:55:15 snj Exp $
$NetBSD: krpc_subr.c,v 1.37.38.2 2015/04/21 04:55:15 snj Exp $
src/sys/nfs/nfs_bio.c:
$NetBSD: nfs_bio.c,v 1.189.4.1 2015/11/04 17:32:00 riz Exp $
$NetBSD: nfs_bio.c,v 1.189.4.1 2015/11/04 17:32:00 riz Exp $
src/sys/nfs/nfs_boot.c:
$NetBSD: nfs_boot.c,v 1.81.4.1 2015/04/06 01:37:29 snj Exp $
$NetBSD: nfs_boot.c,v 1.81.4.1 2015/04/06 01:37:29 snj Exp $
src/sys/nfs/nfs_bootdhcp.c:
$NetBSD: nfs_bootdhcp.c,v 1.52.34.1 2015/04/06 01:37:29 snj Exp $
$NetBSD: nfs_bootdhcp.c,v 1.52.34.1 2015/04/06 01:37:29 snj Exp $
src/sys/nfs/nfs_bootparam.c:
$NetBSD: nfs_bootparam.c,v 1.38 2013/09/12 18:00:18 drochner Exp $
$NetBSD: nfs_bootparam.c,v 1.38 2013/09/12 18:00:18 drochner Exp $
src/sys/nfs/nfs_bootstatic.c:
$NetBSD: nfs_bootstatic.c,v 1.8 2009/10/23 02:32:34 snj Exp $
$NetBSD: nfs_bootstatic.c,v 1.8 2009/10/23 02:32:34 snj Exp $
src/sys/nfs/nfs_clntsocket.c:
$NetBSD: nfs_clntsocket.c,v 1.1.40.1 2015/11/04 17:32:00 riz Exp $
$NetBSD: nfs_clntsocket.c,v 1.1.40.1 2015/11/04 17:32:00 riz Exp $
src/sys/nfs/nfs_clntsubs.c:
$NetBSD: nfs_clntsubs.c,v 1.2 2011/06/12 03:35:59 rmind Exp $
$NetBSD: nfs_clntsubs.c,v 1.2 2011/06/12 03:35:59 rmind Exp $
src/sys/nfs/nfs_export.c:
$NetBSD: nfs_export.c,v 1.58 2013/12/14 16:19:28 christos Exp $
$NetBSD: nfs_export.c,v 1.58 2013/12/14 16:19:28 christos Exp $
src/sys/nfs/nfs_iod.c:
$NetBSD: nfs_iod.c,v 1.6.4.1 2015/11/04 17:32:00 riz Exp $
$NetBSD: nfs_iod.c,v 1.6.4.1 2015/11/04 17:32:00 riz Exp $
src/sys/nfs/nfs_kq.c:
$NetBSD: nfs_kq.c,v 1.25 2011/10/24 11:43:30 hannken Exp $
$NetBSD: nfs_kq.c,v 1.25 2011/10/24 11:43:30 hannken Exp $
src/sys/nfs/nfs_node.c:
$NetBSD: nfs_node.c,v 1.118 2014/05/30 08:47:45 hannken Exp $
$NetBSD: nfs_node.c,v 1.118 2014/05/30 08:47:45 hannken Exp $
src/sys/nfs/nfs_serv.c:
$NetBSD: nfs_serv.c,v 1.170 2014/01/23 10:13:57 hannken Exp $
$NetBSD: nfs_serv.c,v 1.170 2014/01/23 10:13:57 hannken Exp $
src/sys/nfs/nfs_socket.c:
$NetBSD: nfs_socket.c,v 1.192.2.1 2015/11/04 17:32:00 riz Exp $
$NetBSD: nfs_socket.c,v 1.192.2.1 2015/11/04 17:32:00 riz Exp $
src/sys/nfs/nfs_srvcache.c:
$NetBSD: nfs_srvcache.c,v 1.45 2009/03/15 17:20:10 cegger Exp $
$NetBSD: nfs_srvcache.c,v 1.45 2009/03/15 17:20:10 cegger Exp $
src/sys/nfs/nfs_srvsocket.c:
$NetBSD: nfs_srvsocket.c,v 1.4 2009/09/03 20:59:12 tls Exp $
$NetBSD: nfs_srvsocket.c,v 1.4 2009/09/03 20:59:12 tls Exp $
src/sys/nfs/nfs_srvsubs.c:
$NetBSD: nfs_srvsubs.c,v 1.14 2012/11/05 19:06:27 dholland Exp $
$NetBSD: nfs_srvsubs.c,v 1.14 2012/11/05 19:06:27 dholland Exp $
src/sys/nfs/nfs_subs.c:
$NetBSD: nfs_subs.c,v 1.227 2014/08/10 16:44:36 tls Exp $
$NetBSD: nfs_subs.c,v 1.227 2014/08/10 16:44:36 tls Exp $
src/sys/nfs/nfs_syscalls.c:
$NetBSD: nfs_syscalls.c,v 1.154.4.1 2015/11/04 17:46:21 riz Exp $
$NetBSD: nfs_syscalls.c,v 1.154.4.1 2015/11/04 17:46:21 riz Exp $
src/sys/nfs/nfs_vfsops.c:
$NetBSD: nfs_vfsops.c,v 1.229.2.2 2015/11/08 01:14:20 riz Exp $
$NetBSD: nfs_vfsops.c,v 1.229.2.2 2015/11/08 01:14:20 riz Exp $
src/sys/nfs/nfs_vnops.c:
$NetBSD: nfs_vnops.c,v 1.306.2.2 2016/02/06 20:52:36 snj Exp $
$NetBSD: nfs_vnops.c,v 1.306.2.2 2016/02/06 20:52:36 snj Exp $
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/51215: nfs client kernel crash
Date: Fri, 17 Jun 2016 15:51:11 +0000
On Sat, Jun 04, 2016 at 02:15:01PM +0000, Christos Zoulas wrote:
> 50432
Curiously, I've never seen that even once running -current... maybe it
only affects -7 and was caused by a mismatched pullup?
--
David A. Holland
dholland@netbsd.org
From: 6bone@6bone.informatik.uni-leipzig.de
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/51215: nfs client kernel crash
Date: Sat, 18 Jun 2016 19:08:11 +0200 (CEST)
On Fri, 17 Jun 2016, David Holland wrote:
> Date: Fri, 17 Jun 2016 15:55:00 +0000 (UTC)
> From: David Holland <dholland-bugs@netbsd.org>
> Reply-To: gnats-bugs@NetBSD.org
> To: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
> netbsd-bugs@netbsd.org, 6bone@6bone.informatik.uni-leipzig.de
> Subject: Re: kern/51215: nfs client kernel crash
>
> The following reply was made to PR kern/51215; it has been noted by GNATS.
>
> From: David Holland <dholland-bugs@netbsd.org>
> To: gnats-bugs@NetBSD.org
> Cc:
> Subject: Re: kern/51215: nfs client kernel crash
> Date: Fri, 17 Jun 2016 15:51:11 +0000
>
> On Sat, Jun 04, 2016 at 02:15:01PM +0000, Christos Zoulas wrote:
> > 50432
>
> Curiously, I've never seen that even once running -current... maybe it
> only affects -7 and was caused by a mismatched pullup?
I see the "nfs server not responding" message also with netbsd-6. But
netbsd-6 never crashed. In my environment the nfs server is always a
netapp. The message occurs only at high nfs load.
Regards
Uwe
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2014
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home