From owner-freebsd-current@FreeBSD.ORG Thu Apr 22 10:05:16 2010 Return-Path: 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 1D315106564A; Thu, 22 Apr 2010 10:05:16 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id C332A8FC08; Thu, 22 Apr 2010 10:05:15 +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 o3MA51hW018994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Apr 2010 03:05:02 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <4BD01F50.6070403@FreeBSD.org> Date: Thu, 22 Apr 2010 03:05:04 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 References: <4BCD5A7B.2070505@FreeBSD.org> <4BCE2E52.1080107@FreeBSD.org> <4BCE3A52.7060502@feral.com> <201004211004.25701.jhb@freebsd.org> <4BCF5AC1.8080608@FreeBSD.org> In-Reply-To: <4BCF5AC1.8080608@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, mj@feral.com, John Baldwin 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: Thu, 22 Apr 2010 10:05:16 -0000 Maxim Sobolev wrote: > There is already a code to detect non-existing AT keyboard and avoid > attaching atkbd to it. The code is i386-only at the moment, I am trying > to figure out how to modify it so that it works on amd64 as well. Looks like this huge delay is caused by the inb() being astonishingly slow, which is not factored by the timeout routines. Reading keyboard status port once takes about 0.003s! I am not sure if it's common behaviour of the platform, or something specific to this particular model. Do you know by any chance? -Maxim