Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <mkp@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org,  Alexey Charkov <alchark@flipper.net>
Subject: Re: [PATCH 0/5] Recover from persistent UNIT ATTENTION conditions
Date: Wed, 04 Nov 2026 22:36:02 -0500	[thread overview]
Message-ID: <yq1ecd0ymqc.fsf@mail.kernel.org> (raw)
In-Reply-To: <cover.1793400000.git.bvanassche@acm.org>


Bart,

> Some SCSI targets do not clear a power-on or reset UNIT ATTENTION
> condition for all commands. BIWIN BWU2A05* UFS devices, for example,
> keep reporting UNIT ATTENTION for WRITE commands while TEST UNIT
> READY, READ and SYNCHRONIZE CACHE clear the condition.

Applied to 7.5/scsi-staging, thanks!

-- 
Martin K. Petersen

      parent reply	other threads:[~2026-11-05  3:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 22:42 [PATCH 0/5] Recover from persistent UNIT ATTENTION conditions Bart Van Assche
2026-10-30 22:42 ` [PATCH 1/5] scsi: core: Introduce scsi_cmd_needs_stu() Bart Van Assche
2026-10-30 22:42 ` [PATCH 2/5] scsi: core: Simplify scsi_eh_ready_devs() Bart Van Assche
2026-10-30 22:42 ` [PATCH 3/5] scsi: core: Clear UNIT ATTENTION conditions with TEST UNIT READY Bart Van Assche
2026-10-30 22:42 ` [PATCH 4/5] scsi: core: Escalate persistent UNIT ATTENTION conditions Bart Van Assche
2026-11-02 12:06   ` Alexey Charkov
2026-10-30 22:42 ` [PATCH 5/5] scsi: core: Limit retries of commands that receive UNIT ATTENTION Bart Van Assche
2026-11-02 12:06   ` Alexey Charkov
2026-11-02 12:05 ` [PATCH 0/5] Recover from persistent UNIT ATTENTION conditions Alexey Charkov
2026-11-05  3:36 ` Martin K. Petersen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yq1ecd0ymqc.fsf@mail.kernel.org \
    --to=mkp@kernel.org \
    --cc=alchark@flipper.net \
    --cc=bvanassche@acm.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox