From: Damien Le Moal <dlemoal@kernel.org>
To: Dieter Mummenschanz <dmummenschanz@web.de>,
linux-ide@vger.kernel.org, Niklas Cassel <cassel@kernel.org>
Subject: Re: Aw: Re: Re: [PATCH 0/2] Power management fixes
Date: Wed, 31 Jan 2024 16:38:28 +0900 [thread overview]
Message-ID: <3f7cef2a-5ba4-465b-a1f5-77e2bcc50ddb@kernel.org> (raw)
In-Reply-To: <trinity-0df92d73-be55-433c-bdb2-4387f7ea590b-1706686178879@3c-app-webde-bap43>
On 1/31/24 16:29, Dieter Mummenschanz wrote:
> Damien,
> so I've applied the patch to 6.8-rc2. Interesting thing is that the behaviour is
> exactly the same as before (w/o the patch). Besides not
> honoring CONFIG_SATA_MOBILE_LPM_POLICY=3 after boot my system refuses to
> transition into lower power states > pc2 after resume even after letting it sit
> idle for 10 minutes. Transition is only reached after issuing hdparm -Y. So if
> the patch restores the original behaviour then why did it stop working?!
Interesting... hdparm -Y puts the drive to sleep while the revert puts the drive
in standby state. Sleep is a near complete shutdown of the drive, while standby
is not.
In any case, I think something else is causing this. Probably PCI or ACPI
related changes. So a bisect would be needed to understand this. But this is
going to be very painful to do for this as each test take a while I guess ? How
long do you need to wait to see the system going into low power state (when it
is working that is) ?
Also, which kernel version is the last one you know is OK ?
> dmesg:
> https://pastes.io/1vmmvhvfub
> Regards
> Dieter
> *Gesendet:* Dienstag, 23. Januar 2024 um 12:52 Uhr
> *Von:* "Damien Le Moal" <dlemoal@kernel.org>
> *An:* "Dieter Mummenschanz" <dmummenschanz@web.de>, linux-ide@vger.kernel.org
> *Betreff:* Re: Aw: Re: [PATCH 0/2] Power management fixes
> On 1/23/24 20:40, Dieter Mummenschanz wrote:
> > Damien,
> > sorry for getting back to you so late. So is this patch series just a revert or
> > is it something new? Can I patch and test against 6.8-rc or should I use 6.7?
> > Anyway I need at least a couple of days since I'm very busy ATM.
>
> Yes, the second patch is essentially a revert. If you can test with 6.8-rc1 it
> would be great.
>
> Thanks.
>
> --
> Damien Le Moal
> Western Digital Research
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-01-31 7:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 11:51 [PATCH 0/2] Power management fixes Damien Le Moal
2024-01-11 11:51 ` [PATCH 1/2] ata: libata-core: Do not try to set sleeping devices to standby Damien Le Moal
2024-02-14 11:03 ` Niklas Cassel
2024-01-11 11:51 ` [PATCH 2/2] ata: libata-core: Revert "ata: libata-core: Fix ata_pci_shutdown_one()" Damien Le Moal
2024-01-11 18:10 ` Sergei Shtylyov
2024-01-11 23:13 ` Damien Le Moal
2024-02-19 15:29 ` Niklas Cassel
2024-02-23 21:04 ` Sergey Shtylyov
2024-02-26 9:28 ` Niklas Cassel
[not found] ` <DU0P251MB082515FC8FE77424231B475CF4682@DU0P251MB0825.EURP251.PROD.OUTLOOK.COM>
2024-01-22 8:49 ` [PATCH 0/2] Power management fixes Damien Le Moal
[not found] ` <trinity-0be6e8a8-e6d3-4d60-be0d-59592a9edd65-1706010022623@3c-app-webde-bap10>
2024-01-23 11:52 ` Aw: " Damien Le Moal
[not found] ` <trinity-0df92d73-be55-433c-bdb2-4387f7ea590b-1706686178879@3c-app-webde-bap43>
2024-01-31 7:38 ` Damien Le Moal [this message]
2024-01-31 11:49 ` Aw: " Niklas Cassel
2024-01-31 12:09 ` Damien Le Moal
2024-02-01 7:12 ` Aw: " Dieter Mummenschanz
2024-02-01 8:09 ` Damien Le Moal
2024-02-01 7:10 ` Dieter Mummenschanz
2024-02-01 10:51 ` Niklas Cassel
2024-02-02 14:53 ` Aw: " Dieter Mummenschanz
2024-02-05 19:00 ` Niklas Cassel
[not found] ` <trinity-0bc8e6ea-7808-4508-af3a-be22281abf24-1707231996854@3c-app-webde-bs42>
2024-02-06 21:46 ` Niklas Cassel
2024-02-08 14:37 ` Aw: " Dieter Mummenschanz
2024-02-13 20:02 ` 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=3f7cef2a-5ba4-465b-a1f5-77e2bcc50ddb@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=dmummenschanz@web.de \
--cc=linux-ide@vger.kernel.org \
/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.