Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: raoxu <raoxu@uniontech.com>
Cc: cassel@kernel.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ata: libata-pmp: add JMicron JMS562 quirk
Date: Wed, 10 Jun 2026 17:09:34 +0800	[thread overview]
Message-ID: <6a5f24b3-4777-4ed6-bcaa-a65740046ae6@kernel.org> (raw)
In-Reply-To: <71B4D0BBEC4F886F+20260610052835.1111181-1-raoxu@uniontech.com>

On 2026/06/10 13:28, raoxu wrote:
> From: Xu Rao <raoxu@uniontech.com>
> 
> JMicron JMS562, as used in QNAP QDA-A2AR RAID1 adapters, may
> keep the exported ATA device not ready while the array is rebuilding.
> 
> In this state, libata may repeatedly try to softreset and classify
> the fan-out link.  On the affected adapter, this can time out, make
> PMP/SCR access fail, and eventually disable the fan-out link before
> the RAID volume is exported.
> 
> A failing boot shows the fan-out link failing SRST, PMP access
> timing out, SCR read failing, and the link being disabled:
> 
>   ata4.00: softreset failed (device not ready)
>   ata4.15: qc timeout after 3000 msecs (cmd 0xe4)
>   ata4.00: failed to read SCR 0 (Emask=0x4)
>   ata4.00: failed to recover link after 3 tries, disabling
> 
> After that, the root filesystem on the exported RAID volume cannot
> be found.
> 
> Add JMS562 to the existing JMicron PMP quirk that disables LPM,
> avoids softreset on fan-out links, and assumes an ATA device.  This
> prevents libata from dropping the exported RAID volume during rebuild
> recovery.
> 
> Signed-off-by: Xu Rao <raoxu@uniontech.com>

It is really unfortunate that JMicron keeps having these issues. But I do not
see any way around this, so:

Reviewed-by: Damien Le Moal <dlemoal@kernel.org>


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2026-06-10  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  5:28 [PATCH v2] ata: libata-pmp: add JMicron JMS562 quirk raoxu
2026-06-10  9:09 ` Damien Le Moal [this message]
2026-06-10  9:47   ` Niklas Cassel
2026-06-10  9:40 ` Niklas Cassel

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=6a5f24b3-4777-4ed6-bcaa-a65740046ae6@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=cassel@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raoxu@uniontech.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