From Fedora Project Wiki

(Test Results)
(Test Results)
Line 180: Line 180:
| [[User:jscotka|Jan Scotka]]
| [[User:jscotka|Jan Scotka]]
| [ HW]
| [ HW]

Revision as of 12:51, 23 March 2011

Fedora Test Days
Power Management

Date 2011-03-24
Time all day

Website QA/Fedora_15_test_days
IRC #fedora-test-day (webirc)

Mailing list

Can't make the date?
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's instalment of Fedora Test Day will focus on Power Management

Who's available

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...

Note: jskarvad will be available during CET business hours (UTC+1) on #fedora-test-day, #fedora-power, #fedora-devel, otherwise he will be on e-mail with non guaranteed response time.

Prerequisite for Test Day

Typing convetions

In the following text commands that needs to be run as root are prefixed by #, e.g.:

# id

means to run id command under the root account. Commands prefixed by $ do not need to be run under the root account.

How to test?

Focus on pm-utils, powertop, tuned. Some test cases are only for laptop users and it is signalled in test case description field. If you do not have laptop just skip them. You can also skip other test cases (e.g. if you do not have enough time). In this case just leave the columns for skipped test cases blank. Please note that your report will be still valuable even if you do not finish all test cases. The procedure:

  • Run test cases bellow.
  • Report results to the result table.

Prepare your system

If you are using our PM Test Day LiveCD, please skip this step, because everything is already prepared for you.
  1. Install the public key (in case you would like to verify the PM Test Day support package, otherwise you can skip this step because the public key will be installed automatically with the PM Test Day support package in the next step):
    # rpm --import
  2. Install the PM Test Day support package by:
    # yum install
    • This procedure will also install the public key which will be then used for verification of packages from the PM Test Day repo.

Finally make sure you have all current updates (and temporal fixes) installed by:

# yum update

Test Cases

Testcase Description Target Approx. time required
pm-suspend Tests suspend / resume via pm-utils. All 2 minutes
pm-hibernate Tests hibernate / resume via pm-utils. All 5 minutes
pm-bugreport Tests pm-utils bug-reporting functionality. All 2 minutes
pm-powersave Tests detection of AC / battery (upower functionality) and pm-powersave reactions to power source changes (pm-utils). Laptops only 2 minutes
Lid close Tests system reaction to lid close. Laptops only 2 minutes
Backlight control Tests LCD backlight control. Laptops only 1 minute
PowerTOP 2.x basic Tests PowerTOP 2.x basic functionality and UI consistency. All 5 minutes
PowerTOP 2.x PE engine Tests PowerTOP 2.x power estimation engine. Laptops only 60 minutes
PowerTOP 2.x suggestions Tests PowerTOP 2.x tunables. All 5 minutes
Tuned basic Tests tuned-adm (tuned) basic functionality. All 5 minutes
Tuned psave idle Measures energy consumption of machine in active idle with tuned laptop-battery-powersave profile. Laptops only 15 minutes
Tuned psave load Measures test duration / energy consumption of machine under load with tuned laptop-battery-powersave profile. All, laptops preferred 5 - 30 minutes
Tuned perf idle Measures energy consumption of machine in active idle with tuned throughput-performance profile. Laptops only 15 minutes
Tuned perf load Measures test duration / energy consumption of machine under load with tuned throughput-performance profile. All, laptops preferred 5 - 30 minutes

Known Bugs

The following bugs are known, please do not report them again. If you update your system from the PM Test Day repo, you shouldn't encounter them

  • RHBZ #684854 - It is about missing tab bar in PowerTOP 2.x.
  • RHBZ #663995 - It is about SELinux AVCs during suspend / hibernate.

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component pm-utils, or powertop, or tuned. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line. bugreport.txt will be generated by test case pm-bugreport, instructions for uploading are included in this test case. The bugreport.txt gives us valuable information about your HW / SW configuration and debug log of your last suspend / hibernate process.

User Smolt Profile pm-suspend pm-hibernate pm-bugreport pm-powersave Lid close Backlight control PowerTOP 2.x basic PowerTOP 2.x PE engine PowerTOP 2.x suggestions Tuned basic Tuned psave idle Tuned psave load Tuned perf idle Tuned perf load References
Sample User HW
Pass pass
Pass pass
Warning warn
Pass pass
Warning warn
Pass pass
Fail fail
Pass pass
Pass pass
E:2300 T:320 / E:3000 E:2200 T:300 / E:3200
Warning warn
  1. Got report but also ncountered RHBZ #54320
  2. Test pass, but also encountered RHBZ #54321
  3. RHBZ #12345
  4. Got results but also encountered RHBZ #54322
Jan Scotka HW