diff options
author | James Smart <jsmart2021@gmail.com> | 2017-04-21 16:04:46 -0700 |
---|---|---|
committer | Christoph Hellwig <hch@lst.de> | 2017-04-24 09:25:48 +0200 |
commit | 975ff31c77348c567b4c12418d456446c50006dd (patch) | |
tree | 89658e15797c54d283486782422fd35a75cca2f6 /arch/m32r/lib/delay.c | |
parent | a44e4e8b6bf22926be6ed63f99def5e62953ac08 (diff) |
Fix nvme unregister port timeout.
During some link event testing it was observed that the
wait_for_completion_timeout in the lpfc_nvme_unregister_port
was timing out all the time.
The initiator is claiming the nvme_fc_unregister_remoteport upcall is
not completing the unregister in the time allotted.
[ 2186.151317] lpfc 0000:07:00.0: 0:(0):6169 Unreg nvme wait failed 0
The wait_for_completion_timeout returns 0 when the wait has
been outstanding for the jiffies passed by the caller. In this error
message, the nvme initiator passed value 5 - meaning 5 jiffies -
and this is just wrong.
Calculate 5 seconds in Jiffies and pass that value
from the current jiffies.
Also the log message for the unregister timeout was reduced
because timeout failure is the same as timeout.
Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
Signed-off-by: James Smart <james.smart@broadcom.com>
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Diffstat (limited to 'arch/m32r/lib/delay.c')
0 files changed, 0 insertions, 0 deletions