From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 21 08:53:34 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D0AC16A41F for ; Wed, 21 Dec 2005 08:53:34 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from kosh.jetnet.co.uk (kosh.jetnet.co.uk [80.87.128.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2765D43D46 for ; Wed, 21 Dec 2005 08:53:34 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from localhost (localhost [127.0.0.1]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 365EC213E5 for ; Wed, 21 Dec 2005 08:53:33 +0000 (GMT) Received: from kosh.jetnet.co.uk ([127.0.0.1]) by localhost (mail.jetnet.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 88101-05-2 for ; Wed, 21 Dec 2005 08:53:24 +0000 (GMT) Received: from [192.168.0.90] (82-69-108-39.dsl.in-addr.zen.co.uk [82.69.108.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kosh.jetnet.co.uk (Postfix) with ESMTP id 4B00820C43 for ; Wed, 21 Dec 2005 08:53:24 +0000 (GMT) Message-ID: <43A91804.4090301@jetnet.co.uk> Date: Wed, 21 Dec 2005 08:53:24 +0000 From: David Reid User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051216) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD AMD64 Mailing List X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at jetnet.co.uk Cc: Subject: how to get more info #2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2005 08:53:34 -0000 Following on from my last attempt to get more information on why my box keeps rebooting, it was suggested that the lack of panics was a function of running under X. Off list it was suggested I try remote debugging via firewire, something I have now done. The panic showed up in vm_map_entry_splay as a page fault. The function was called following a trap 0xc. I tried to get into gdb to get more information but it complained about a lack of remote debuggers. As I'm still new to the remote debugging thing does anyone have any pointers/suggestions for how to extract more information next time it crashes and what sort of information I should post? Thanks, david