From owner-freebsd-current@freebsd.org  Mon Nov  9 21:15:38 2015
Return-Path: <owner-freebsd-current@freebsd.org>
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 6E5BFA29ECF;
 Mon,  9 Nov 2015 21:15:38 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4C1A31DE6;
 Mon,  9 Nov 2015 21:15:38 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net
 [73.231.226.104])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id E200EB923;
 Mon,  9 Nov 2015 16:15:35 -0500 (EST)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-current@freebsd.org
Cc: Hans Petter Selasky <hps@selasky.org>, Andriy Gapon <avg@freebsd.org>,
 FreeBSD Current <freebsd-current@freebsd.org>,
 FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject: Re: strange kernel crash
Date: Mon, 09 Nov 2015 12:16:38 -0800
Message-ID: <2278845.gkxYBUMIWE@ralph.baldwin.cx>
User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; )
In-Reply-To: <563CEB53.50909@selasky.org>
References: <563C8CED.3020101@FreeBSD.org> <563CEB53.50909@selasky.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Mon, 09 Nov 2015 16:15:36 -0500 (EST)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2015 21:15:38 -0000

On Friday, November 06, 2015 07:02:59 PM Hans Petter Selasky wrote:
> On 11/06/15 12:20, Andriy Gapon wrote:
> > Now the strange part:
> >
> >     0xffffffff80619a18 <+744>:   jne    0xffffffff80619a61 <__mtx_lock_flags+817>
> >     0xffffffff80619a1a <+746>:   mov    %rbx,(%rsp)
> > => 0xffffffff80619a1e <+750>:   movq   $0x0,0x18(%rsp)
> >     0xffffffff80619a27 <+759>:   movq   $0x0,0x10(%rsp)
> >     0xffffffff80619a30 <+768>:   movq   $0x0,0x8(%rsp)
> 
> Were these instructions dumped from RAM or from the kernel ELF file?

Probably not from RAM.  You can use 'info files' in gdb to see what is
handling the address range in question (core vs executable).  x/i in ddb
would have been the "real" truth.

-- 
John Baldwin