[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A6598B.5080004@s5r6.in-berlin.de>
Date: Tue, 24 Jul 2007 21:56:59 +0200
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Manuel Lauss <mano@...rinelk.homelinux.net>
CC: Andreas Micklei <andreas.micklei@...star.de>,
Andreas Messer <andreas.messer@...d-mail.uni-wuerzburg.de>,
linux-kernel@...r.kernel.org, linux1394-devel@...ts.sourceforge.net
Subject: Re: [BUG] firewire: mass-storage i/o-problems
Manuel Lauss wrote:
> Actually, copying data to the disk while playing/seeking through a moviefile
> which is also located on it is already enough. Forget the NFS thing...
>
> Afterwards the firewire_sbp2 module has to be rmmod-ed and modprobed again
> or it will continue to throw errors even for single reads.
>
> I hope this helps tracking it down...
I tried this and similar tests on my main PC (PCIe based) and on an
Athlon/KM266 PC, with 1394b and 1394a hardware. Nothing happened,
except for a single "status write for unknown orb", followed by command
abort from which the disk immediately recovered. I did many tests and
it didn't happen again. I.e. it's probable that the supposed bug
happens here too, but very rarely.
Could you (and everyone else who has repeated I/O errors with the new
drivers, but not with the old drivers) test the attached patches, one
patch at a time? They apply to 2.6.22.
--
Stefan Richter
-=====-=-=== -=== ==---
http://arcgraph.de/sr/
View attachment "test1-firewire-fw-sbp2-default-to-128k-transfers.patch" of type "text/plain" (853 bytes)
View attachment "test2-firewire-fw-sbp2-increase-busy-timeout.patch" of type "text/plain" (2133 bytes)
Powered by blists - more mailing lists