We had this a coupe of times in the 2.0.x timeframe as well with
some drives. We emailed Leonard Z. about it a couple of times and
it turned out in all cases to be buggy firmware on the drives.
It might well be that the 2.2.x drivers / scsi layer does things
that 2.0.x didn't do, and that the drives firmware locks up. You
can start by trying to turn off tagged hash for example to see
if it helps. See the docs or source file of your scsi driver.
Sometimes you can also find firmware updates for the drive on
the manufacturers website, though I have no idea how to upgrade
the firmware on a SCSI drive.
HTH
Mike.
-- First things first, but not necessarily in that order.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/