Bug 1543493 - Agressive Link Power Management doesn't work on HP Elitebook 2540p [NEEDINFO]
Summary: Agressive Link Power Management doesn't work on HP Elitebook 2540p
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 27
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-08 15:04 UTC by Clemens Eisserer
Modified: 2018-08-29 15:24 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-29 15:24:55 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
dmesg messages (65.06 KB, text/plain)
2018-02-08 15:04 UTC, Clemens Eisserer
no flags Details

Description Clemens Eisserer 2018-02-08 15:04:21 UTC
Created attachment 1393210 [details]
dmesg messages

Description of problem:

An update shipped at the beginning of february causes servere SATA problems with my Elitebook-2540p when the system is running on battery. When plugged in everything works fine, as does the SSD when I use it with my desktop computer.

Kernel does not seem to be the culprit (4.14.14 shows the same issue with updated userland, although it worked fine before), so I guess something related to power management has changed.

Comment 1 Clemens Eisserer 2018-02-08 20:23:09 UTC
My guess is this is related to Agressive Link Power Management:

* When I start the laptop with wall power it works fine and stable
* When I select IDE instead of AHCI in BIOS it also works fine

My guess is ALPM was accidently enabled by some F27 update (during its stable period). I thought ALPM was queued for Fedora 28?

Comment 2 Clemens Eisserer 2018-02-12 19:35:14 UTC
Follow-Up:

Hans de Goede helped me in the mailing list about this issue:
I had accidently installed tlp (thinking it was only a command-line-utility), which was actually including a daemon setting the SATA power saving strategy dynamically.

The the bug-report is actually a kernel bug with ALPM not working properly on my hardware configuration.

Comment 3 Hans de Goede 2018-02-14 13:05:59 UTC
Hi Clemens,

The min_power setting which TLP selects is known to not be liked by various SSDs, I've been working on a new med_power_with_dipm setting which gives about the same power-savings and should be liked better by most SSDs.

This setting is available in the 4.15 kernel, for testing this please install this kernel: https://koji.fedoraproject.org/koji/buildinfo?buildID=1044175

Download the kernel-core-4...x86_64.rpm and kernel-modules-4...x86_64.rpm files there into a dir, then from this dir run:

sudo rpm -ivh kernel*.x86_64.rpm

And then reboot into the new kernel, now do (as root):

for i in /sys/class/scsi_host/host*/link_power_management_policy; do
    echo med_power_with_dipm > $i
done

And then to check this worked do "cat /sys/class/scsi_host/host0/link_power_management_policy" this should return "med_power_with_dipm" now.

Then use the laptop as normal and see if things work normally this way. Note the latest version of TLP will automatically use "med_power_with_dipm" instead of min_power on kernels which support this and "med_power_with_dipm" will be the default setting for laptops in Fedora 28.

Regards,

Hans


Note to self / for future reference the SSD in this laptop is a:
[    1.566363] ata2.00: ATA-8: OCZ-OCTANE, 1.14.1, max UDMA/133

Comment 4 Justin M. Forbes 2018-07-23 15:35:14 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28.

If you experience different issues, please open a new bug report for those.

Comment 5 Justin M. Forbes 2018-08-29 15:24:55 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.