summaryrefslogtreecommitdiffstats
path: root/Documentation/ABI/testing/sysfs-driver-ufs
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk@kernel.org>2021-01-07 10:53:16 -0800
committerMartin K. Petersen <martin.petersen@oracle.com>2021-01-07 22:50:48 -0500
commiteeb1b55b6e25c5f7265ff45cd050f3bc2cc423a4 (patch)
tree264cb1108f8bf735797d088c155b002ef00ba591 /Documentation/ABI/testing/sysfs-driver-ufs
parent4ee7ee530bc2bae6268247988d86722c65d02a37 (diff)
downloadlinux-stable-eeb1b55b6e25c5f7265ff45cd050f3bc2cc423a4.tar.gz
linux-stable-eeb1b55b6e25c5f7265ff45cd050f3bc2cc423a4.tar.bz2
linux-stable-eeb1b55b6e25c5f7265ff45cd050f3bc2cc423a4.zip
scsi: ufs: Fix tm request when non-fatal error happens
When non-fatal error like line-reset happens, ufshcd_err_handler() starts to abort tasks by ufshcd_try_to_abort_task(). When it tries to issue a task management request, we hit two warnings: WARNING: CPU: 7 PID: 7 at block/blk-core.c:630 blk_get_request+0x68/0x70 WARNING: CPU: 4 PID: 157 at block/blk-mq-tag.c:82 blk_mq_get_tag+0x438/0x46c After fixing the above warnings we hit another tm_cmd timeout which may be caused by unstable controller state: __ufshcd_issue_tm_cmd: task management cmd 0x80 timed-out Then, ufshcd_err_handler() enters full reset, and kernel gets stuck. It turned out ufshcd_print_trs() printed too many messages on console which requires CPU locks. Likewise hba->silence_err_logs, we need to avoid too verbose messages. This is actually not an error case. Link: https://lore.kernel.org/r/20210107185316.788815-3-jaegeuk@kernel.org Fixes: 69a6c269c097 ("scsi: ufs: Use blk_{get,put}_request() to allocate and free TMFs") Reviewed-by: Can Guo <cang@codeaurora.org> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'Documentation/ABI/testing/sysfs-driver-ufs')
0 files changed, 0 insertions, 0 deletions