All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	Ioannis Barkas <jnyb.de@gmail.com>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH v4] ata: libata: disable LPM for WDC WD20EFAX-68FB5N0 hard drives
Date: Wed, 7 May 2025 10:59:13 +0200	[thread overview]
Message-ID: <aBsg4aKYK3lfGASx@ryzen> (raw)
In-Reply-To: <CAAZ0mTctoC5UCsDVH56x5OS_500URheBU66USNuq+rwktLrEiw@mail.gmail.com>

On Mon, May 05, 2025 at 08:09:44PM +0300, Mikko Juhani Korhonen wrote:
> ma 5.5.2025 klo 18.37 Niklas Cassel (cassel@kernel.org) kirjoitti:
> 
> > 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.
> > > 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
> > 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"
> 
> mjkorhon@taavi:~$ sudo lspci -nn | grep -E "SATA|AHCI"
> 01:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 500
> Series Chipset SATA Controller [1022:43eb]


Hello Mario,

We are seeing some LPM issues with an AMD AHCI controller when using a
(fairly recent) WD drive (so I would be slightly surprised if LPM wasn't)
implemented correctly.

The AMD AHCI controller is however something that I haven't seen before:
AMD 500 Series Chipset SATA Controller [1022:43eb]

For AMD, I have mostly seen:

PCI_VDEVICE(AMD, 0x7800)
PCI_VDEVICE(AMD, 0x7801)
PCI_VDEVICE(AMD, 0x7900)
PCI_VDEVICE(AMD, 0x7901)


I have never seen any 0x43eb before.
Is this AHCI chip less common than the others?


We did add a quirk that disables LPM (when used with Samsung drives) for
ATI AHCI controllers recently:
https://lore.kernel.org/linux-ide/20250317170348.1748671-2-cassel@kernel.org/


Could perhaps this 0x43eb be a rebranded ATI AHCI controller?


If we had LPM problems with AMD 0x78XX/0x79XX AHCI controllers,
I'm quite sure that we would have seen way more bug reports by now.


Kind regards,
Niklas

  parent reply	other threads:[~2025-05-07  8: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
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 [this message]
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=aBsg4aKYK3lfGASx@ryzen \
    --to=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=jnyb.de@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mario.limonciello@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.