Test Day:2009-04-02 Power management

DATE	TIME	WHERE
Thu May 02, 2009	From 12:00 to 00:00 UTC (7am -> 7pm ET)	#fedora-qa)

What to test?

Today's instalment of Fedora Test Day will focus on:

• Features/PowerManagement

Who's available

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

• Development
  • Phil Knirsch - Lead, tuned, monitoring, documentation
  • Jiri Skala - BLTK packager
  • Marcela Maslanova - initscript/udev service start/stop automation
• Quality Assurance
  • Jan Scotka
  • Karel Volny
  • Yulia Kopkova

What's needed to test

• Rawhide or F-11-Beta fully updated.
• FAS Account - you can create an account in 3 minutes if you don't have one
• Your hardware profile uploaded to Smolt according to these instructions

Use caution
Remember, rawhide is a development branch. Use an installation you don't mind getting broken.

How to test?

Update your machine

See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live Image

Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture	MD5SUM
i386	551ca2636525dbf5a3530115cde634ee
x86_64	b0f87f300b83bf4baee86819fae1eaed

Latest syslinux package?
Creating a LiveUSB of this rawhide image requires the latest version of syslinux, which is currently available in Rawhide and in the latest Windows liveusb-creator. Users of F10 and below can upgrade to the latest syslinux package using

yum --enablerepo=rawhide update syslinux

.

Test

Follow each of these test cases:

• QA:Testcase_Power_Management_personal
• QA:Testcase_Power_Management_bluetooth
• QA:Testcase_Power_Management_init_1

General way

Make sure powertop is installed on your machine.

The tests can be run in various levels of accuracy depending on your system and additional equipment. For laptops the tests should be run on battery power so powertop can record the power usage. For normal systems use of a wattmeter like the ones from Watts Up can help record the power usage instead.

1. Run powertop -d
2. Run powertop -d on battery mode (laptops only)
3. Run powertop -d with a wattmeter

Additionally if you install kernel-devel and kernel-debuginfo you can additionally install tuned-utils and run additional monitoring tools:

1. Run diskdevstat
2. Run netdevstat

The results of those can be combined with the results from the various powertop runs.

For automated recording we've written a script that checks for the various tools necessary to record the results and saves the available results in several files and makes a tarball of them via your system-id.

Additionally in case you don't want to do the upload the script will output a summary of the results which you can just copy and paste into the wiki page here as well.

Progress

• In progress [ 90% ]
  • Need to find proprer way how to test it.
    • powertop - main utility to collect data about process
    • acpi - used in bltk (battery life toolkit, which is good for performance of some type of stress (reader, developer, office, idle)
  • What measure
    • More exact measurement in init runlevel 1
      • Written some scripts to test it
        • bzip2 test
        • dd copy test from /dev/zero
        • vsftpd test witl localhost lftp client
      • Idle test of bltk in runlevel 1
    • In runlevel 5
      • Other bltk stress (reader, office) usage - need fully charged battery
• old # Plautrba testcase for testing of bluetooth on demand
  • • computer tuned up and not tuned

Send in your results

Thank you.

Results

User	Smolt Profile	Personal use	Bluetooth output	Init1 basic	Bltk test	Comments
User:SampleUser