I realize this is in an old thread but I noticed the same message after updating kernel from 6.12.41 to 6.12.53.
After a reboot, I now read (for all disks plugged to the mb sata ports)
Code: Select all
[ 9.582513] ata5.00: LPM support broken, forcing max_power
[ 9.583968] ata3.00: LPM support broken, forcing max_power
[ 9.584224] ata4.00: LPM support broken, forcing max_power
[ 9.584271] ata1.00: LPM support broken, forcing max_power
[ 9.587018] ata3.00: LPM support broken, forcing max_power
[ 9.598848] ata4.00: LPM support broken, forcing max_power
[ 9.599582] ata1.00: LPM support broken, forcing max_power
[ 9.606960] ata5.00: LPM support broken, forcing max_power
If I reboot to 6.12.41, it doesn't show up. Maybe I could try a cold boot later to see if there is a difference or not.
----
edit:
Same after a cold boot with 6.12.53 : "LPM support broken, forcing max_power"
Otherwise, I found out that it affects this specific motherboard only (amd chipset)
because with an other (old) motherboard (intel) & kernel 6.12.53 too, I don't have this message for sata disks.
----
https://www.kernel.org/doc/html/latest/ ... olicy.html
I don't know if I should worry about it or not.
I guess not since I don't use any power saving for my ssd/hdd anyway.
edit:
added in 6.12.43:
Code: Select all
commit f170bc6fa429438b7eaee43a797b237b06fd1a1d (HEAD)
ata: libata-sata: Add link_power_management_supported sysfs attribute
commit 0060beec0bfa647c4b510df188b1c4673a197839 upstream.
A port link power management (LPM) policy can be controlled using the
link_power_management_policy sysfs host attribute. However, this
attribute exists also for hosts that do not support LPM and in such
case, attempting to change the LPM policy for the host (port) will fail
with -EOPNOTSUPP.
Introduce the new sysfs link_power_management_supported host attribute
to indicate to the user if a the port and the devices connected to the
port for the host support LPM, which implies that the
link_power_management_policy attribute can be used.
Since checking that a port and its devices support LPM is common between
the new ata_scsi_lpm_supported_show() function and the existing
ata_scsi_lpm_store() function, the new helper ata_scsi_lpm_supported()
is introduced.
and:
Code: Select all
commit aa078896e33125708b1a9ed947be96570937a862
ata: ahci: Disallow LPM policy control if not supported
[ Upstream commit 65b2c92f69d3df81422d27e5be012e357e733241 ]
Commit fa997b0576c9 ("ata: ahci: Do not enable LPM if no LPM states are
supported by the HBA") introduced an early return in
ahci_update_initial_lpm_policy() to ensure that the target_lpm_policy
of ports belonging to a host that does not support the Partial, Slumber
and DevSleep power states is unchanged and remains set to
ATA_LPM_UNKNOWN and thus prevents the execution of
ata_eh_link_set_lpm().
However, a user or a system daemon (e.g. systemd-udevd) may still
attempt changing the LPM policy through the sysfs
link_power_management_policy of the host.
Improve this to prevent sysfs LPM policy changes by setting the flag
ATA_FLAG_NO_LPM for the port of such host, and initialize the port
target_lpm_policy to ATA_LPM_MAX_POWER to guarantee that no unsupported
low power state is being used on the port and its link.
