Test Day:2012-10-11 Power Management

From FedoraProject

Revision as of 23:03, 10 October 2012 by Jskarvad (Talk | contribs)

Jump to: navigation, search
Fedora Test Days
Power Management

Date 2012-10-11
Time all day

Website QA/Fedora_18_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.
On site event
You can attend this event online or personally in Red Hat Brno office


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 at least during 10:00 - 22:00 (UTC+2) on #fedora-test-day, #fedora-power, #fedora-devel, otherwise he will be on e-mail with non guaranteed response time. He will be also available on site in Red Hat Brno office during 13:00 - 19:00, Visitors room, 4th floor (in the front of reception desk).

Prerequisite for Test Day

  • The 32 bit live medium (SHA-1: e003ad7e7bcac9cc018ee2e0cee5977a4779b59d) or 64 bit live medium (SHA-1: f63f4faebdd0b3398ba6755d681d7e630efba091) or an updated Fedora 18 pre-release or you may get nightly composed LiveCD.
    • It is possible to convert the LiveCD into LiveUSB by following the How_to_create_and_use_Live_USB instructions. If you convert the LiveCD into LiveUSB it is recommended to create on USB another primary partition that will serve as swap. This is useful for pm-hibernate test case.
    • If you attend the event on-site in Red Hat Brno office, there will be prepared bootable USB flash disks/CD ROMs, thus you only need to bring your hardware there.
  • Your hardware profile uploaded to Smolt according to these instructions
  • Optional: account on fedoraproject.org if you plan to upload the pm-utils bugreport file. If you do not have one and you do not plan to get it, you can still attend the test day - there are instructions in the appropriate test case(s) bellow how to handle such situation.

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?

It is focused especially on suspend, hibernate, power-consumption, LCD brightness control and tuned. Some test cases are only for laptop users and it is noted in the 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 or to the form.

Prepare your system

PM Test Day Live medium
If you are using our PM Test Day Live medium, please skip the following steps, 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 http://jskarvad.fedorapeople.org/RPM-GPG-KEY-pm-test-day
  2. Install the PM Test Day support package by:
    # yum install http://jskarvad.fedorapeople.org/pm-test-day-repo/pm-test-day-4-1.fc18.noarch.rpm
    • This procedure will also install the public key which will be then used for verification of packages from the PM Test Day repo.

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

# yum update

Clear your audit log (especially important in case you aren't running from the live medium):

# echo -n > /var/log/audit/audit.log

Known Bugs / Workarounds

  • RHBZ #862801 - Anaconda hangs when 'Configuring installed system'
    You can encounter this when doing liveinst from the live media, current workaround: 'pkill anaconda'.

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 2 minutes
pm-suspend-hybrid Tests hybrid suspend (AKA suspend to both) / resume via pm-utils. All 2 minutes
pm-powersave Tests detection of AC / battery (upower functionality) and pm-powersave reactions to power source changes (pm-utils). Laptops 1 minutes
Lid close Tests system reaction to lid close. Laptops 1 minutes
Backlight control Tests LCD backlight control. Laptops 1 minute
Tuned Tests tuned-adm (tuned) basic functionality. All 5 minutes
Tuned disabled idle Measures power consumption of machine in active idle with tuned disabled. Laptops or users with wattmeter 15 minutes
Tuned powersave idle Measures power consumption of machine in active idle with tuned laptop-battery-powersave profile. Laptops or users with wattmeter 15 minutes
Selinux AVCs Test if ther is no AVCs during profile switching. All 1 minutes

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component pm-utils, selinux-policy, or tuned. If you are reporting suspend/hibernate problem, please also attach output from dmesg and pm-utils-bugreport-info.sh. 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 or to the form. The first column should be your name with a link to your Fedora User Wiki page (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.

Alternative reporting through the [form]
If you are not familiar with the Wiki editing or you come here in prime time and there are a lot of conflicted edits in the Wiki, try to report via our simplified [form]. Results from this form will be automatically transferred to the Wiki later (after the event), thus the number of reports currently visible in the wiki doesn't correspond to the number of reports so far sent through the form.
User Smolt
pm-suspendr pm-hibernate pm-suspend-hybrid pm-powersave Lid close Backlight control Tuned Tuned disabled idle Tuned powersave idle Selinux AVCs References
Sample User Sample Machine
Fail fail
Fail fail
Pass pass
Warning warn
Pass pass
Inprogress inprogress
Fail fail
4.800 Wh 4.710 Wh
Pass pass
  1. RHBZ #54321
  2. Got report but also encountered RHBZ #54320
  3. RHBZ #864911
User Smolt
pm-suspend pm-hibernate pm-suspend-hybrid pm-powersave Lid close Backlight control Tuned Tuned disabled idle Tuned powersave idle Selinux AVCs References

Previous test day (for reference)

Previous F17 PM Test Day