From owner-freebsd-firewire@FreeBSD.ORG Mon Aug 17 11:06:53 2009 Return-Path: Delivered-To: freebsd-firewire@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5567E106568B for ; Mon, 17 Aug 2009 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 42FB48FC60 for ; Mon, 17 Aug 2009 11:06:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n7HB6rUJ075763 for ; Mon, 17 Aug 2009 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n7HB6qF8075759 for freebsd-firewire@FreeBSD.org; Mon, 17 Aug 2009 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 17 Aug 2009 11:06:52 GMT Message-Id: <200908171106.n7HB6qF8075759@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-firewire@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2009 11:06:53 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re o kern/136652 firewire [firewire] Firewire-attached "WD My Book 1028" does no p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total. From owner-freebsd-firewire@FreeBSD.ORG Thu Aug 20 08:15:16 2009 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 826AB106568B for ; Thu, 20 Aug 2009 08:15:16 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id 48FA78FC60 for ; Thu, 20 Aug 2009 08:15:16 +0000 (UTC) Received: (qmail 15814 invoked from network); 20 Aug 2009 01:15:15 -0700 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.200?) (69.64.235.60) by iron2.pdx.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 20 Aug 2009 01:15:15 -0700 From: Sean Bruno To: freebsd-current@freebsd.org Content-Type: text/plain Date: Thu, 20 Aug 2009 01:15:14 -0700 Message-Id: <1250756114.23644.8.camel@Lappy> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) Content-Transfer-Encoding: 7bit Cc: freebsd-firewire Subject: Have *you* disabled Firewire? X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2009 08:15:16 -0000 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? Sean From owner-freebsd-firewire@FreeBSD.ORG Thu Aug 20 21:51:49 2009 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D92E6106568C for ; Thu, 20 Aug 2009 21:51:49 +0000 (UTC) (envelope-from freebsd-firewire@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 951998FC6C for ; Thu, 20 Aug 2009 21:51:49 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1MeFXv-0004Z1-Q1 for freebsd-firewire@freebsd.org; Thu, 20 Aug 2009 23:51:47 +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:51:47 +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:51:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-firewire@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-current@freebsd.org Subject: Re: Have *you* disabled Firewire? X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2009 21:51:49 -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 From owner-freebsd-firewire@FreeBSD.ORG Thu Aug 20 23:55:44 2009 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF381106568B for ; Thu, 20 Aug 2009 23:55:44 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id B2F1B8FC43 for ; Thu, 20 Aug 2009 23:55:44 +0000 (UTC) Received: (qmail 22739 invoked from network); 20 Aug 2009 16:55:41 -0700 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.200?) (69.64.235.60) by iron2.pdx.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 20 Aug 2009 16:55:41 -0700 From: Sean Bruno To: Julian Stecklina In-Reply-To: <87hbw2gnn3.fsf@tabernacle.localhost> References: <1250756114.23644.8.camel@Lappy> <87hbw2gnn3.fsf@tabernacle.localhost> Content-Type: text/plain Date: Thu, 20 Aug 2009 16:55:43 -0700 Message-Id: <1250812543.2680.21.camel@Lappy> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) Content-Transfer-Encoding: 7bit Cc: freebsd-firewire Subject: Re: Have *you* disabled Firewire? X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2009 23:55:45 -0000 [ removing -current ] On Thu, 2009-08-20 at 23:51 +0200, Julian Stecklina wrote: > 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? > Hangs yes. If one waits long enough(2 minutes I think), it will panic. > > 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, I'm trying to gather information, thanks for the reminder about your specific hardware. (JMicron based) I've got the same failures reported with JMicron and NVidia based controllers. I will peruse the logs of all the failures and try to come up with something soon. :) Sean