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, Hans de Goede <hansg@kernel.org>
Subject: Re: [PATCH v4] ata: libata: disable LPM for WDC WD20EFAX-68FB5N0 hard drives
Date: Wed, 11 Jun 2025 15:33:46 +0200 [thread overview]
Message-ID: <aEmFuqA5kNhMD41Z@ryzen> (raw)
In-Reply-To: <CAAZ0mTdBgeedcF3gE6bKm=+qFj8Sfuc0xVc-kDb2=nhMS3F_3Q@mail.gmail.com>
On Wed, Jun 11, 2025 at 04:14:44PM +0300, Mikko Juhani Korhonen wrote:
> ma 9.6.2025 klo 16.49 Niklas Cassel (cassel@kernel.org) kirjoitti:
> > > It is unfortunate that the BIOS manufacturer has managed to mess this up,
> > > but since this is the first motherboard where I've heard about the problem
> > > of LPM only working on certain ports, even though it is a per controller
> > > thing, just not having good power saving for this motherboard seems fine.
> > >
> > > I suggest that we simply add the DMI name of your motherboard to
> > > ahci_broken_lpm().
> >
> > (As without that series, it is not possible to add an entry
> > where there is no good BIOS version that has been released.)
>
> Hello Niklas,
>
> thanks - ok we are assuming that this is something that happens only
> on this motherboard for this AMD 0x43EB controller at least for now.
From what AMD people told us, this controller is not the same as the ancient
ATI based AHCI controller that had a bunch of problems with LPM.
Also, LPM works on some ports, but not others. That suggests that the AHCI
controller actually supports LPM and that this is a BIOS / integration issue.
> Was your thought also that we restrict disabling lpm only up to the
> current BIOS version, and if there are BIOS updates which don't fix
> the issue we just bump version number here?
The table in ahci_broken_lpm() previously included BIOS versions that were
good. (There has been a new version released that has fixed the LPM problem
that existed in older BIOSes.)
I recently added the "ASUSPRO D840MB_M840SA", which does not have any good
version.
I was thinking that they probably won't release any new BIOS versions for
"ASUSPRO D840MB_M840SA" and your motherboard, so most likely we will never
need to bump these. But perhaps that is a silly assumption.
Perhaps a better solution would have been to have two tables?
One table that looks like before. (Anything older than the "good" version
gets LPM disabled.) And then a new table for boards that we quirk
unconditionally (because there is no new version that fixes the LPM problems).
Because like you say, perhaps the manufacturer will release a new BIOS with
simply a small hotfix, and will thus have a newer build date, but will still
have broken LPM.
Perhaps I should throw out some of the commits from for-6.16-fixes, and
implement it using two tables instead.
(Commit 6f29d393061c ("ata: ahci: Use correct BIOS build date for ThinkPad
W541 quirk") can still be kept.)
> And I guess there are not going to be any firmware updates to the WDC
> WD20EFAX-68FB5N0 drive, I understood that you or Damien might know
> something about this? This would of course not help if the problem is
> in the motherboard.
I don't think this drive will get any new FW.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-06-11 13:33 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
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 [this message]
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=aEmFuqA5kNhMD41Z@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hansg@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