From owner-freebsd-bugs@FreeBSD.ORG Wed Nov 24 14:30:25 2010 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35A211065695 for ; Wed, 24 Nov 2010 14:30:25 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 097688FC15 for ; Wed, 24 Nov 2010 14:30:25 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oAOEUOMu026671 for ; Wed, 24 Nov 2010 14:30:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oAOEUOSh026662; Wed, 24 Nov 2010 14:30:24 GMT (envelope-from gnats) Date: Wed, 24 Nov 2010 14:30:24 GMT Message-Id: <201011241430.oAOEUOSh026662@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Fulvio Ciriaco Cc: Subject: Re: kern/151924: very slow boot from disk: 15m+ X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fulvio Ciriaco List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2010 14:30:25 -0000 The following reply was made to PR kern/151924; it has been noted by GNATS. From: Fulvio Ciriaco To: Remko Lodder Cc: fulvio ciriaco , freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/151924: very slow boot from disk: 15m+ Date: Wed, 24 Nov 2010 15:29:51 +0100 Hallo, I recently hit a problem with linux 2.6.32 kernel which might be related to the present problem with freebsd boot. At times the system became unresponsive for a short period of time and the message: ata1.00: exception Emask 0x0 SAct ... appeared in dmesg. The solution was to put pci=noacpi in the boot options. Any similar option on FreeBSD disabling only part of acpi? Fulvio At Thu, 4 Nov 2010 11:23:31 +0100, Remko Lodder wrote: > > > > > Can you also send a verbose boot (dmesg) so that we can see how the hardware probing etc goes? To be honest; > the information you send in now, is not enough to see and understand why this takes long. It would also be great > if you can have a look whether or not there are error messages in the logfiles (/var/log/*) that might suggest that > there are timeouts or something (which in turn might indicate that the disk is having problems or something). > > Thanks, > Remko > > -- > /"\ Best regards, | remko@FreeBSD.org > \ / Remko Lodder | > X http://www.evilcoder.org/ | Quis custodiet ipsos custodes > / \ ASCII Ribbon Campaign | Against HTML Mail and News > > > >