From owner-freebsd-current@FreeBSD.ORG  Tue Oct  9 08:26:26 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D54CC16A41B
	for <freebsd-current@freebsd.org>; Tue,  9 Oct 2007 08:26:26 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36])
	by mx1.freebsd.org (Postfix) with ESMTP id 04E2A13C45A;
	Tue,  9 Oct 2007 08:26:25 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <470B3B31.10307@FreeBSD.org>
Date: Tue, 09 Oct 2007 10:26:25 +0200
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Randall Stewart <rrs@cisco.com>
References: <470AE33B.7000806@cisco.com> <470AE40D.7090006@cisco.com>
In-Reply-To: <470AE40D.7090006@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Michael Tuexen <tuexen@fh-muenster.de>, freebsd-current@freebsd.org
Subject: Re: AMD64 panic on boot
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2007 08:26:26 -0000

Randall Stewart wrote:
> Randall Stewart wrote:
>> Hi all:
>>
>> I just updated to the latest.. and I am seeing a crash on
>> boot up of my 8-core Xeon machines (running in AMD mode).
>>
>> its a
>>
>> pagefault UA= 0x2b
>>
>> sysctl_handle_int+0x27
>> syscall+0x254
>> Xfast_syscall+0xab
>>
>> IP= 0xffffffff8048e7d7
>>
>>
>> I can't get a core unfortunately.. I get a core device
>> unavailable..
>>
>> I have one of the machines sitting in a DDB> prompt
>> and its twin sitting on the old kernel..
>>
>> Let me know how I can help.. and in the mean time I will poke
>> around in kgdb on the running machine :-)
>>
>> R
> Hmm.. it appears to be in..
> 0xffffffff8048e2e7 is in sysctl_handle_int 
> (../../../kern/kern_sysctl.c:816).
> 811              */
> 812             if (arg1)
> 813                     tmpout = *(int *)arg1;
> 814             else
> 815                     tmpout = arg2;
> 816             error = SYSCTL_OUT(req, &tmpout, sizeof(int));
> 817
> 818             if (error || !req->newptr)
> 819                     return (error);
> 
> 
> So its trying to copy out and faulting.. not sure what..
> 
> Let me know if there is some info I can poke out of DDB
> 
> R
> 
> 

I also saw a page fault from sysctl -a the other day...I thought it 
might be my fault (from my p4 branch, not cvs) but didnt investigate. 
Maybe it wasn't.

Kris