From owner-freebsd-hackers@FreeBSD.ORG  Fri Jul 19 19:32:44 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 348DD695;
 Fri, 19 Jul 2013 19:32:44 +0000 (UTC) (envelope-from yuri@rawbw.com)
Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45])
 by mx1.freebsd.org (Postfix) with ESMTP id 1271AD53;
 Fri, 19 Jul 2013 19:32:43 +0000 (UTC)
Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1])
 (authenticated bits=0)
 by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id r6JJWhTf031547;
 Fri, 19 Jul 2013 12:32:43 -0700 (PDT) (envelope-from yuri@rawbw.com)
Message-ID: <51E9945B.1050907@rawbw.com>
Date: Fri, 19 Jul 2013 12:32:43 -0700
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130628 Thunderbird/17.0.7
MIME-Version: 1.0
To: John Baldwin <jhb@freebsd.org>
Subject: Re: Kernel crashes after sleep: how to debug?
References: <51E3A334.8020203@rawbw.com> <201307181652.48757.jhb@freebsd.org>
 <51E88EDA.50000@rawbw.com> <201307191100.08549.jhb@freebsd.org>
In-Reply-To: <201307191100.08549.jhb@freebsd.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Alan Cox <alc@freebsd.org>, freebsd-hackers@freebsd.org
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 19:32:44 -0000

On 07/19/2013 08:00, John Baldwin wrote:
> Well, you can probably find the value of 'm' in a register if you look at the
> dissassembly around the fault.  You can then cast that pointer to the right
> type and print its contents.

Here is the value of *m in frame 8:
(kgdb) p *(struct vm_page*)0xfffffe00b460abf8
$3 = {pageq = {tqe_next = 0xfe26, tqe_prev = 0xfffffe00b5a124d8}, listq 
= {tqe_next = 0xfffffe0081ad8f70, tqe_prev = 0xfffffe0081ad8f78},
left = 0x6, right = 0xd00000201, object = 0x100000000, pindex = 
4294901765, phys_addr = 18446741877712530608, md = {pv_list = {
tqh_first = 0xfffffe00b460abc0, tqh_last = 0xfffffe00b5579020}, pat_mode 
= -1268733096}, queue = 72 'H', segind = -85 '�',
hold_count = -19360, order = 0 '\0', pool = 254 '�', cow = 65535, 
wire_count = 0, aflags = 0 '\0', flags = 0 '\0', oflags = 0,
act_count = 0 '\0', busy = 176 '�', valid = 208 '�', dirty = 126 '~'}


Yuri