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 <pknirsch@redhat.com> - (Lead, tuned, monitoring, documentation)
  • Jiri Skala <jskala@redhat.com> - (BLTK packager)
  • Marcela Maslanova <mmaslano@redhat.com> - (initscript/udev service start/stop automation)
• Quality Assurance
  • Jan Scotka <jsotka@redhat.com>
  • Karel Volny <kvolny@redhat.com>
  • Yulia Kopkova <ykopkova@redhat.com>

Prerequisite for Test Day

• Rawhide fully updated (some tips below). Remember, Rawhide is an unsupported development branch: use an installation you don't mind getting broken.

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

• • burn boot.iso and boot into and use lastest install tree
  • upgrade from F10 ( must firstly:)
    • • yum upgrade rpm
      • yum upgrade
    • then switch repos into rawhide and upgrade to rawhide
      • yum --enablerepo=rawhide updade rpm
      • yum --enablerepo=rawhide updade
  • Use apha release of rawhide
• FAS Account - you can create an account in 3 minutes if you don't have one

No animals will be hurt during testing

How to test?

• Update your machine to latest Rawhide (see above)
• install useful packages (described in each testcases which are important:

 # yum install powertop bltk tuned-utils 

The following testcases are available:

QA:Testcase_powermanagemt_personal
QA:Testcase_powermanagemt bluetooth
QA:Testcase_powermanagemt init1

• Upload your output into wiki, via steps in tescases

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