From owner-freebsd-current@FreeBSD.ORG Tue Apr 20 21:48:29 2010 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C806A1065675; Tue, 20 Apr 2010 21:48:29 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id 82CD38FC17; Tue, 20 Apr 2010 21:48:29 +0000 (UTC) Received: from [192.168.1.38] (S0106005004e13421.vs.shawcable.net [70.71.175.212]) (authenticated bits=0) by sippysoft.com (8.14.3/8.14.3) with ESMTP id o3KLmQNb005759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Apr 2010 14:48:27 -0700 (PDT) (envelope-from sobomax@sippysoft.com) Message-ID: <4BCE212B.4060205@sippysoft.com> Date: Tue, 20 Apr 2010 14:48:27 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: John Baldwin References: <4BCD5A7B.2070505@FreeBSD.org> <4BCD5C20.8000508@FreeBSD.org> <4BCD9E72.1000502@FreeBSD.org> <201004200920.08846.jhb@freebsd.org> In-Reply-To: <201004200920.08846.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 20 Apr 2010 22:07:56 +0000 Cc: freebsd-hackers@FreeBSD.ORG, "current@freebsd.org" Subject: Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Apr 2010 21:48:29 -0000 John Baldwin wrote: > On Tuesday 20 April 2010 8:30:42 am Maxim Sobolev wrote: >> Update: I've discovered that the 7.3 kernels actually boot after some >> ridiculously long waiting period after the "boot" command (i.e. 10 >> minutes or even more). I suspect that it might be caused by the memory >> probing, which as far as I know the FreeBSD does to determine if the >> physical memory that has been reported by BIOS really exists. >> >> Here is what kernel reports about RAM: >> >> http://sobomax.sippysoft.com/ScreenShot605.png >> >> Any comments? > > Maybe try adding > > hint.atkbdc.0.disabled="1" > hint.atkbd.0.disabled="1" > > to /boot/device.hints? That has reportedly removed minute-long boot delays on > some Nehalem machines. No, that have not helped at all. I measured the delay - it's about 6 minutes. Do you or anybody else have other ideas? Regards, -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts T/F: +1-646-651-1110 Web: http://www.sippysoft.com MSN: sales@sippysoft.com Skype: SippySoft