From owner-freebsd-net@freebsd.org Fri Sep 18 13:56:50 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55BA59CE418 for ; Fri, 18 Sep 2015 13:56:50 +0000 (UTC) (envelope-from julien@jch.io) Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E075917E5 for ; Fri, 18 Sep 2015 13:56:49 +0000 (UTC) (envelope-from julien@jch.io) Received: by wicfx3 with SMTP id fx3so65485259wic.1 for ; Fri, 18 Sep 2015 06:56:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type; bh=mUzGopqvslYoMXy5dJJ09p4yLg1NfgNHUaa/W/9jAeg=; b=arD0kX25h+Q1ea00UAfdmQHa4zg7mTpCdD0AsCIE27ku5ddeM3g0wXSqbub9eQsyKE EEk9I6DVqcOlI9DSqg166G/eZawiZ5FpFVx0MtnVlFqO5K1tNGurQpwFWs2tWXd/boO8 fNqmSGHqt5rjTGyzVeaRxBfg6RSj9CXKc6MJgikobMHxDXsbCkPnnlaJhGHgX8hAnJv6 b7UOcBwo/nXInkYYzvxTuloVhpCzAHYvpk3v6lzqOpCOLZtsYhf8nKEVDfvTItENkIFk iJMPTqf8SOBBOpBioUxO+7IIeAO/lSH8ykTYxD9KnULnWfZkep1QA9595JNLH5tM4zcg aJoA== X-Gm-Message-State: ALoCoQkkaXycIAnLPu0/O819ACKVYcHEQFPMYb/A7KyYfCUiCJrsV4rWt+ScMONJPRu8tIpIhJm8 X-Received: by 10.194.92.68 with SMTP id ck4mr8036020wjb.141.1442584601841; Fri, 18 Sep 2015 06:56:41 -0700 (PDT) Received: from del2sochahar-l1.vcorp.ad.vrsn.com ([217.30.88.7]) by smtp.googlemail.com with ESMTPSA id j7sm9040905wjz.11.2015.09.18.06.56.40 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Sep 2015 06:56:41 -0700 (PDT) Subject: Re: Kernel panics in tcp_twclose To: Palle Girgensohn , freebsd-net@freebsd.org References: <26B0FF93-8AE3-4514-BDA1-B966230AAB65@FreeBSD.org> From: Julien Charbon X-Enigmail-Draft-Status: N1110 Message-ID: <55FC1809.3070903@freebsd.org> Date: Fri, 18 Sep 2015 15:56:25 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <26B0FF93-8AE3-4514-BDA1-B966230AAB65@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="FWnD3UtvklttSg1bb2eNanqOQTxu4rfff" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 13:56:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --FWnD3UtvklttSg1bb2eNanqOQTxu4rfff Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Palle, On 18/09/15 11:12, Palle Girgensohn wrote: > We see daily panics on our production systems (web server, apache > running MPM event, openjdk8. Kernel with VIMAGE. Jails using netgraph > interfaces [not epair]). >=20 > The problem started after the summer. Normal port upgrades seems to > be the only difference. The problem occurs with 10.2-p2 kernel as > well as 10.1-p4 and 10.1-p15. >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203175 >=20 > Any ideas? Thanks for you detailed report. I am not aware of any tcp_twclose() related issues (without VIMAGE) since FreeBSD 10.0 (does not mean there are none). Few interesting facts (at least for me): - Your crash happens when unlocking a inp exclusive lock with INP_WUNLOC= K() - Something is already wrong before calling turnstile_broadcast() as it is called with ts =3D NULL: turnstile_broadcast (ts=3D0x0, queue=3D1) at /usr/src/sys/kern/subr_turnstile.c:838 __rw_wunlock_hard () at /usr/src/sys/kern/kern_rwlock.c:988 tcp_twclose () at /usr/src/sys/netinet/tcp_timewait.c:540 tcp_tw_2msl_scan () at /usr/src/sys/netinet/tcp_timewait.c:748 tcp_slowtimo () at /usr/src/sys/netinet/tcp_timer.c:198 I won't go to far here as I am not expert enough in VIMAGE, but one question anyway: - Can you correlate this kernel panic to a particular event? Like for example a VIMAGE/VNET jail destruction. I will test that on my side on a 10.2 machine. -- Julien --FWnD3UtvklttSg1bb2eNanqOQTxu4rfff Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJV/BgXAAoJEKVlQ5Je6dhxf8IH/iko4HYhG6QLHsbJ+5HcSJVk xJz/PWyaLtsFsvOQVszXWU8MtsC1HkWyvv+5yJdMbEDPSj0sxG+DJ0jVqliNSidu 6opF68HjoqOzo+piBDyvxzQOXtDnofjfEDNRdXtRh49LL9QcvxmQHViWvSHJg8iw 82qdfdCrbUr7dJWknjR6EAvRjrFbZe37neFXkSfRKJqrS7sOohV4DXBa5NqPcamw ANJOne7YgYW4T1iSUZP7QQLNtJYQp5PtLt4e7rLNFg1TcTS9l9iGlEdlWtUU+jEd Dgd8jwyrQ3LajHE9CclSNmU29cGi9nYZy5ifH3UpKh/QyhuiqFc5brx73TMBcxY= =QeCn -----END PGP SIGNATURE----- --FWnD3UtvklttSg1bb2eNanqOQTxu4rfff--