| Summary: | powertop systemd-service hsould be restarted after suspend | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marc Krämer <mageia> |
| Component: | RPM Packages | Assignee: | José Jorge <lists.jjorge> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | powertop-2.9-5.mga6.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Marc Krämer
2018-08-11 13:32:57 CEST
Marc Krämer
2018-08-11 13:33:47 CEST
Assignee:
bugsquad =>
lists.jjorge Thanks for reporting, but I think you are wrong : this tunes only kernel-parameters that are kept after both suspend and hibernate. I have just ensured in my system : - display TUNABLES in powertop : all are GOOD - suspend / awake - display TUNABLES in powertop : all are GOOD - hibernate / poweron - display TUNABLES in powertop : all are GOOD Feel free to reopen if you have further information. Resolution:
(none) =>
INVALID Hi José, here on my thinkpad many tunables are in bad shape after resume. Before suspend I checked all values and tuneables are all good. The using suspend (via lxde) and resuming via powerkey tuneables for ~20 devices are bad. Did you check your values are in bad shape before using powertop? Resolution:
INVALID =>
(none) I think this can be done via systemd-sleep target. (In reply to Marc Krämer from comment #2) > Hi José, > Did you check your values are in bad shape before using powertop? Yes. Maybe you have something interesting in your hardware. Feel free to contribute a trigger for systemd-sleep, but it should be ignored by default as most hardware does not have this problem and powertop is huge in RAM. No activity in months, closing. Feel free to reopen if needed. Resolution:
(none) =>
FIXED |