From owner-freebsd-bugs@FreeBSD.ORG  Mon Aug  9 04:52:00 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1754716A4CE
	for <freebsd-bugs@freebsd.org>; Mon,  9 Aug 2004 04:52:00 +0000 (GMT)
Received: from sqnork.irq.org (q.xs4all.nl [194.109.236.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DA5E743D1D
	for <freebsd-bugs@freebsd.org>; Mon,  9 Aug 2004 04:51:58 +0000 (GMT)
	(envelope-from bofn@sqnork.irq.org)
Received: by sqnork.irq.org (CommuniGate Pro PIPE 4.1.8)
  with PIPE id 3737377; Mon, 09 Aug 2004 06:51:55 +0200
X-MailScan: 7564953-0808528408
Received: from [203.97.2.243] (account bofn@sqnork.irq.org)
  by sqnork.irq.org (CommuniGate Pro WebUser 4.1.8)
  with HTTP id 3737383; Mon, 09 Aug 2004 06:51:51 +0200
From: "bofn" <bofn@irq.org>
To: freebsd-bugs@freebsd.org
X-Mailer: CommuniGate Pro WebUser Interface v.4.1.8
Date: Mon, 09 Aug 2004 06:51:51 +0200
Message-ID: <web-3737383@sqnork.irq.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
cc: hsu@bbnetworks.net
Subject: kern/68978 ,  Firewire crashes, loose pointers in kernel ?
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Aug 2004 04:52:00 -0000

Hi,

i have the same issue but with brand new hardware running 4.10 stable todays
build. 

it happens when i pump a fast data stream to the device for a few minutes.
it doesnt matter if i use tar to the raw device, or a file to a fs on the disk.
the enclosure goes into a error state after this.

it works fine when talking to an OS-X or Win2K system.

this is the log after a tar dump to /dev/da0: 
----------8<-------------------------
da0 at sbp0 bus 0 target 0 lun 0
da0: <Prolific (1394 ATAPI,Rev 0102> Fixed Simplified Direct Access SCSI-4
device 
da0: 50.000MB/s transfers
da0: 190782MB (390721968 512 byte sectors: 255H 63S/T 24321C)
sbp0:0:0 request timeout(cmd orb:0x1a18d76c) ... agent reset
sbp0:0:0 request timeout(cmd orb:0x1a18d8a4) ... target reset
sbp0:0:0 request timeout(mgm orb:0x1a18d9dc) ... reset start
fwohci0: txd err=14 ack busy_X
fw_asybusy
fwohci0: txd err=14 ack busy_X
fw_asybusy
fwohci0: txd err=14 ack busy_X
fw_asybusy
fwohci0: txd err=14 ack busy_X
fw_asybusy
firewire0: max_asyretry exceeded
sbp0:0:0 sbp_reset_start failed: resp=16
firewire0: split transaction timeout dst=0xffc0 tl=0x39 state=8
sbp0:0:0 sbp_reset_start failed: resp=60