From: Niklas Cassel <cassel@kernel.org>
To: Mikko Juhani Korhonen <mjkorhon@gmail.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
Ioannis Barkas <jnyb.de@gmail.com>,
linux-ide@vger.kernel.org, Niklas Cassel <Niklas.Cassel@wdc.com>
Subject: Re: [PATCH v4] ata: libata: disable LPM for WDC WD20EFAX-68FB5N0 hard drives
Date: Mon, 5 May 2025 17:37:46 +0200 [thread overview]
Message-ID: <aBjbSt5hTaUP_JhG@ryzen> (raw)
In-Reply-To: <CAAZ0mTeepp7G9CtLFq+U_n0h2+SF8V8j2K=0hkNAp0Fzdc7TAQ@mail.gmail.com>
Hello Mikko,
On Mon, May 05, 2025 at 10:58:22AM +0300, Mikko Juhani Korhonen wrote:
> > > On 5/1/25 05:36, Ioannis Barkas wrote:
> > >> It would be better to have more details on this since only the 2TB
> > >> model is targeted.
>
> Hello guys,
> first of all thanks for helping me with git format-patch, I should
> have read instructions about not using gmail text mode. The last patch
> I sent (or not can't remember for sure) was a dot matrix printer
> driver for something like 1.1.95 :)
>
> I have two WD20EFAX-68FB5N0 and both behave consistently, unusable
> from 6.9.0 on as they just keep resetting the SATA link , but they
> have worked flawlessly with 6.8.x for a year and also now with the
> quirk applied.
>
> I have also tested a different WDC model with med_power_with_dipm on
> the same SATA port and there are no problems.
>
> But after you guys got suspicious I found there is in fact a SATA port
> on my motherboard where the WD20EFAX-68FB5N0 works with LPM on. So I
> guess it's entirely possible that this is after all some kind of
> interoperating issue between a certain SATA port of a ASUS B550 F
> Gaming WiFi and the WDC, either unique to my items or in a larger
> production batch.
This motherboard looks to be AMD chipset, so I assume AMD AHCI controller.
Could you send the output of:
$ lspci -nn | grep -E "SATA|AHCI"
From your logs, it looks like you have a single AHCI controller,
so it is very surprising if LPM works by simply moving the drive to
another port (on the same controller).
Sure, AHCI does allow supporting DevSleep only on certain ports,
but AFAICT all other LPM supported bits are in the CAP register,
which is the same for all ports.
But
1) If there was a port that didn't support it, we would have seen
a "port does not support device sleep" print.
2) The prints from dmesg shows lpm-pol 3, so DevSleep is not enabled.
So the settings should be the same for all ports.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-05-05 15:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 20:36 [PATCH v4] ata: libata: disable LPM for WDC WD20EFAX-68FB5N0 hard drives Ioannis Barkas
2025-05-01 18:47 ` Damien Le Moal
2025-05-02 1:32 ` Damien Le Moal
2025-05-05 7:58 ` Mikko Juhani Korhonen
2025-05-05 15:37 ` Niklas Cassel [this message]
2025-05-05 17:09 ` Mikko Juhani Korhonen
2025-05-07 8:55 ` Damien Le Moal
2025-05-10 10:14 ` Mikko Juhani Korhonen
2025-05-10 11:59 ` Niklas Cassel
2025-05-10 18:29 ` Ioannis Barkas
2025-05-11 17:08 ` Mikko Juhani Korhonen
2025-05-11 18:53 ` Niklas Cassel
2025-05-11 18:59 ` Mikko Juhani Korhonen
2025-05-11 19:18 ` Niklas Cassel
2025-05-11 20:40 ` Mikko Juhani Korhonen
2025-05-12 5:37 ` Mikko Juhani Korhonen
2025-05-12 9:25 ` Niklas Cassel
2025-05-12 10:34 ` Mikko Juhani Korhonen
2025-05-12 11:20 ` Niklas Cassel
[not found] ` <CAAZ0mTeiVqZQvkWzJ8aFH4FUPCZwy5O+9hPBgDPhSgNNz+t6HA@mail.gmail.com>
2025-05-14 17:57 ` Niklas Cassel
2025-05-17 16:31 ` Mikko Juhani Korhonen
[not found] ` <CAAZ0mTdZEd6n+tDvqbqzMQS2W+3efpYOeHupYcj3rDSVeuHFBA@mail.gmail.com>
2025-05-23 14:05 ` Niklas Cassel
2025-06-02 11:17 ` Mikko Juhani Korhonen
2025-06-05 12:18 ` Niklas Cassel
2025-06-09 13:49 ` Niklas Cassel
2025-06-11 13:14 ` Mikko Juhani Korhonen
2025-06-11 13:33 ` Niklas Cassel
2025-05-07 8:59 ` Niklas Cassel
2025-05-08 19:24 ` Mario Limonciello
2025-05-07 8:59 ` Damien Le Moal
2025-05-11 18:55 ` Mikko Juhani Korhonen
-- strict thread matches above, loose matches on Subject: below --
2025-05-05 19:38 Ioannis Barkas
2025-05-05 23:33 ` Damien Le Moal
2025-05-06 11:29 ` Mikko Juhani Korhonen
2025-04-29 16:44 Mikko Korhonen
2025-04-30 6:35 ` 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=aBjbSt5hTaUP_JhG@ryzen \
--to=cassel@kernel.org \
--cc=Niklas.Cassel@wdc.com \
--cc=dlemoal@kernel.org \
--cc=jnyb.de@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mjkorhon@gmail.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