From owner-freebsd-firewire@FreeBSD.ORG  Fri Dec 26 06:25:03 2008
Return-Path: <owner-freebsd-firewire@FreeBSD.ORG>
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 2F1461065670;
	Fri, 26 Dec 2008 06:25:03 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from sopwith.solgatos.com
	(pool-71-117-207-61.ptldor.fios.verizon.net [71.117.207.61])
	by mx1.freebsd.org (Postfix) with ESMTP id 9897B8FC14;
	Fri, 26 Dec 2008 06:25:02 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: by sopwith.solgatos.com (Postfix, from userid 66)
	id 32768B64F; Thu, 25 Dec 2008 22:21:06 -0800 (PST)
Received: from localhost by sopwith.solgatos.com (8.8.8/6.24)
	id GAA20643; Fri, 26 Dec 2008 06:23:09 GMT
Message-Id: <200812260623.GAA20643@sopwith.solgatos.com>
To: Sean Bruno <sbruno@miralink.com>
In-reply-to: Your message of "Mon, 22 Dec 2008 22:01:55 PST."
	<49507ED3.9010006@miralink.com> 
Date: Thu, 25 Dec 2008 22:23:09 +0000
From: Dieter <freebsd@sopwith.solgatos.com>
Cc: freebsd-firewire@freebsd.org, bug-followup@freebsd.org
Subject: Re: kern/118093: 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: Fri, 26 Dec 2008 06:25:03 -0000

> > I confirmed that spl's are complete no-ops since rel 5.  So, you want 
> > to ignore
> > them as they are just markers now where locking should be implemented.

I hunted down the spl code, and you're right.  Wow, I wonder how drivers
still using spl calls work at all?

> is to real behavior, but /var/log/messages has a tendency to get garbled 
> like this:
> 
> Dec 22 16:00:18 home-test kernel: fwohci1: Initiate bus reset
> Dec 22 16:00:18 home-test kernel: fwohci1: BUS reset
> Dec 22 16:00:18 home-test kernel: fwohci1: node_id=0xc800ffc0, gen=8, 
> CYCLEMASTER mode
> Dec 22 16:00:18 home-test kernel: firewi
> Dec 22 16:00:18 home-test kernel: re1:
> Dec 22 16:00:18 home-test kernel: 1 n
> Dec 22 16:00:18 home-test kernel: odes
> Dec 22 16:00:18 home-test kernel: , ma
> Dec 22 16:00:18 home-test kernel: xhop
> Dec 22 16:00:18 home-test kernel: <=
> Dec 22 16:00:18 home-test kernel: 0, c
> Dec 22 16:00:18 home-test kernel: able

Do the lines get folded on the console, or only in /var/log/messages?