Re: [PATCH] ata: libata-sata: retry hardreset when device detected but PHY not established
From: Niklas Cassel
Date: Thu May 28 2026 - 03:14:24 EST
Hello Xingui,
On Thu, May 28, 2026 at 03:01:39PM +0800, yangxingui wrote:
>
> Latest update: The issue we are currently facing is that the SATA host side
> is continuously waiting for the disk to return the COMWAKE primitive. From
> the SATA analyzer, it can be seen that the disk has already returned the
> COMWAKE primitive. This may be related to poor COMWAKE signal quality,
> causing the host to fail to recognize it. Performing a hard reset might be
> able to fix the issue.
I'm a little confused. In your previous update you said that the issue had
been resolved.
Now you say that an additional hard reset (COMRESET) "might be able" to
fix the issue.
That does not sound like you have actually verified if it does so or not.
Perhaps you can try implementing my suggestion in:
https://lore.kernel.org/linux-ide/afMgoFBFPWR0f4gK@ryzen/
which does an additional hard reset (COMRESET).
But please only send out a patch if you have actually verified that the
suggestion actually resolves your issue.
Kind regards,
Niklas