From owner-freebsd-drivers@FreeBSD.ORG  Wed Dec 17 05:10:24 2008
Return-Path: <owner-freebsd-drivers@FreeBSD.ORG>
Delivered-To: freebsd-drivers@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1AC52106564A;
	Wed, 17 Dec 2008 05:10:24 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from sopwith.solgatos.com
	(pool-71-182-69-106.ptldor.fios.verizon.net [71.182.69.106])
	by mx1.freebsd.org (Postfix) with ESMTP id 8C7028FC18;
	Wed, 17 Dec 2008 05:10:22 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: by sopwith.solgatos.com (Postfix, from userid 66)
	id 9B0D13F22; Tue, 16 Dec 2008 20:51:06 -0800 (PST)
Received: from localhost by sopwith.solgatos.com (8.8.8/6.24)
	id DAA17848; Wed, 17 Dec 2008 03:29:13 GMT
Message-Id: <200812170329.DAA17848@sopwith.solgatos.com>
To: freebsd-firewire@FreeBSD.org, freebsd-drivers@FreeBSD.org,
	bug-followup@FreeBSD.org
In-reply-to: Your message of "Tue, 16 Dec 2008 09:51:44 PST."
	<4947EAB0.3020704@miralink.com> 
Date: Tue, 16 Dec 2008 19:29:13 +0000
From: Dieter <freebsd@sopwith.solgatos.com>
Cc: 
Subject: Re: kern/118093: firewire bus reset hogs CPU,
	causing data to be lost 
X-BeenThere: freebsd-drivers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Writing device drivers for FreeBSD <freebsd-drivers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-drivers>, 
	<mailto:freebsd-drivers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-drivers>
List-Post: <mailto:freebsd-drivers@freebsd.org>
List-Help: <mailto:freebsd-drivers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-drivers>,
	<mailto:freebsd-drivers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2008 05:10:24 -0000

Sean>  Which file in dev/firewire are you looking at?

fwohci.c  and  firewire.c

examples:

printf("non CYCLEMASTER mode\n");

device_printf(fc->dev, "Initiate bus reset\n");

-------------------

Warner>  This can't be the case.  There's no SPL involved at all.  Maybe
Warner>  removing the printfs causes an interrupt to be serviced faster,
Warner>  resulting in what appears to be better performance...

With the printfs, Ethernet is not getting serviced.  This
is repeatable and easily reproduced.   Without the printfs,
it seems ok.

If it isn't spl, what is locking out Ethernet?