On Wed, 2014-05-21 at 15:23 -0700, Jun Wu wrote:
> > 18630751 May 21 11:01:53 poc2 kernel: [ 1528.191740] host7: xid
> 6e4:
> > Exchange timer armed : 0 msecs
> > 18630752 May 21 11:01:53 poc2 kernel: [ 1528.191747] host7: xid
> 6e4:
> > f_ctl 800000 seq 1
> > 18630753 May 21 11:01:53 poc2 kernel: [ 1528.191756] host7: xid
> 6e4:
> > f_ctl 800000 seq 2
> > 18630754 May 21 11:01:53 poc2 kernel: [ 1528.191763] host7: xid
> 6e4:
> > Exchange timed out
> > 18630755 May 21 11:01:53 poc2 kernel: [ 1528.191777]
> ft_queue_data_in:
> > Failed to send frame ffff8805bf245e00, xid <0x6e4>, remaining
> 458752,
> > lso_max <0x10000>
Exchange 0x6e4 is aborted and then target still sending frame, while
later should not occur but first setting up abort with 0 msec timeout
doesn not look correct either and it is different that 8000 ms on
initiator side. Are you using same switch between initiator and target
with DCB enabled ?
Reducing retries could narrow down to early aborts is the cause here,
can you try with REC disabled on initiator side for that using this
change ?
diff --git a/drivers/scsi/libfc/fc_fcp.c b/drivers/scsi/libfc/fc_fcp.c
index 1d7e76e..43fe793 100644
--- a/drivers/scsi/libfc/fc_fcp.c
+++ b/drivers/scsi/libfc/fc_fcp.c
@@ -1160,6 +1160,7 @@ static int fc_fcp_cmd_send(struct fc_lport *lport,
struct fc_fcp_pkt *fsp,
fc_fcp_pkt_hold(fsp); /* hold for fc_fcp_pkt_destroy */
setup_timer(&fsp->timer, fc_fcp_timeout, (unsigned long)fsp);
+ rpriv->flags &= ~FC_RP_FLAGS_REC_SUPPORTED;
if (rpriv->flags & FC_RP_FLAGS_REC_SUPPORTED)
fc_fcp_timer_set(fsp, get_fsp_rec_tov(fsp));
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
