From owner-freebsd-current@FreeBSD.ORG Sun Nov 13 17:11:40 2011 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 57DFB106566B for ; Sun, 13 Nov 2011 17:11:40 +0000 (UTC) (envelope-from rdeiriar@spock.cl) Received: from mail.spock.cl (enteljoven2.enteljoven.cl [164.77.63.23]) by mx1.freebsd.org (Postfix) with ESMTP id BC0A38FC16 for ; Sun, 13 Nov 2011 17:11:39 +0000 (UTC) Received: from [192.168.1.100] (pc-17-182-45-190.cm.vtr.net [190.45.182.17]) (AUTH: PLAIN rdeiriar@spock.cl, TLS: TLSv1/SSLv3, 256bits, CAMELLIA256-SHA) by mail.spock.cl with ESMTPSA; Sun, 13 Nov 2011 14:11:35 -0300 id 000004F5.000000004EBFFA47.00002ADC Message-ID: <4EBFFA2E.6030203@spock.cl> Date: Sun, 13 Nov 2011 14:11:10 -0300 From: Roberto de Iriarte User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0) Gecko/20110930 Thunderbird/7.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4EBF185F.2080106@cran.org.uk> <4EBF1DBA.40205@cran.org.uk> <4EBF7526.4090407@FreeBSD.org> In-Reply-To: <4EBF7526.4090407@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 9.0-RC1 fails to boot ("run_interrupt_driven_hooks: still waiting...") 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: Sun, 13 Nov 2011 17:11:40 -0000 I have a machine, an IBM x3550 M3 with an IBM M1015 card flashed to IT mode, in which i can produce this very same problem in some EFI BIOS configurations. I would be glad to help testing/debugging the problem Best regards, Roberto > on 13/11/2011 03:30 Bruce Cran said the following: >> On 13/11/2011 01:07, Bruce Cran wrote: >>> FreeBSD 9.0-RC1 doesn't boot on my Tyan S7025 system: it gets stuck at >>> xpt_config: >>> >>> run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config >>> run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config >>> run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config >>> run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config >>> run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config >> I had a Firewire card in the machine - removing it caused the problem to go away. >> > I think that Sean has been looking for someone who can reproduce the problem and > is willing to help debugging it. >