From: Niklas Cassel <cassel@kernel.org>
To: wolf@yoxt.cc
Cc: linux-ide@vger.kernel.org, dlemoal@kernel.org, tj@kernel.org
Subject: Re: [REGRESSION] libata: SATA LPM forcibly disabled on Intel Raptor Lake since Linux 6.14.
Date: Wed, 7 Jan 2026 11:14:29 +0100 [thread overview]
Message-ID: <aV4yBZkxVD2Olg3X@ryzen> (raw)
In-Reply-To: <605b34a7723436284699c9a8e524907b@yoxt.cc>
On Tue, Jan 06, 2026 at 08:57:07PM +0100, wolf@yoxt.cc wrote:
> Hello,
>
> I am reporting a power-management regression in libata affecting the Intel
> Raptor Lake SATA AHCI Controller, introduced after Linux 6.14.
(snip)
> and 4 apparent dummy ports might be unexpected?
>
> Manually setting LPM on the affected hosts fails with:
> echo med_power_with_dipm >
> /sys/class/scsi_host/host*/link_power_management_policy
> -bash: echo: write error: Operation not supported
This is most likely because your ports are marked as External / Hotplug
capable by BIOS.
LPM and Hotplug are mutually exlusive in SATA.
So in order allow your ports to detect a hotplug event, LPM cannot be
disabled.
Things you can do:
-Go into your BIOS settings and disable the hot-plugging capability for the
ports.
-If you don't have such a setting, you can use the mask_port_ext AHCI module
parameter. Simply add:
ahci.mask_port_ext=<your portmask here> to your kernel command line
For more info, see this thread:
https://lore.kernel.org/linux-ide/5a74106a-d9db-4e63-b3e6-3857f30a1190@interia.pl/T/
Kind regards,
Niklas
next prev parent reply other threads:[~2026-01-07 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 19:57 [REGRESSION] libata: SATA LPM forcibly disabled on Intel Raptor Lake since Linux 6.14 wolf
2026-01-07 10:14 ` Niklas Cassel [this message]
2026-01-07 10:19 ` Damien Le Moal
[not found] ` <70a55b1ecd97f30795879994a07764bc@yoxt.cc>
2026-01-07 10:38 ` Damien Le Moal
2026-01-07 11:20 ` Niklas Cassel
2026-01-07 15:16 ` Damien Le Moal
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=aV4yBZkxVD2Olg3X@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.org \
--cc=wolf@yoxt.cc \
/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