Test Day:2013-04-17 Power Management

Fedora Test Days
Power Management
Date	2013-04-17
Time	all day
Website	QA/Fedora_19_test_days
IRC	#fedora-test-day (webirc)
Mailing list	test

In construction
The Test Day page is yet in construction. It will be ready for the Test Day - when this message is removed :) .

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 ...

• Development - Jaroslav Škarvada (jskarvad) / PowerManagement SIG
• Quality Assurance - Jan Ščotka (jscotka), Martin Holec (Martix)

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, Mint room, ground floor, Brno 1 building (the older/bigger one), there will be installed navigation signs.

Prerequisite for Test Day

• An updated Fedora 19 pre-release (preferred) or the 32 bit live medium (SHA-1: TBD) or 64 bit live medium (SHA-1: TBD) 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 the 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. (13.00-17.00 CEST)
• Bugzilla account on the http://bugzilla.redhat.com if you plan to report found defects (bugs) to developers (highly recommended). If you do not have one and you do not plan to get it, you can still attend the test day and report the found issues to the test day wiki or via the reporting application, but this may slow down the resolution of bugs significantly.

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?

This test day is focused especially on suspend, hibernate, LCD brightness control, tuned application power management of video cards and overall power consumption. 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 the test cases bellow.

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 for the PM Test Day Overlay Repository (the key is also included in the pm-test-day support package, so if you don't mind to install the pm-test-day support package with the --nogpgcheck option you can go directly to step 2):

   # rpm --import http://jskarvad.fedorapeople.org/RPM-GPG-KEY-pm-test-day

2. Install the PM Test Day support package by (use the --nogpgcheck option if you didn't install the public key in the step 1):

   # yum install http://jskarvad.fedorapeople.org/pm-test-day-repo/pm-test-day-5-1.fc19.noarch.rpm

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

# yum update

You can also clear your audit log to easily spot all new PM Test Day related Selinux AVCs (this is recommended in case you aren't running from the live medium):

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

Known Bugs / Workarounds

• Problem with screen locking:

  Screen locking is disabled on live medium, to enable:

  • Set password for liveuser:

    # passwd liveuser

  • Enable the locking feature:

    $ gsettings set org.gnome.desktop.lockdown disable-lock-screen 'false'

  • Enable the lock in gnome-control-center:

    $ gnome-control-center screen

• Problem with hibernation from gnome-shell

  • AFAIK currently it is not possible to hibernate from the gnome-shell UI without tweaking (please don't ask me why, I am not Gnome developer), you can invoke the full hibernation (including desktop locking if set, see above) by using systemd:

    $ systemctl hibernate

Test Cases

Testcase	Description	Target	Approx. time required
Suspend	Tests suspend / resume.	All	2 minutes
Hibernate	Tests hibernate / resume.	All	2 minutes
Suspend hybrid	Tests hybrid suspend (AKA suspend to both) / resume.	All	2 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	Tests if there are no SELinux AVCs during profile switching.	All	5 minutes

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component systemd, selinux-policy, kernel, or tuned. If you are reporting suspend/hibernate problem, please also attach output from dmesg and journalctl. 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. 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 short description of the system you tested (i.e. machine identification and preferably BIOS version in case you know it and/or you are able to get it by e.g. dmidecode tool). For each test case, use the result template to enter your result, as shown in the example result line.

Alternative reporting through the [web application]
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, you can try to report via o [web app]. Results from this web application will be automatically transferred to the Wiki on 2013-04-28 and the alternative reporting system will be shutdown to this date. Feel free to continue testing and filling the wiki even after this date. Please note the number of reports currently visible in the wiki doesn't correspond to the number of reports so far sent (i.e. reports sent through the web application).

User	System description Profile	Suspend	Hibernate	Suspend Hybrid	Lid close	Backlight control	Tuned	Tuned disabled idle	Tuned powersave idle	Selinux AVCs	References
Sample User	Lenovo T500 (BIOS version 3.22)	fail	pass	warn	pass	inprogress	fail	4.800 Wh	4.710 Wh	pass
User	System description Profile	Suspend	Hibernate	Suspend Hybrid	Lid close	Backlight control	Tuned	Tuned disabled idle	Tuned powersave idle	Selinux AVCs	References

Previous test day (for reference)

Previous F18 PM Test Day