Date: Sun, 13 Nov 2016 11:24:43 +0100 From: "O. Hartmann" <ohartmann@walstatt.org> To: "Andrey V. Elsukov" <ae@FreeBSD.org> Cc: "O. Hartmann" <ohartmann@walstatt.org>, karels@FreeBSD.org, FreeBSD CURRENT <freebsd-current@freebsd.org>, 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: <alpine.GSO.1.10.1610231515170.5272@multics.mit.edu> <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>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Am Sun, 13 Nov 2016 12:41:07 +0300 "Andrey V. Elsukov" <ae@FreeBSD.org> schrieb: > On 13.11.2016 12:23, O. Hartmann wrote: > >>>>> 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 should > >>>>> be faster. If not, the core will help track down the real problem. > >>>> > >>>> Although I was under the impression the in-kernel-config option > >>>> > >>>> makeoptions DEBUG=-g > >>>> > >>>> would make debugging symbols available, I'm proved wrong. > >> > >> Do you have option FLOWTABLE in your kernel config? > > > > Would you suggest to disable this feature in the kernel? Or does the feature, 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. > All right. At this very moment I compile a most recent world and kernel WITHOUT the option FLOWTABLE. It takes a lot(!) of time to revert the whole system to the 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/Intel architectures I use and maintain immediately after r307233 and it lasted for at least r307884 (approx.), that was, when I reverted everything to r307157 (the point from which I started non-crahsing). Now, I have several relatively modern systems (norebooks 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 - without a crash in days under heavy load (network I/O) and poudriere builds - without issues. But everything I have in my hands with IvyBridge (XEON, consumer grade CPUs) and lower (one Intel Core2Duo 2-socket server) is crashing with CURRENT beyond r307233. Maybe 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 with FLOWTABLES. Thanks and kinf regards, Oliver -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iJ4EARMKAAYFAlgoP2wACgkQ0udvH8hYWJTJQwH+Omq68R4vE1QirCoHwVQzzFcK CoKwtS0UxaqfA4MEMi8OryTn28vqCBclL+4Y5gQugMusefpYUfNs59rnXL6BdwIA inqstfKiGqgGuMel/7pNOLS3NMdxcUT3xuGjbdSubsJmaV41HSs4x5xPBb5QbVLP N3BQEdc9ImFPaIkxlBckmg== =tNng -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161113112443.6c52ed9a>