From owner-freebsd-current@freebsd.org Sun Nov 13 09:44:03 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 CF44CC3BC79 for ; Sun, 13 Nov 2016 09:44:03 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:1900:2254:206a::19:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx2.freebsd.org", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A899FCC9; Sun, 13 Nov 2016 09:44:03 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx2.freebsd.org (Postfix) with ESMTP id D83086B2DF; Sun, 13 Nov 2016 09:44:01 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: was: CURRENT [r308087] still crashing: Backtrace provided To: "O. Hartmann" 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> Cc: karels@FreeBSD.org, FreeBSD CURRENT , glebius@FreeBSD.org From: "Andrey V. Elsukov" Message-ID: <4f23664d-f3bc-e7c7-e529-92b84a4dcd37@FreeBSD.org> Date: Sun, 13 Nov 2016 12:41:07 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161113102352.6edbf89d@thor.walstatt.dynvpn.de> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="i03BHGmWWDnD7SVcejkfpEIl7KB19oHcf" 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:44:03 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --i03BHGmWWDnD7SVcejkfpEIl7KB19oHcf Content-Type: multipart/mixed; boundary="dmAouBhlpr26j1grPeuxI9tuNBFkKksEq"; protected-headers="v1" From: "Andrey V. Elsukov" To: "O. Hartmann" Cc: karels@FreeBSD.org, FreeBSD CURRENT , glebius@FreeBSD.org Message-ID: <4f23664d-f3bc-e7c7-e529-92b84a4dcd37@FreeBSD.org> Subject: Re: was: CURRENT [r308087] still crashing: Backtrace provided 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> In-Reply-To: <20161113102352.6edbf89d@thor.walstatt.dynvpn.de> --dmAouBhlpr26j1grPeuxI9tuNBFkKksEq Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 > Would you suggest to disable this feature in the kernel? Or does the fe= ature, by > accident, influence the debugging ?? Hi, 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 WBR, Andrey V. Elsukov --dmAouBhlpr26j1grPeuxI9tuNBFkKksEq-- --i03BHGmWWDnD7SVcejkfpEIl7KB19oHcf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEsBAEBCAAWBQJYKDUzDxxhZUBmcmVlYnNkLm9yZwAKCRABxeoEEMihejP1CAC1 TjMD9cFf0FXuTgpRrtPlFpNPak09DS2ShmSyvPyIOHsGDdlvcE2v7FDWvP8rHSJV Ik3xWJmkJ0Z2lxaTYC4jP+W+6wkkndAyXHgMsXg05gBUkeDB96C3JS2bdBFc6Kju 3aeywb4cajdZUW/PbVG5nWe5wVjOm09jwgZXmRcV3NrSNaHqFShJL2GiXY+QA5G3 71h6vLgD+i88E9H65arObBXfDKeGY2UgbJDnYujKv6pQEL7+dJFNFBTekCXn135q aXM7JCruSYBpZwAP96WJS89aJLbGFJPYa1tOZ8cCwLDR560scMokQxQdcSxhSWaL vxxweN2JCsUwjIWZRO+a =nAxR -----END PGP SIGNATURE----- --i03BHGmWWDnD7SVcejkfpEIl7KB19oHcf--