On Wednesday 29 of August 2007, Jens Axboe wrote: > On Wed, Aug 29 2007, Arkadiusz Miskiewicz wrote: > > On Wednesday 29 of August 2007, Jens Axboe wrote: > > > On Wed, Aug 29 2007, Arkadiusz Miskiewicz wrote: > > > > On Wednesday 29 of August 2007, Jens Axboe wrote: > > > > > On Wed, Aug 29 2007, Arkadiusz Miskiewicz wrote: > > > > > > I guess I should sent these here since it looks like not scsi bug > > > > > > anyway. > > > > > > > > > > It's stex, right? It seems to have some issues with multiple > > > > > completions of commands, which craps out the block layer of course. > > > > > > > > Yes, stex. I'm staying with 2.6.19 in that case since it works fine > > > > in that version. > > > > > > > > So scsi bug ... 8-) > > > > > > And you based that conclusion on what exactly? > > > > Isn't drivers/scsi/* handled by linux-scsi@? (that's what I mean) > > Yep indeed, I thought you meant that it was a scsi bug (and not an stex > one). You could try and copy the 2.6.19 stex driver into 2.6.20 and see > if that works, though. Looks like this bug is known for months :-( Ed Lin pointed to http://lkml.org/lkml/2007/1/23/268 with possible patch (that unfortunately serialises access to storage devices, well...) There is also: http://bugzilla.kernel.org/show_bug.cgi?id=7842 I'm running 2.6.22 with that patch now, did huge (few hours) rsync that previously caused oopses and now everything works properly. Can we get some form of this patch into Linus tree? -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
