Date: Tue, 17 Apr 2018 10:03:37 -0600 From: Dan Allen <danallen46@gmail.com> To: Kyle Evans <kevans@freebsd.org> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: amd64 kernel crash introduced between 20180329 & 20180408 Message-ID: <D799424E-B29F-4E8A-AF4C-120AF8977DDA@gmail.com> In-Reply-To: <CACNAnaGEHmFY2DyndNECkd7%2BmFHeNgF81mKkg5yZBehb935O-A@mail.gmail.com> References: <B8E3D49E-60B1-41FD-A40F-5B0E856483CC@gmail.com> <CACNAnaGV%2B6htEnZaxdVJuqetwd=cbu4xhd1XF2RFZNwAMLG5XA@mail.gmail.com> <4EE33A98-C010-4D79-A502-19D009384B0D@gmail.com> <CACNAnaGEHmFY2DyndNECkd7%2BmFHeNgF81mKkg5yZBehb935O-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 17 Apr 2018, at 9:24 AM, Kyle Evans <kevans@freebsd.org> wrote: >=20 > Can you set vm.pmap.pti=3D0 at the loader prompt and see if > this affects your situation at all, just to rule that out? I redid everything from the start, did set vm.pmap.pti=3D0, and it = behaves exactly the same: kernel panic. Thanks for your help! Do I have any other takers? ;-) Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D799424E-B29F-4E8A-AF4C-120AF8977DDA>