kern/74238: fw_rcv: unknown response; firewire ad-hoc work around fails;

[Simson Garfinkel]

>Number:         74238
>Category:       kern
>Synopsis:       fw_rcv: unknown response; firewire ad-hoc work around fails;
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 22 13:40:28 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Simson Garfinkel
>Release:        5.3-RC1 AMD64 &  5.3-BETA4
>Organization:
MIT
>Environment:
> uname -a
FreeBSD r2-old.nitroba.com 5.3-BETA4 FreeBSD 5.3-BETA4 #2: Sat Oct 16 14:35:21 EDT 2004     root at r2.nitroba.com:/usr/src/sys/i386/compile/R2  i386

FreeBSD r3.nitroba.com 5.3-RC1 FreeBSD 5.3-RC1 #0: Sat Oct 16 21:06:05 UTC 2004     root at fanboy.samsco.home:/usr/obj/usr/src/sys/GENERIC  amd64
[simsong at r3 ~] 314 % 

>Description:
I've also seen this problem on 5.3_RELENG (which, by the way, paniced on my hardware with that TCP problem.)

Firewire transfers cause these errors to show up on the console:
firewire0: split transaction timeout dst=0xffc0 tl=0x4 state=3
sbp_orb_pointer_callback: xfer->resp = 60
fw_rcv: unknown response WRES(2) src=0xffc0 tl=0x4 rt=1 data=0x84519637
try ad-hoc work around!!
no use...
firewire0: split transaction timeout dst=0xffc0 tl=0x2c state=3
sbp_orb_pointer_callback: xfer->resp = 60
fw_rcv: unknown response WRES(2) src=0xffc0 tl=0x2c rt=1 data=0x8451b42f
try ad-hoc work around!!
no use...

It doesn't seem to cause data los. Any thoughts?

>How-To-Repeat:
      copy files to the firewire drive. It has happened with 4 different drives I've tried.
>Fix:
      
>Release-Note:
>Audit-Trail:
>Unformatted: