From owner-freebsd-current@freebsd.org Sun Nov 13 09:24:09 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 4F300C3B4E1 for ; Sun, 13 Nov 2016 09:24:09 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 B40441D1D; Sun, 13 Nov 2016 09:24:07 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.walstatt.dynvpn.de ([78.52.171.148]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Ma1Mt-1cNGEq1V7f-00LjIL; Sun, 13 Nov 2016 10:23:59 +0100 Date: Sun, 13 Nov 2016 10:23:52 +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: <20161113102352.6edbf89d@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_/3s+uYNQ99jDJJ/peJyhmDv3"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:N6d1oDd8YLKJfNOJyJFMETQYh+3W4bOkdu8XWTGzTyXmQKLs2cu JVGrBFGUY31QrmxkZ3NkzzGjPp5MtA5ZjtDJpF3D75sJpAtAeZL+wr7FZUmWu4uqgKjlYGM fgQ3m9ctdkE94Y9fTCQ7uDY+SngvjtHkS6nm2HNpSWM/WvnBaZU4B2uNhbXF2Qz3M2hGrC+ 4f4t88BYBuo8wFX6KOY/A== X-UI-Out-Filterresults: notjunk:1;V01:K0:acjOsSsZGXE=:cOfGUj8v+x7+YQ6+KznfUD VdrGr+ga8IcQ/jXIradiHWkZDxeSe5T3Kj3sgwceSgNspFkqXbnasZOKZ9JTsXnhpCcFUJd24 A8c3Q/5v+gnP+GtS+u9W0vrKmqTN70Aq/c7CcfTGRsxjx+SB3OGwl3hoYH+QsmcWhXYhAvmsE N93RtwjLUoSeianUzhRlwjN3yiWAZxSozt2e54I21nfoo6n/5YSRNfHgLl9E31JaRq4wnLc3a Lx1PH5cerbORsrThPAax4WQ9eLlvOWg+xZP8JkWsCyA2VwxrXnTjNbCnEfxSbwBVUROniAkTh 6uCbJYaElVPKiRGK2s/IkL3fV5YfwonGm3i0DPaKKrba7j4Jb1b/tKZS96FZ/BAUDXAlW2SsN Ox2FhMvTowT7LPo5GsHiIqWLfazSxd5p70pu5HUJ2QN6wbS1ago3Wb6UXrN83mQRVkfgRY6oc 3WqNNGD5dRFPrMFs/nqf121b5UBFesDfh2uLNkiADTGr2HihZnY4lpzZ4LaQq5UbRqqLeqzfc BXLPWo4B+dqcP91W0rlhWnZaMU4shuC5aE8oPbCwef+5zxKa6ZgrPq0g0b6mg/Q9fo0QOqVU7 ZxotGdqb9WSOSppd2y7IOrTde+ktCjxoledEJJomKQXQUqPhfUixUCjUXefXhmXmusvmpItXN Ul1gNhX8MBoTfLOrGkL8UF8Y0Lsnn7LeDQOiE/nkHrPOqXSs37O6EDuNvVa4lSPHhaymX9Jkb DT/atQWILsFRMcE1j2CshW6IPBuWuMI2UcpFW5ViCYXxRN2Ztzd4YerK6VA= 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: Sun, 13 Nov 2016 09:24:09 -0000 --Sig_/3s+uYNQ99jDJJ/peJyhmDv3 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? Would you suggest to disable this feature in the kernel? Or does the featur= e, by accident, influence the debugging ?? >=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 --=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_/3s+uYNQ99jDJJ/peJyhmDv3 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iJ4EARMKAAYFAlgoMSgACgkQ0udvH8hYWJRVZwIAnQIrZTrGEZ4DzYq3CLcyphUx L9zCN4zpig6qgrypEpPqFWq7M1VtLeEjPLE7omNaSZR6Om/DKP7ySu5JvFGL2QH/ eMi1tzDwq3U+WS8oDWktWYJ357hoc2d4HwTqmaqXVEutS5MrqgaqSUahOLOMPpwx egrw3m1mlG/zEWqXcx5LZA== =Q047 -----END PGP SIGNATURE----- --Sig_/3s+uYNQ99jDJJ/peJyhmDv3--