Handling Expected-data-transfer-legnth and CDB transfer-len mismatch
"Qi, Yanling" <[email protected]> Mon, 14 May 2007 15:29:43 -0600
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <[email protected]> |
Hi All, We saw an initiator problem where the expected-data-transfer-length and transfer-len inside CDB got mismatched for a write-and-verify (10). The expected-data-transfer-length is 0x4000 but the transfer-len in the CDB is 0. The target completed the request with good status, turned Residual-underflow bit on and set residual-count=0x4000. See frames 16 and 38 in the attached ethereal trace file for details. Did the target handle this error condition correctly? Thanks, --yanling Yanling Qi Engenio Storage Group - LSI Logic 512-794-3713 (Office) 512-794-3702 (Fax) [email protected] _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips
expectedDataLength-transfer-len.pcap
(application/octet-stream, 33.9 KB) - not displayed