On Sun, 2006-10-15 at 13:36 -0400, Steven N. Hirsch wrote: > <6> target0:0:0: ppr msgout: Parallel Protocol Request period = 12.5 ns offset = 62 width = 16 The driver asks for FAST-80 > <6> target0:0:0: ppr msgin: Parallel Protocol Request period = 25 ns offset = 62 width = 16 And the device denies the request and suggests FAST-40 instead > <6> target0:0:0: asynchronous > <6> 0:0:0:0: M_REJECT to send for : Parallel Protocol Request period = 25 ns offset = 62 width = 16 > <6> target0:0:0: ppr msgout: Parallel Protocol Request period = 25 ns offset = 31 width = 16 > <6> target0:0:0: ppr msgin: Parallel Protocol Request period = 25 ns offset = 31 width = 16 > <6> target0:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31) Which is what you eventually end up with. The driver is working as advertised ... the curiosity is why the device suggests FAST-40 in the first place. There are reports of devices doing things like this when they're unhappy with the contents of some of the flags of the initial PPR message. A work around for a Quantum Atlas with this issue went into 2.6.18 ... which kernel was this you were using? James - 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
