From owner-freebsd-firewire@FreeBSD.ORG  Mon Feb  2 21:13:41 2009
Return-Path: <owner-freebsd-firewire@FreeBSD.ORG>
Delivered-To: freebsd-firewire@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 790EE106568D;
	Mon,  2 Feb 2009 21:13:41 +0000 (UTC)
	(envelope-from gavin@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 4DEB78FC0A;
	Mon,  2 Feb 2009 21:13:41 +0000 (UTC)
	(envelope-from gavin@FreeBSD.org)
Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n12LDf3L059998;
	Mon, 2 Feb 2009 21:13:41 GMT
	(envelope-from gavin@freefall.freebsd.org)
Received: (from gavin@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n12LDfEI059994;
	Mon, 2 Feb 2009 21:13:41 GMT (envelope-from gavin)
Date: Mon, 2 Feb 2009 21:13:41 GMT
Message-Id: <200902022113.n12LDfEI059994@freefall.freebsd.org>
To: gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-firewire@FreeBSD.org
From: gavin@FreeBSD.org
Cc: 
Subject: Re: kern/118093: [firewire] firewire bus reset hogs CPU,
	causing data to be lost
X-BeenThere: freebsd-firewire@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Firewire support in FreeBSD <freebsd-firewire.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-firewire>, 
	<mailto:freebsd-firewire-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-firewire>
List-Post: <mailto:freebsd-firewire@freebsd.org>
List-Help: <mailto:freebsd-firewire-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-firewire>, 
	<mailto:freebsd-firewire-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2009 21:13:42 -0000

Synopsis: [firewire] firewire bus reset hogs CPU, causing data to be lost

Responsible-Changed-From-To: freebsd-bugs->freebsd-firewire
Responsible-Changed-By: gavin
Responsible-Changed-When: Mon Feb 2 21:11:18 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).  This looks like it may be some bad
interaction between the firewire stack and using a serial
console.  To submitter: It may be worth while switching to
uart(4) rather than sio(4) for your serial ports and seeing
if that makes any difference (as I don't think uart(4) uses
the Giant lock).

http://www.freebsd.org/cgi/query-pr.cgi?pr=118093