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: Sat, 10 May 2025 13:59:40 +0200 [thread overview]
Message-ID: <aB8_rITWsMzkTiyE@ryzen> (raw)
In-Reply-To: <CAAZ0mTf3T5RTDKtd148GyGOiVz98isFFbMDXfku8yAk9FfLVeQ@mail.gmail.com>
On Sat, May 10, 2025 at 01:14:52PM +0300, Mikko Juhani Korhonen wrote:
> ke 7.5.2025 klo 11.56 Damien Le Moal (dlemoal@kernel.org) kirjoitti:
> > >>>>> On 5/1/25 05:36, Ioannis Barkas wrote:
> > >>> 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
> > Can you share a dmesg output for the good case with 6.8.x kernel ?
> > We would like to see differences with the non-working case.
>
> Hello Damien,
> here is the dmesg from good 6.8.12. Thanks!
Hello Mikko,
In the (bad) dmesg that you shared earlier, we saw:
touko 05 09:18:59 taavi kernel: ata1: SATA max UDMA/133 abar
m131072@0xfc580000 port 0xfc580100 irq 42 lpm-pol 3
touko 05 09:18:59 taavi kernel: ata2: SATA max UDMA/133 abar
m131072@0xfc580000 port 0xfc580180 irq 42 lpm-pol 3
touko 05 09:18:59 taavi kernel: ata3: SATA max UDMA/133 abar
m131072@0xfc580000 port 0xfc580200 irq 42 lpm-pol 3
touko 05 09:18:59 taavi kernel: ata4: SATA max UDMA/133 abar
m131072@0xfc580000 port 0xfc580280 irq 42 lpm-pol 3
touko 05 09:18:59 taavi kernel: ata5: SATA max UDMA/133 abar
m131072@0xfc580000 port 0xfc580300 irq 42 lpm-pol 3
touko 05 09:18:59 taavi kernel: ata6: SATA max UDMA/133 abar
m131072@0xfc580000 port 0xfc580380 irq 42 lpm-pol 3
In this new (good) dmesg we see:
[ 1.839502] ata1: SATA max UDMA/133 abar m131072@0xfc580000 port
0xfc580100 irq 42 lpm-pol 0
[ 1.840186] ata2: SATA max UDMA/133 abar m131072@0xfc580000 port
0xfc580180 irq 42 lpm-pol 0
[ 1.840859] ata3: SATA max UDMA/133 abar m131072@0xfc580000 port
0xfc580200 irq 42 lpm-pol 0
[ 1.841516] ata4: SATA max UDMA/133 abar m131072@0xfc580000 port
0xfc580280 irq 42 lpm-pol 0
[ 1.842166] ata5: SATA max UDMA/133 abar m131072@0xfc580000 port
0xfc580300 irq 42 lpm-pol 0
[ 1.842804] ata6: SATA max UDMA/133 abar m131072@0xfc580000 port
0xfc580380 irq 42 lpm-pol 0
lpm-pol 0 means "keep firmware settings".
That we see a difference suggests that the value of the Kconfig
CONFIG_SATA_MOBILE_LPM_POLICY
of these two kernel builds are not the same.
Could you double check this?
It is theoretically possible that both kernels were built with the same
Kconfig value. If your BIOS marks a port as external / hotplug capable,
then libata will force set lpm-pol to 0 (overriding the Kconfig value).
However, if you haven't changed any BIOS settings between booting your
two different kernels, then this second scenario sounds very unlikely.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-05-10 11:59 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
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 [this message]
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=aB8_rITWsMzkTiyE@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;
as well as URLs for NNTP newsgroup(s).