From owner-freebsd-current@FreeBSD.ORG Tue Apr 27 23:06:38 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 29ED9106564A; Tue, 27 Apr 2010 23:06:38 +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 CB1798FC13; Tue, 27 Apr 2010 23:06:37 +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 o3RN6X7r065752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Apr 2010 16:06:33 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <4BD76E04.30604@FreeBSD.org> Date: Tue, 27 Apr 2010 16:06:44 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Alexander Sack References: <4BCD5A7B.2070505@FreeBSD.org> <201004271654.07340.jhb@freebsd.org> <4BD751DD.80407@FreeBSD.org> <201004271725.36518.jhb@freebsd.org> In-Reply-To: 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: Tue, 27 Apr 2010 23:06:38 -0000 Alexander Sack wrote: > On Tue, Apr 27, 2010 at 5:25 PM, John Baldwin wrote: >> On Tuesday 27 April 2010 5:06:37 pm Maxim Sobolev wrote: >>> John Baldwin wrote: >>>> On Tuesday 27 April 2010 4:26:09 pm Maxim Sobolev wrote: >>>>> John Baldwin wrote: >>>>>> Hmm, I think you should definitely commit the atkbdc_isa.c change first of >>>>>> all. I'm still thinking about the other change. I wonder if we can figure >>>>>> out that a keyboard isn't present sooner somehow? Do you know if the keyboard >>>>>> appears to be present but just slow vs if the keyboard is eventually found to >>>>>> not be present? >>>>> Our syscons does keyboard probing two times - once early during kernel >>>>> initialization before most of the subsystems have been initialized yet, >>>>> and then "real" probing later in boot process. Interesting thing is that >>>>> initially keyboard looks present. Reading status port in >>>>> atkbdc_configure() gives value other than 0xff, although reading is >>>>> thousand times slower than usually. This causes syscons try attaching >>>>> it. Even though reading status port works, apparently either emulation >>>>> is not complete or there is some other issue, so that it never responds >>>>> to some commands. Slow access and lack of response results in >>>>> wait_for_data() function waiting several minutes instead of 200ms as >>>>> designed. This what causes that 6-10 minutes delay in boot process. >>>> I believe the USB driver has disabled the keyboard emulation by the time the >>>> second probe happens in syscons. Can you try disabling legacy USB support in >>>> the BIOS just to make sure that is what causes the delay? >>> Unfortunately it's not possible. Hosting provider doesn't allow me to >>> have access to BIOS settings. > > Stunt double: I tried it and it has no effect. The waits in atkdbd > kills it with or without USB legacy support on. The wait on this > machine is about 1-2 minutes before boot. Just another data point. Have you tried my patch? Does it help? -Maxim