From owner-freebsd-current@freebsd.org Sun Nov 13 10:25:01 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 6A991C3DEAC for ; Sun, 13 Nov 2016 10:25:01 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 D6A9E17D4; Sun, 13 Nov 2016 10:25:00 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.walstatt.dynvpn.de ([78.52.171.148]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Ldttv-1cXC1g3BZL-00j054; Sun, 13 Nov 2016 11:24:51 +0100 Date: Sun, 13 Nov 2016 11:24:43 +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: <20161113112443.6c52ed9a@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.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/F0q3OJ6zvoI_/IVMQcR6ErD"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:w35dDPyFfd1G8J2E1KFXnHt4DwFxYwAJMRdV+xFvcc+W4pHtX72 5GgolWelWGbzT/EzpGaqX5j7MmpUNnj0VH/bVva9TDoGBEM0mzsQ8krga8VGl+PgD/DKETF UhL57a3KOWLN1M5AKfAy7+xobtysZ9K25qlwaVNGb5Wa4LDcrmd/3dcrP+1dKenDBo4T7FB +udJX5G9xo0lDmVgqMDVg== X-UI-Out-Filterresults: notjunk:1;V01:K0:gznqu2mljU4=:gP+1o8zJEj9y9mzWJLOuSO jUwizHKTiy7102xTNXMG9rR1ukes3y8QYUNtlSMt/5TYgnvGnXf8STno2JOQl4fYrp9Y/M2sY yXK23bWpjVKhE3w16JpwFiU/ctAFRFNfLLKUBWPBponeOQ78DMZu1XR/eTxP1ckQ0Zq1nvi/9 af++7Axi4VxRRw7O0oKKq0PZGimAaENsW0SDiERnisOTquqCcbu3Jb/Qb4pnGjhASFg/gl92Y NlBrGoGhn/P2QWABhmQ0INbjvvm8A5MyzA5AHqeu8u5DVYp9qmpee3uTySGhWUQZaL2JbLgcP 7VJPaMh/TDn5bGlGqM5yyxBWVFnklbk1Aoz8zmq5fGW//5hUtFH+IlBcdmSAc/SdS9CszFy6V cFKlt+S6hcBgygZgRMWjBSlLPF8ssv1+tWP3NbS9+9qMvvvnJS3VoyehR0OtcZkQQspGcZmwD WoZI4cbIzrONtfQTC1GrkVoROlqXDwWsH0r9vcBFkNEivoniTtNQusfjkxjAbi3is+f4/aTHS iGYZUSKq6KbloIwW2pMY0B6nXSsTsCml1qfgPAquj44SFyNLXa69QwtRbroo9OzTc2HNWtyoG 8VWTjPnCs2ReJYgp3TBLtyAptOzOi6mtpgWIr72QJ9ScrxejJlrE1/35Z7z5A7VOfRmH0xRRF zrI15qb7lRSLTFABgDsbcplInMwGWUCt4MTMKi0BFypdgYbrh37uhD6+Dp+A7nG7UCnZm5twW l54WiD4LHG4FIWH+O8huVV6GeAI/4AZte5cyjo+irS7kXKlKuguazpB4T90= 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 10:25:01 -0000 --Sig_/F0q3OJ6zvoI_/IVMQcR6ErD 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 All right. At this very moment I compile a most recent world and kernel WIT= HOUT the option FLOWTABLE. It takes a lot(!) of time to revert the whole system to t= he working r307233 again (we figured out, that r307234 triggers the crashes so far). The interesting thing to me is that the crash occured on all platforms/Inte= l architectures I use and maintain immediately after r307233 and it lasted for at least r30= 7884 (approx.), that was, when I reverted everything to r307157 (the point from = which I started non-crahsing). Now, I have several relatively modern systems (noreb= ooks with Haswell Mobile CPU, XEON Haswell Workstation and Skylake XEON Servers, AMD = Jaguar based PCEngines APU 2C4) with FLOWTABLE enabled and with most recent CURRENT - wi= thout a crash in days under heavy load (network I/O) and poudriere builds - without issue= s. But everything I have in my hands with IvyBridge (XEON, consumer grade CPUs) an= d lower (one Intel Core2Duo 2-socket server) is crashing with CURRENT beyond r307233. Ma= ybe I oversee the different internal cash architectures and probably optimization problem. Anyway, this just to repeat for the records ;-) I'll give notice after my boxes have been compiled to most recent CURRENT w= ith FLOWTABLES. Thanks and kinf regards, Oliver=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_/F0q3OJ6zvoI_/IVMQcR6ErD Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iJ4EARMKAAYFAlgoP2wACgkQ0udvH8hYWJTJQwH+Omq68R4vE1QirCoHwVQzzFcK CoKwtS0UxaqfA4MEMi8OryTn28vqCBclL+4Y5gQugMusefpYUfNs59rnXL6BdwIA inqstfKiGqgGuMel/7pNOLS3NMdxcUT3xuGjbdSubsJmaV41HSs4x5xPBb5QbVLP N3BQEdc9ImFPaIkxlBckmg== =tNng -----END PGP SIGNATURE----- --Sig_/F0q3OJ6zvoI_/IVMQcR6ErD--