Date: Thu, 2 Nov 2017 10:04:37 +0100 From: "O. Hartmann" <o.hartmann@walstatt.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64) Message-ID: <20171102100437.4ddbef44@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <bc0aa4ea-849d-b76f-5324-1a4d6c0738fb@FreeBSD.org> References: <20171031123215.GP1387@albert.catwhisker.org> <cad48069-8f32-0a2a-1814-93a7f4aaa650@FreeBSD.org> <20171031130241.GZ1387@albert.catwhisker.org> <20171101083257.1c2b55aa@freyja.zeit4.iv.bundesimmobilien.de> <bc0aa4ea-849d-b76f-5324-1a4d6c0738fb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Nov 2017 10:12:59 +0200 Andriy Gapon <avg@FreeBSD.org> wrote: > On 01/11/2017 09:33, O. Hartmann wrote: > > I have the same (or similar) probleme here on two boxes now, maybe more to > > come as I start updating CURRENT cyclic. > > > > Reverting r325227 solves to problem for now. > > Oliver, > > David and I have been working on this and a fix is coming soon. > Sorry for the trouble and thanks for the report. > Everything is all right, the exclusion of r325227 helped over the problem and I do not see any problems after the recent patch. Thanks for the fast repair. No trouble induced, so far (old kernel ran perfectly). Kind regards, Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171102100437.4ddbef44>