From owner-freebsd-stable@FreeBSD.ORG Wed May 20 20:15:34 2009 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 476401065680 for ; Wed, 20 May 2009 20:15:34 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id F29468FC16 for ; Wed, 20 May 2009 20:15:33 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1M6sCK-0007fQ-EE for freebsd-stable@freebsd.org; Wed, 20 May 2009 20:15:32 +0000 Received: from 200.41.broadband11.iol.cz ([90.178.41.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 May 2009 20:15:32 +0000 Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 May 2009 20:15:32 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: martinko Date: Wed, 20 May 2009 22:15:19 +0200 Lines: 13 Message-ID: <4A1464D7.501@users.sf.net> References: <4A08A132.3070503@users.sf.net> <20090511224957.GB52703@dan.emsphone.com> <4A09DCF3.3010600@users.sf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.18) Gecko/20081125 SeaMonkey/1.1.13 In-Reply-To: Sender: news Cc: scottl@freebsd.org Subject: Re: run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config 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: Wed, 20 May 2009 20:15:34 -0000 David La Croix wrote: > I experienced the same problem (same motherboard) ... both amd64 > and i386 versions did the exact same thing ... > > I got the installer to work by going into the BIOS and disabling the > onboard firewire. Well, I can confirm that disabling on-board FireWire helps (though it is workaround only which may be an issue for users of FireWire devices). Thank you, David, for the hint! M.