From owner-freebsd-current@freebsd.org Thu Nov 2 09:04:48 2017 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 066FCE5492D for ; Thu, 2 Nov 2017 09:04:48 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D718C7348F for ; Thu, 2 Nov 2017 09:04:47 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: by mailman.ysv.freebsd.org (Postfix) id D6688E5492C; Thu, 2 Nov 2017 09:04:47 +0000 (UTC) Delivered-To: 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 D6094E5492B for ; Thu, 2 Nov 2017 09:04:47 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A0CF73484; Thu, 2 Nov 2017 09:04:46 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MS5Dm-1dgzSG1Tvm-00TDk5; Thu, 02 Nov 2017 10:04:38 +0100 Date: Thu, 2 Nov 2017 10:04:37 +0100 From: "O. Hartmann" To: Andriy Gapon 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: References: <20171031123215.GP1387@albert.catwhisker.org> <20171031130241.GZ1387@albert.catwhisker.org> <20171101083257.1c2b55aa@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:mrmYtnbJEKnYT6jC3eO0+gFofqaO95CbVTEo26VPCq+VPexdOqk zmpasYZHJPu9wwYG17Tei2fVugJDKHvAInu7VAGAJ4obtW/+PsLtSfX+krMDOlObbADy01f 08FSu0rExpKs3CD/nVOU3cRYXaaW3dLugHWpAjbcKRer6mRNAxBRKH3/bKAC8UDhxM4ktn3 IOoI8eZeTLrBnQ+iAMkLQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:bFqNLRPlnKM=:foQ6PHZfgN8Tbb2LRHxyVd Eczfl2pFOqO9sMnYR9q5/sDrd4JcWa9K1WtLj6DsxHxwpZ8euOLkUDdJc1x++2yNQgFNTXMoG Fc6txRP1DSWHkfMi8iMOB0ImeedIKShu5tZOFm/KQp6JAV5Ii57xgypD1QVJcUtYx2xnZQv+5 1dPQUUw7qV462XRgs8b19m6e2Kitm6XcoKzdt5yDSuglTQlgwl6L1O15E511QD7aYGAPVCp5u 8qegEMwO2Y7pt2drosskT1CXFbVv2+SFWAFYcHz6/p93Z0FtcsiE7def7jF3I2U56YFaiwJCC lxZeBt/k+b7LMYU52oZDCtRWd9Vpu/i2h/H3BIbrb9DVlHFqB7WvAu2IgR0mnEFf6Z/YYq6O/ zwsWcj2VZPqjhWcjflXEsPRTpt4W5EAt6bENdsKJMP9ZVjVIEZIqIRR7U7uRMJhdcIFXBvy+5 qJJAwmVHmcsbdo1MhYsk6MIdHsMbTwR88a11fejKbBDjUGzRcisD115breeql39uL5Y5qfCK5 V5rTMAXvXckOn4Gflf9s3IFNMXXA6gp3Rtq67Dwkw3wB0/Tn7125N5GOQo0Y3zheTtt3BpKFV zhbISFG4VIVT8CI4/qbcUgLtbWxI9ozIEXAoM7ro3umvsi6Jr7mP91i7qWquv8v5UV8+fZlcc XD5m7Jrqtf9Kt36/K8SyVI88MYmhTdboK6dYwlmzIZ5d3HB2VU82o6Gr8V5PCBMejznt/dU6c iCi5v98fm+V1eS7Xv/IuhMSnNMIa6R+TIl2uZOMTsTdvWO8PyQOorx5Ub+rkZPlsNhetYdyM7 HPqXVwp4thGsLh5xARj9PPBgXoRcxJi7P9DnYzhLvJ1O5fGzRw= X-Mailman-Approved-At: Thu, 02 Nov 2017 10:49:12 +0000 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: Thu, 02 Nov 2017 09:04:48 -0000 On Wed, 1 Nov 2017 10:12:59 +0200 Andriy Gapon 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