From owner-freebsd-current@freebsd.org Sun Nov 13 19:54:50 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 D9FA0C3F5CC for ; Sun, 13 Nov 2016 19:54:50 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 54F6B17F2; Sun, 13 Nov 2016 19:54:49 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from thor.walstatt.dynvpn.de ([78.52.160.227]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M2c1V-1cxymG2kPF-00sQzb; Sun, 13 Nov 2016 20:49:33 +0100 Date: Sun, 13 Nov 2016 20:49:27 +0100 From: "O. Hartmann" To: "Andrey V. Elsukov" Cc: "O. Hartmann" , karels@FreeBSD.org, FreeBSD CURRENT , glebius@FreeBSD.org Subject: Re: was: CURRENT [r308087] still crashing: Backtrace provided Message-ID: <20161113204909.61484c3f@thor.walstatt.dynvpn.de> In-Reply-To: <4f23664d-f3bc-e7c7-e529-92b84a4dcd37@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> <20161113102352.6edbf89d@thor.walstatt.dynvpn.de> <4f23664d-f3bc-e7c7-e529-92b84a4dcd37@FreeBSD.org> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/F6bnzPtBwSU5JYeJgiXHtOS"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:XtREGgeHpojrqC0/qTzNmoaA6Z/0kF+M/nNLjDU/OrSRPJIGL/h XSPcu1FKCHloSqczxXcq63tUUrr5xdzRcvCV2VyyK/T8MFyvdeSxZk4laZ4PZWwPi76W9zr i93Thc+gEft6gRvBdMR/uR/xz7PEkhWuDvZQ3Om4Bbie0PmqqJ9eDrIgdvb/Slri4Ob/Ql3 Ptqsqp2X1u5Ju2AI15WVw== X-UI-Out-Filterresults: notjunk:1;V01:K0:KikB8kzK2Vc=:6sbNuth5PCctHLm3vi/5BN pkqO47I+NO0YAAENTWBcQMHnX+sE/T17BE6neH9bXMHzOxV6EU2Z7wqsxH25xVjke0exYPhyb vDaN0BTyu8jM/1A2ZUn5NU6DHn3x4PHmDLZakun+kJjrXDezmO+47X4I97dPciq8b+6FaPLrl Gze9GGwH/SM1Uoc6uqHQgHm1j0mX5UpIry3xZtQTUQWE/qkbR8j6QMhTTiMWw4SY97VlyfxNF cH7WDRWWvrTfoQXYd/66lbyECjhMjfuWSGYY5lpZILN9wCxfstsdpGVM1+xbBByMWpebqgHCw Ouk7fa9T/Ryqu3q6Ff5Te080I53BLbjIbPTvfccnAQGtLnvHwE8m7dsIn6qHbhw74RuJYdE/e vW8CZ5+Bf47XFv07GZrtz/HQgwJU43WHYRZZkTiIVg9S0Ys26dSZ+UupHjtGcR2E1/B3XQnu8 5ffpjLBuUOVoVtrtoPu2SuFTtBYi6F9nrLSfIMr0ZPiMaaFLC3qNetXc37PJ2D+MvCX6T1VlC FgmNrZuFSh1hbosAATnepn5ev133+2OnkILOHNyaC++oMACStVbiPK2mg1TS0+Kzs8sA3WVZ5 2KaBm+I2gaQcXuHS2RGUJ3o8adqaxO7HpDcVRWEltH4SviUigyzPzH3qA1z0+oI12JEvxtADj QDXIsZvvHXWt5JwmMXqG9XoH3hFUdvRgSYHc1jNnhv9LT06hEw0ThYUx+ZH3EgfKiAgPufOSV 7hM7xSFUbhwmOFxkX2p9l9iqR/T0eRW5upOE1VDDCxQAJZjCUSSdWASC5Zg= X-Mailman-Approved-At: Sun, 13 Nov 2016 22:47:56 +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: Sun, 13 Nov 2016 19:54:50 -0000 --Sig_/F6bnzPtBwSU5JYeJgiXHtOS Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Sun, 13 Nov 2016 12:41:07 +0300 "Andrey V. Elsukov" schrieb: > On 13.11.2016 12:23, O. Hartmann wrote: > >>>>> Great, thank you. I would first like to confirm that r307234 is ind= eed > >>>>> causing the crash - since it appears to be easy to trigger, that sh= ould > >>>>> 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 > >> > >> Do you have option FLOWTABLE in your kernel config? =20 > >=20 > > Would you suggest to disable this feature in the kernel? Or does the fe= ature, by > > accident, influence the debugging ?? =20 >=20 > Hi, >=20 > I never used FLOWTABLE, but as I know, when L2 caching was reintroduced > the kernel with enabled FLOWTABLE has started crashing almost > immediately. glebius@ added workaround in r300854 to prevent the panic. > Then we discussed with him that the change in in_pcb.c should be > reasonable. And he decided to revert the workaround. Now it seems > without r300854 FLOWTABLE isn't usable. >=20 ... it seems that FLOWTABLE is the culprit. Running CURRENT 308616 for hours now ... --=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_/F6bnzPtBwSU5JYeJgiXHtOS Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iJ4EARMKAAYFAlgow8cACgkQ0udvH8hYWJQMvgIAggZDj5koUuOSoF6OzMGs/acD rBdIyj38W19UtacCyjPNRImWscXeTnRRDQvUZ9kByijj4MAUwjPR44hcWmcrDQIA qMwmau8qBlZ7zhPCOy0sM8wMOrVJiC7EaQrPj2Vtz9qB2TphwXfSWMK5RD2tdaZ5 idyPakHNwk2EGtOonXKoZA== =lBEL -----END PGP SIGNATURE----- --Sig_/F6bnzPtBwSU5JYeJgiXHtOS--