Linux ATA/IDE development
 help / color / mirror / Atom feed
From: yangxingui <yangxingui@huawei.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	<linux-kernel@vger.kernel.org>, <liuyonglong@huawei.com>,
	<kangfenglong@huawei.com>, <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ata: libata-sata: retry hardreset when device detected but PHY not established
Date: Wed, 6 May 2026 10:23:13 +0800	[thread overview]
Message-ID: <a6bd2366-dbea-f82b-92b5-fd038c3a768d@huawei.com> (raw)
In-Reply-To: <afMgoFBFPWR0f4gK@ryzen>



On 2026/4/30 17:28, Niklas Cassel wrote:
> On Thu, Apr 30, 2026 at 10:46:22AM +0200, Niklas Cassel wrote:
>> If that is the case ata_do_reset() would return 0, and
>> ata_eh_followup_srst_needed() (returns true only if -EAGAIN) would return false.
>>
>> Which should eventually cause us to retry another hard reset, as long as
>> tries <= max_tries.
> 
> I see now that max_tries is just set to 1.
> 
> I think I would prefer another hardreset (with a larger timeout) over
> a follow-up softreset after the hardreset...
> 
> If -EAGAIN is reserved for "do an follow up SRST after the COMRESET",
> because certain Port Multipliers need it.
> 
> Perhaps introduce another error code, which means, device detected,
> overload max_tries to 3 and goto retry.
> 
> That way we will retry using COMRESET, with increasing timeouts, since:
> deadline = ata_deadline(jiffies, ata_eh_reset_timeouts[try++]);
> 
Increasing the deadline of the debound does not solve the problem. 
Additionally, we do not have a customer environment locally, so we are 
not sure whether retry a hardreset can completely resolve the issue. 
However, in this scenario, the SATA hard disk manufacturer has added a 
mechanism to attempt to proactively trigger COMINIT for re-establishing 
the link after an abnormal link establishment. Feedback from pressure 
testing indicates that the issue has been resolved. ^-^

Thanks,
Xingui
.

      reply	other threads:[~2026-05-06  2:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260425060447.1312763-1-yangxingui@huawei.com>
     [not found] ` <e8d237bc-7191-4881-924b-86a34ff0f3b9@kernel.org>
2026-04-27  1:51   ` [PATCH] ata: libata-sata: retry hardreset when device detected but PHY not established yangxingui
2026-04-27  4:45     ` Damien Le Moal
2026-04-29  1:14       ` yangxingui
2026-04-29  1:36         ` Damien Le Moal
2026-04-29  7:01           ` yangxingui
2026-04-30  8:46             ` Niklas Cassel
2026-04-30  9:28               ` Niklas Cassel
2026-05-06  2:23                 ` yangxingui [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=a6bd2366-dbea-f82b-92b5-fd038c3a768d@huawei.com \
    --to=yangxingui@huawei.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=kangfenglong@huawei.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuyonglong@huawei.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