Bug 6360 - Bad power management in Mageia
Summary: Bad power management in Mageia
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-06 23:05 CEST by Ilyés Zoltán
Modified: 2013-11-23 16:16 CET (History)
2 users (show)

See Also:
Source RPM: razorqt-0.4.1-3.mga2
CVE:
Status comment:


Attachments

Description Ilyés Zoltán 2012-06-06 23:05:31 CEST
Description of problem:
I compared Arch and Mageia power management today. On both system I had razorqt running, cpu governor set to powersave and set all the tunables with powertop to good, wireless turned off from the switch. This was actually a real-life experiment cause I was on a train.

What I found is the following:
On Arch I got about 26 wakeups/sec while I was reading pdf-s with okular and 14 wakeups/sec when idle, about 16-17W discharge rate
On Mageia I did not got below 150 wakeups at all on idle, 10W discharge rate.

I repeat both systems were running razorqt, both had the nvidia binary drivers installed, and all unnecessary services were disabled on both (no bluetoth, no cups, no ssh, no samba). The only difference, in regard of services was that Mageia had iptraf enabled, but there was no network activity at all.

Anyway,the bottom line is that Mageia consumes more power than Archlinux (I have no other linux OS to compare with), which means less battery time, which affects some people (like me) badly.

I don't know if this should be a bug report or a feature request, but please improve Mageia power management.

Oh, what I also observed is when the ondemand cpu governor is active, my cpu jumps to a higher frequency level more ofthen, than in Archlinux. The reason I think is the same, more wakeups/sec.

My system is an Asus X55Sv laptop, Intel Core2Duo T7500, 2.2Ghz with NVidia 9500M GS, if matters.

Version-Release number of selected component (if applicable):


How reproducible:
Always.

Steps to Reproduce:
1.
2.
3.
Comment 1 Marja Van Waes 2012-11-29 21:34:59 CET
@ Ilyés

Did Arch already switch to systemd, too?


CC'ing razorqt maintainer.

@ Matteo

Do you have any ideas?

CC: (none) => marja11, matteo.pasotti
Source RPM: (none) => razorqt-0.4.1-3.mga2

Comment 2 Matteo Pasotti 2012-11-29 23:34:53 CET
I don't think this is a razorqt related issue and it's quite difficult to make a comparison because the two distributions differ quite a lot.

Ilyés, does Arch Linux use the same kernel provided by Mageia? Which version of RazorQt are you using on Arch Linux? Is that the same provided with Mageia 2? Same question for all the other applications you use? And so on...
Comment 3 Manuel Hiebel 2013-10-22 12:21:20 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 4 Manuel Hiebel 2013-11-23 16:16:46 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


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