On Tue, Jul 24, 2007 at 09:56:59PM +0200, Stefan Richter wrote: > 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.
I tried 2.6.23 in the meantime, it's *MUCH* harder to trigger; in fact I had to skip through movies for ~10 minutes to get the orb timeout. The disk was inaccessible for a few seconds then recovered fine. > 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. Will do. Thanks, Manuel Lauss - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/