From owner-freebsd-stable@FreeBSD.ORG Mon Feb 1 09:37:40 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 705D010656E1 for ; Mon, 1 Feb 2010 09:37:40 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B32158FC1E for ; Mon, 1 Feb 2010 09:37:39 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA19832; Mon, 01 Feb 2010 11:37:35 +0200 (EET) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Nbsit-000H8C-8c; Mon, 01 Feb 2010 11:37:35 +0200 Message-ID: <4B66A0DD.2070109@icyb.net.ua> Date: Mon, 01 Feb 2010 11:37:33 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091128) MIME-Version: 1.0 To: Peter Jeremy References: <20100201085131.GA34006@server.vk2pj.dyndns.org> In-Reply-To: <20100201085131.GA34006@server.vk2pj.dyndns.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Kernel probe order issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2010 09:37:40 -0000 on 01/02/2010 10:51 Peter Jeremy said the following: > Whilst trying to boot a brand new FreeBSD 8-stable/amd64 kernel, > I ran into an unfortunate nasty with the kernel probe order. > > This particular box has no PS/2 ports so I have a USB keyboard and > have removed atkbd et al from my kernel config. Unfortunately, whilst > trying to merge changes from 5 different sources, I also accidently > deleted my HDD controller. Quite reasonably, the lack of disk > controller made the kernel spit out an error message and "mountroot>" > prompt. Unfortunately, this occurs after the kernel has switched from > BIOS to its own drivers but _before_ ukbd(4) is probed so I didn't > have any keyboard. (Some experimenting with a serial console > confirmed that ukbd is probed after the root device). > > This strikes me as undesirable. Is there some way to bump up the > probe/attach priority of console input devices to ensure that they > exist before the kernel tries to read input? It seems to be a problem with either your keyboard or your USB controller. USB keyboard can be discovered much earlier than mountroot if the hardware is ready. No magical software priority bump can help here. -- Andriy Gapon