From owner-freebsd-current@FreeBSD.ORG Thu Aug 20 21:55:03 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 ACFF5106564A for ; Thu, 20 Aug 2009 21:55:03 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 690A48FC16 for ; Thu, 20 Aug 2009 21:55:03 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1MeFb4-0005jx-CF for freebsd-current@freebsd.org; Thu, 20 Aug 2009 23:55:02 +0200 Received: from dslb-094-222-063-132.pools.arcor-ip.net ([94.222.63.132]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 20 Aug 2009 23:55:02 +0200 Received: from js by dslb-094-222-063-132.pools.arcor-ip.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 20 Aug 2009 23:55:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Julian Stecklina Date: Thu, 20 Aug 2009 23:51:12 +0200 Lines: 30 Message-ID: <87hbw2gnn3.fsf@tabernacle.localhost> References: <1250756114.23644.8.camel@Lappy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: dslb-094-222-063-132.pools.arcor-ip.net User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:M/R+zdd7rUYAQWxqEZw4fMTVnMk= Sender: news Cc: freebsd-firewire@freebsd.org 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: Thu, 20 Aug 2009 21:55:03 -0000 Sean Bruno writes: > 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" Panic? Most people reported hangs, haven't they? > 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 did provide this some months ago for my AMD 780G-based board. Was there anything that looked suspicious? Is it worth retrying? Regards, -- Julian Stecklina The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners - Ernst Jan Plugge