From owner-freebsd-questions@FreeBSD.ORG Wed Jun 12 19:57:22 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F3405C6B for ; Wed, 12 Jun 2013 19:57:22 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from april.london.02.net (april.london.02.net [87.194.255.143]) by mx1.freebsd.org (Postfix) with ESMTP id C25B41E20 for ; Wed, 12 Jun 2013 19:57:22 +0000 (UTC) Received: from [192.168.2.50] (149.241.239.214) by april.london.02.net (8.5.140) id 50D0FF990DE6A3B1 for freebsd-questions@freebsd.org; Wed, 12 Jun 2013 20:56:07 +0100 Message-ID: <51B8D257.8080501@onetel.com> Date: Wed, 12 Jun 2013 20:56:07 +0100 From: Chris Whitehouse User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111228 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: 9.1-RELEASE slow boot References: <20130607230429.a090ca0c.freebsd@edvax.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jun 2013 19:57:23 -0000 >>> On Fri, 7 Jun 2013 19:38:34 +0200, Fernando Apesteguía wrote: >>>> Since I updated to 9.1-RELEASE my boot process seems to stall for a >>>> while. Booting in verbose mode shows messages like these ones: >>>> >>>> Opening device da0 -> 6 (repeated like 30 times or so) >>>> Opening device da1 -> 6 (repeated like 30 times or so) >>>> Opening device da2 -> 6 (repeated like 30 times or so) >>>> Opening device da3 -> 6 (repeated like 30 times or so) >>>> >>>> Those devices correspond to my internal SD card reader that doesn't >>>> work on FreeBSD anyway. This seems some kind of probing right? I don't >>>> want to wait for those devices. What can I do to speed up booting? I >>>> didn't change my system settings either. Did anything related change >>>> in the kernel about probing these type of devices? Since you are not using the device could you not just disable it in the BIOS? Chris