From owner-freebsd-current@freebsd.org Wed Nov 9 14:19:26 2016 Return-Path: Delivered-To: freebsd-current@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 B44F8C38B48 for ; Wed, 9 Nov 2016 14:19:26 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C87E9AE; Wed, 9 Nov 2016 14:19:25 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from thor.walstatt.dynvpn.de ([92.225.3.98]) by mail.gmx.net (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MMXVC-1cBcrb2HWg-008H8s; Wed, 09 Nov 2016 15:19:17 +0100 Date: Wed, 9 Nov 2016 15:19:07 +0100 From: "O. Hartmann" To: "Andrey V. Elsukov" Cc: Mark Johnston , "O. Hartmann" , FreeBSD CURRENT , glebius@FreeBSD.org Subject: Re: was: CURRENT [r308087] still crashing: Backtrace provided Message-ID: <20161109151907.5be62312@thor.walstatt.dynvpn.de> In-Reply-To: <4b9812b8-ab5b-ff78-01bf-1dc99b1a72d0@FreeBSD.org> References: <20161029163336.46bb24c4.ohartman@zedat.fu-berlin.de> <20161030013345.GC67644@raichu> <20161030082525.6fb6d8a4.ohartman@zedat.fu-berlin.de> <20161030163934.GA49633@raichu> <20161030185500.64e57233.ohartman@zedat.fu-berlin.de> <20161030182509.GA1491@charmander> <20161105184509.28d162f1@thor.walstatt.dynvpn.de> <20161105203748.GD63972@wkstn-mjohnston.west.isilon.com> <20161106111356.39850d7e@thor.walstatt.dynvpn.de> <20161108182829.GA62725@wkstn-mjohnston.west.isilon.com> <4b9812b8-ab5b-ff78-01bf-1dc99b1a72d0@FreeBSD.org> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/pJ2my=I2Cc5NG/uMCW/ygKb"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:xUbRs/WCAL7u96VptPFYozzyHGgp7nytht16O6y7URjxwT+r//n 66B1Vp6FAOSPuv+RRWtUyLjD2gVSUkk+CSNEjnELpPR/MVHwg+D0+a8NfRS9pPI+OwpAr6y anZTTsNvK9a2MXHCjpgN7ckbGVICtGyV1vqcwWid0gIsIALo1A3s2m89HHPUU9EzFGEuSTJ JQzJveQ//ughSxNJ55v+w== X-UI-Out-Filterresults: notjunk:1;V01:K0:ev+BmZ4dYlQ=:ibCF7oMnbgPkkxnPUXhbEu jFHmtiWpJ0XG9WiDhahXB4dlBUMBlpszuLhfWnhQfSFMbKQ5tb6UHZSg1OSjWHdcH02JllQ88 aBfdunhV3/CR1ZdP+TncB3g6xCdYWbs393NhEisA7sRPaN9oms+YF7189QLN/C2UT11ob/kjg Zx1yFI+WeGKfCyy7qKegKmxogMh7rYNmt2Hsu6ICtAONMQmwSZ4yyBhDGRxUpIbpeDTcN/7nV cW0QQbpw7HIhb5EpfzgM/WSOX64kfNXIZyIooJc7oUNf6sAfAup4tFsd6LmV8MpEXnGzxUkvq 4ouf4ybiKLMJR25xGkxiudtWGETZAibV8XbLleMiYNIcaTiQXsTB38TQI9DdSuolXREYjHpxh mlSEUdr3vty9kRplau0l1melcMusBW0IFTk986opVgQ372n07jPcShA9A1v7oz1JcusJCP0Zo BMTEkVnVvQZly9j8diiZkXUWSHd80dOHxgAvCXpFnts4cumm8C3h8JbsKIY9bn1GEiwNKXoKl ztleJzYzpSZfXTjFzSR/SrSwpEzi8QXBJUP7YtZhpSqz+EZSgSwqLmC+FnUu/cIq/7EzT8OB+ aHOjzz28lTG22/nJG+8ZIku+P3siMQ0A6grClcDEA+0rOD4gic3/jVJjmJLO/d+cURC0t1c2M 75UPAIfDr49y0sS2qTFEq26/GN5q4xnVJiLWiKLOPAdcLJshY5joJNtE53ozSshj/Ebs6eClC dK0fX4GALUTgEDY0tj0WwitpBb16c9jk4myd3p3xa+eoiW0a734A5AO3UOE= X-Mailman-Approved-At: Wed, 09 Nov 2016 15:56:24 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 09 Nov 2016 14:19:26 -0000 --Sig_/pJ2my=I2Cc5NG/uMCW/ygKb Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Wed, 9 Nov 2016 17:11:37 +0300 "Andrey V. Elsukov" schrieb: > On 08.11.2016 21:28, Mark Johnston wrote: > > On Sun, Nov 06, 2016 at 11:13:56AM +0100, O. Hartmann wrote: =20 > >>> Great, thank you. I would first like to confirm that r307234 is indeed > >>> causing the crash - since it appears to be easy to trigger, that shou= ld > >>> be faster. If not, the core will help track down the real problem. =20 > >> > >> Although I was under the impression the in-kernel-config option > >> > >> makeoptions DEBUG=3D-g > >> > >> would make debugging symbols available, I'm proved wrong. =20 >=20 > Do you have option FLOWTABLE in your kernel config? >=20 > >> #9 0xffffffff807b44fb in __rw_wlock_hard (c=3D,= =20 > >> tid=3D, file=3D,=20 > >> line=3D) at /usr/src/sys/kern/kern_rwlock.c:8= 30 =20 >=20 > Just my opinion. Setting RT_LLE_CACHE flag in ip_output is wrong. This > flag should be set when ro_lle actually filled with cached data. >=20 Yes, i do have and it is present on all systems. --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/pJ2my=I2Cc5NG/uMCW/ygKb Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iJ4EARMKAAYFAlgjMFsACgkQ0udvH8hYWJTa/gH9ExhSYB1EPcj93hoWlaGK7YDk ova0b6TgTITI3wqSMBchqfHMZj5EiMbSKwser8CRJMzrBQVQfO7S8GV6tOODOgH/ XqXgOPwo/NE2RMjwPjkgb0GZw+kn4hf5MDzlk9KCPjRTNA17/RAHFvbobDRj9Iel +BxZl5F9/IL9oiv6/BRgFQ== =YGSH -----END PGP SIGNATURE----- --Sig_/pJ2my=I2Cc5NG/uMCW/ygKb--