Date: Mon, 24 Aug 2009 11:49:33 +1000 From: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> To: Sean Bruno <sean.bruno@dsl-only.net> Cc: freebsd-current@freebsd.org, freebsd-firewire <freebsd-firewire@freebsd.org> Subject: Re: Have *you* disabled Firewire? Message-ID: <20090824014933.GA52180@duncan.reilly.home> In-Reply-To: <1250756114.23644.8.camel@Lappy> References: <1250756114.23644.8.camel@Lappy>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090824014933.GA52180>