From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 6 17:11:14 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1973F59 for ; Wed, 6 Aug 2014 17:11:14 +0000 (UTC) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) by mx1.freebsd.org (Postfix) with ESMTP id C35E628F5 for ; Wed, 6 Aug 2014 17:11:14 +0000 (UTC) Received: from marvin.beer.town (c-24-125-214-90.hsd1.va.comcast.net [24.125.214.90]) by smtp.vangyzen.net (Postfix) with ESMTPSA id DCBDD56444; Wed, 6 Aug 2014 12:11:13 -0500 (CDT) Message-ID: <53E261B1.5010108@vangyzen.net> Date: Wed, 06 Aug 2014 13:11:13 -0400 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Matt Fleming Subject: Re: Sanity Check: Bogus(?) General Protection Fault References: <53E237B6.4040703@vangyzen.net> <20140806144833.GE15082@console-pimps.org> <53E24FF0.7030305@vangyzen.net> <20140806161932.GG15082@console-pimps.org> In-Reply-To: <20140806161932.GG15082@console-pimps.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Aug 2014 17:11:15 -0000 On 08/06/2014 12:19, Matt Fleming wrote: > On Wed, 06 Aug, at 11:55:28AM, Eric van Gyzen wrote: >> Thanks, Matt. That has always been my understanding (and I just found >> the docs to confirm). I doubted myself because the problem is now even >> more bizarre. The mov before the faulting instruction apparently didn't >> complete. %r11 is still an old value, not 0x....f7a8. > > The mov to %r11 isn't an immediate move, it's a memory read. So > %r11 will contain the *contents* of 0xffffffff809bf7a, not the address > itself (note the missing '$' as in the shr instruction above it). Argh! THAT was the sanity-check I needed. Thanks again, Matt. "It's always some mundane detail." --Michael Bolton Eric