Date: Thu, 31 May 2018 07:04:40 -0400 From: Mark Johnston <markj@FreeBSD.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: "Jonathan T. Looney" <jtl@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: panic: vm_phys_free_pages: page 0x... has unexpected order 0 Message-ID: <20180531110433.GA41152@raichu> In-Reply-To: <783f525c-d1ab-f4cd-9e3e-64d2e70f549b@FreeBSD.org> References: <932853d2-16f9-67c0-fcf8-745bb5e358d4@FreeBSD.org> <cad2a4a7-6f7e-9c9b-eb48-ef645091a929@FreeBSD.org> <CADrOrmvq%2B1D5vJYgPP2zF434a59QbWS0sYuTFuND_gKWL258iw@mail.gmail.com> <783f525c-d1ab-f4cd-9e3e-64d2e70f549b@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 31, 2018 at 10:10:40AM +0300, Andriy Gapon wrote: > On 31/05/2018 05:04, Jonathan T. Looney wrote: > > On Tue, May 29, 2018 at 10:18 AM, Andriy Gapon <avg@freebsd.org > > <mailto:avg@freebsd.org>> wrote: > > > > > > [ping] > > > > On 21/05/2018 11:44, Andriy Gapon wrote: > > > > > > FreeBSD 12.0-CURRENT amd64 r332472 > > > Does this panic ring a bell to anyone? > > > Has it already been fixed? > > > Thank you! > > > > > > Is there any chance that r333703 fixes this problem for you? It fixes a race > > that can manifest itself in other ways. I'm honestly not sure whether it could > > also cause this problem. > > Thank you for the suggestion. > I guess it's worth trying that fix. > I'll report back in a while. r333703 fixes a bug in r332974, while the problem was reported on r332472, so it won't address the crash.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180531110433.GA41152>