From owner-freebsd-firewire@FreeBSD.ORG  Tue Aug 19 06:23:45 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 163C71065675;
	Tue, 19 Aug 2008 06:23:45 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from parsely.rain.com (parsely.rain.com [199.26.172.196])
	by mx1.freebsd.org (Postfix) with ESMTP id 5E8128FC24;
	Tue, 19 Aug 2008 06:23:44 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from sopwith.solgatos.com (uucp@localhost)
	by parsely.rain.com (8.11.4/8.11.4) with UUCP id m7J6NZh52792;
	Mon, 18 Aug 2008 23:23:35 -0700 (PDT)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from localhost by sopwith.solgatos.com (8.8.8/6.24)
	id GAA18270; Tue, 19 Aug 2008 06:22:29 GMT
Message-Id: <200808190622.GAA18270@sopwith.solgatos.com>
To: Sean Bruno <sbruno@miralink.com>
In-reply-to: Your message of "Mon, 18 Aug 2008 15:27:01 PDT."
	<48A9F735.5090507@miralink.com> 
Date: Mon, 18 Aug 2008 23:22:29 +0100
From: Dieter <freebsd@sopwith.solgatos.com>
Cc: Scott Long <scottl@samsco.org>, freebsd-firewire@freebsd.org
Subject: Re: Something broke :-( Re: fwcontrol update 
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: Tue, 19 Aug 2008 06:23:45 -0000

> > I notice that it doesn't print every generation.
> > I notice that the node_id changes.
>
>
> This alarms me quite a bit.  I didn't think there was anyway for the 
> generation to change
> without the log message being spit out.  Interesting.

Perhaps there is some register on the controller chip that
affects receiving data but not sending it, and isn't getting
initialized.  Perhaps the controller chip thinks it is receiving
bad data, and flags an error or requests a bus reset?

If the resets are happening faster than the printf can run,
maybe the data (generation number) changes underneath the printf,
much like ps/top don't get a pure snapshot?