From owner-freebsd-current@FreeBSD.ORG Mon Aug 24 01:49:42 2009 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 182DA1065672 for ; Mon, 24 Aug 2009 01:49:42 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nskntmtas05p.mx.bigpond.com (nskntmtas05p.mx.bigpond.com [61.9.168.149]) by mx1.freebsd.org (Postfix) with ESMTP id 97A4C8FC0C for ; Mon, 24 Aug 2009 01:49:41 +0000 (UTC) Received: from nskntotgx02p.mx.bigpond.com ([124.188.162.219]) by nskntmtas05p.mx.bigpond.com with ESMTP id <20090824014939.DDVX1919.nskntmtas05p.mx.bigpond.com@nskntotgx02p.mx.bigpond.com> for ; Mon, 24 Aug 2009 01:49:39 +0000 Received: from areilly.bpa.nu ([124.188.162.219]) by nskntotgx02p.mx.bigpond.com with ESMTP id <20090824014939.BPYL19419.nskntotgx02p.mx.bigpond.com@areilly.bpa.nu> for ; Mon, 24 Aug 2009 01:49:39 +0000 Received: (qmail 53333 invoked by uid 501); 24 Aug 2009 01:49:33 -0000 Date: Mon, 24 Aug 2009 11:49:33 +1000 From: Andrew Reilly To: Sean Bruno Message-ID: <20090824014933.GA52180@duncan.reilly.home> References: <1250756114.23644.8.camel@Lappy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1250756114.23644.8.camel@Lappy> User-Agent: Mutt/1.4.2.3i X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150203.4A91F1B3.00A6,ss=1,fgs=0 X-SIH-MSG-ID: rRg1Fdf+TAD0zmQv0WC2OwcnyAzlq3Mv8Z4QX81loRIGTUDBp8PfStreLP1RsMuxxDxIJhqENGUpaa/tTY3RstCK Cc: freebsd-current@freebsd.org, freebsd-firewire Subject: Re: Have *you* disabled Firewire? 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: Mon, 24 Aug 2009 01:49:42 -0000 On Thu, Aug 20, 2009 at 01:15:14AM -0700, Sean Bruno wrote: > I'm seeing evidence that the Firewire stack has been problematic for a > small, but growing set of users out there. I see from a perusal of the > mailing lists, that some users are disabling their Firewire stack after > they cannot boot or install FreeBSD. This usually is due to a panic > preceded by the message:" > "run_interrupt_driven_hooks - waiting for xpt_config" > > This log message was added in the past to provide a diagnostic > indication of a failure. > > If you are one of these folks who have disabled their Firewire driver, > please let me know. Also get me the following: > Full boot dmesg output (bootverbose) > Can you load "firewire"?(in kernel? after boot via module?) > Can you load "sbp"?(in kernel? after boot via module?) > *anything* else you might thing is relevant? I get the xpt_config waits, but I have not disabled firewire: I just work around the problem by manually disconnecting the external drive in question and re-attaching it after the boot has failed and falled into single-user mode. It seems to work fine for post-boot arrival. Want my bootverbose logs? (I think that I posted them before, the first time around, but can probably make a new set.) Also: this does seem to be a race condition kind of thing, because in the intervening time I *have* had at least one successful, hands-off boot. Cheers, -- Andrew