m (internal link cleaning) |
|||
(8 intermediate revisions by 3 users not shown) | |||
Line 158: | Line 158: | ||
| [[User:jskarvad|Jaroslav Škarvada]] | | [[User:jskarvad|Jaroslav Škarvada]] | ||
| [http://www.smolts.org/client/show/pub_2a35d874-f0c8-4011-b746-e461d7adf07d Lenovo T500] | | [http://www.smolts.org/client/show/pub_2a35d874-f0c8-4011-b746-e461d7adf07d Lenovo T500] | ||
| {{result|warn}} <ref>Test passed, but I encountered {{bz|742061}} that was related to wlan. I had to install abrt-cli in order to report it, because the abrt-gui didn't handle it. All comments about it will be handled to abrt guys.</ref> | | {{result|warn}} <ref group="long">Test passed, but I encountered {{bz|742061}} that was related to wlan. I had to install abrt-cli in order to report it, because the abrt-gui didn't handle it. All comments about it will be handled to abrt guys.</ref> | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|pass}} [http://fedoraproject.org/w/uploads/f/f8/Pm-test-day-20110324-pub_8aa3ce1e-cf39-4224-b5ab-04e72f17554b.txt bugreport] | | {{result|pass}} [http://fedoraproject.org/w/uploads/f/f8/Pm-test-day-20110324-pub_8aa3ce1e-cf39-4224-b5ab-04e72f17554b.txt bugreport] | ||
Line 175: | Line 175: | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|warn}} <ref>My system doesn't suspend with docking station because GNOME3 is brain-damaged. {{bz|719679}}, with patch [https://bugzilla.gnome.org/show_bug.cgi?id=657201 here]. Since this wastes power, I'm reporting it here for powersaving test day even though it is because "the designers wanted this behavior".</ref> | | {{result|warn}} <ref group="long">My system doesn't suspend with docking station because GNOME3 is brain-damaged. {{bz|719679}}, with patch [https://bugzilla.gnome.org/show_bug.cgi?id=657201 here]. Since this wastes power, I'm reporting it here for powersaving test day even though it is because "the designers wanted this behavior".</ref> | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|pass}} | | {{result|pass}} | ||
Line 211: | Line 211: | ||
| [http://www.smolts.org/client/show/pub_cf149895-0a90-474f-8039-8710f72197ca Lenovo ThinkPad T510] | | [http://www.smolts.org/client/show/pub_cf149895-0a90-474f-8039-8710f72197ca Lenovo ThinkPad T510] | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|fail}} <ref>Didn't hibernate, but a message AC POWER printed instead of it (like AC cable plugged in, but I didn't do anything with the cable). Run from LiveUSB.</ref> | | {{result|fail}} <ref group="long">Didn't hibernate, but a message AC POWER printed instead of it (like AC cable plugged in, but I didn't do anything with the cable). Run from LiveUSB.</ref> | ||
| {{result|pass}} [http://scratch.englab.brq.redhat.com/hhorak/pm-test-day-20110324-pub_02a03ebf-914e-417e-8f65-998961ed7791.txt bugreport] | | {{result|pass}} [http://scratch.englab.brq.redhat.com/hhorak/pm-test-day-20110324-pub_02a03ebf-914e-417e-8f65-998961ed7791.txt bugreport] | ||
| {{result|pass}} | | {{result|pass}} | ||
Line 227: | Line 227: | ||
| {{result|pass}} [http://jvcelak.fedorapeople.org/testday-110929/pm-test-day-dell.txt bugreport] | | {{result|pass}} [http://jvcelak.fedorapeople.org/testday-110929/pm-test-day-dell.txt bugreport] | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|warn}} <ref>Didn't suspend when the lid was closed. But it works after reboot Before the reboot, PM features of the desktop were kind of missing. The battery icon was not there, no brightness control in "gnome-control-center power". This happens to me from time to time on regular basis, maybe some problem with ACPI. But I cannot reliably reproduce.</ref> | | {{result|warn}} <ref group="long">Didn't suspend when the lid was closed. But it works after reboot Before the reboot, PM features of the desktop were kind of missing. The battery icon was not there, no brightness control in "gnome-control-center power". This happens to me from time to time on regular basis, maybe some problem with ACPI. But I cannot reliably reproduce.</ref> | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|pass}} | | {{result|pass}} | ||
Line 276: | Line 276: | ||
| [http://www.smolts.org/client/show/pub_af919474-739a-4b7d-ae4d-aea8045af926 KVM virtual machine] | | [http://www.smolts.org/client/show/pub_af919474-739a-4b7d-ae4d-aea8045af926 KVM virtual machine] | ||
| {{result|fail}} <ref>cat /sys/power/state shows only disk</ref> | | {{result|fail}} <ref>cat /sys/power/state shows only disk</ref> | ||
| {{result|fail}} <ref>(upowerd:5277): UPower-WARNING **: Failed to acquire org.freedesktop.UPower (upowerd:5277): UPower-WARNING **: Could not acquire name; bailing out, not working </ref> | | {{result|fail}} <ref group="long">(upowerd:5277): UPower-WARNING **: Failed to acquire org.freedesktop.UPower (upowerd:5277): UPower-WARNING **: Could not acquire name; bailing out, not working </ref> | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|fail}} <ref> Some profile caused, that mouse was disabled and not working, tested with: for foo in `tuned-adm list 2>&1 |egrep "^- " |sed "s/- //"`; do tuned-adm profile $foo; sleep 1; tuned-adm active; done, after investigation I found that spindown-disc caused the problem with mouse</ref> | | {{result|fail}} <ref group="long"> Some profile caused, that mouse was disabled and not working, tested with: for foo in `tuned-adm list 2>&1 |egrep "^- " |sed "s/- //"`; do tuned-adm profile $foo; sleep 1; tuned-adm active; done, after investigation I found that spindown-disc caused the problem with mouse</ref> | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|none}} | | {{result|none}} | ||
Line 316: | Line 316: | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|fail}} <ref>Hibernate works ok, but in resume process ocurred force reboot.</ref> | | {{result|fail}} <ref>Hibernate works ok, but in resume process ocurred force reboot.</ref> | ||
| {{result|pass}} [ | | {{result|pass}} [[File:Pm-test-day-20110324-pub_65ca9c56-3cba-4292-abde-0980e02469f1.txt|bugreport]] | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|fail}} <ref>No reaction. System kept running, backlight on/off works.</ref> | | {{result|fail}} <ref>No reaction. System kept running, backlight on/off works.</ref> | ||
Line 382: | Line 382: | ||
| {{result|fail}} <ref>Hibernate works ok, but sometimes there is force reboot while resume (but sometimes correct).</ref> | | {{result|fail}} <ref>Hibernate works ok, but sometimes there is force reboot while resume (but sometimes correct).</ref> | ||
| {{result|pass}} [http://fedoraproject.org/w/uploads/d/d2/Pm-test-day-20110324-pub_4f9e2987-f566-43f5-8036-c8e03e1cd06e.txt bugreport] | | {{result|pass}} [http://fedoraproject.org/w/uploads/d/d2/Pm-test-day-20110324-pub_4f9e2987-f566-43f5-8036-c8e03e1cd06e.txt bugreport] | ||
| {{result|fail}} <ref>Gnome detected it properly but no OSD is shown and no file /tmp/pmtd-osd.log is created (not exists). Neither restarting upowerd does not solve this problem. However, when was battery low, OSD was shown.</ref> | | {{result|fail}} <ref group="long">Gnome detected it properly but no OSD is shown and no file /tmp/pmtd-osd.log is created (not exists). Neither restarting upowerd does not solve this problem. However, when was battery low, OSD was shown.</ref> | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|warn}} <ref>Increasing is not properly showed by Gnome. It works only from start to first half. In half of progress bar, backlight is in full state and increasing causing progress bar change but no backlight. When decreasing, other thing happens - backlight is set lower than should be and immediately light up (to correct level) - so it's causing unpleasant flashing.</ref> | | {{result|warn}} <ref group="long">Increasing is not properly showed by Gnome. It works only from start to first half. In half of progress bar, backlight is in full state and increasing causing progress bar change but no backlight. When decreasing, other thing happens - backlight is set lower than should be and immediately light up (to correct level) - so it's causing unpleasant flashing.</ref> | ||
| {{result|pass}} | | {{result|pass}} | ||
| 823 mAh | | 823 mAh | ||
Line 420: | Line 420: | ||
| {{result|warn}}<ref>Resuming froze the system forcing hard reset</ref> | | {{result|warn}}<ref>Resuming froze the system forcing hard reset</ref> | ||
| {{result|inprogress}} | | {{result|inprogress}} | ||
| {{result| | | {{result|pass}}[ bugreport] | ||
| {{result| | | {{result|pass}} | ||
| {{result| | | {{result|pass}} | ||
| {{result| | | {{result|pass}} | ||
| {{result| | | {{result|pass}} | ||
| E:2791 mWh | | E:2791 mWh | ||
| E: | | E:2392 mWh | ||
| <references/> | | <references/> | ||
|- | |- | ||
| [[User:luya|Luya Tshimbalanga]] | |||
| [http://www.smolts.org/client/show/pub_47816dee-2c35-40a7-9e38-236fec3bb786 Desktop] | |||
| {{result|warn}}<ref>Resuming froze the system forcing hard reset</ref> | |||
| {{result|fail}}<ref>Swap is about 6GB while RAM size is 8GB, fail to hibernate</ref> | |||
| {{result|na}} | |||
| {{result|na}} | |||
| {{result|inprogress}} | |||
| {{result|na}} | |||
| {{result|na}} | |||
| na | |||
| na | |||
| <references/> | |||
|- | |- | ||
! User | ! User | ||
Line 444: | Line 456: | ||
|} | |} | ||
[[Category:Fedora 16 Test Days]] | == Long comments == | ||
<references group="long" /> | |||
[[Category:Fedora 16 Test Days]] |
Latest revision as of 15:36, 18 September 2016
Fedora Test Days | |
---|---|
![]() | |
Power Management | |
Date | 2011-09-29 |
Time | all day |
Website | QA/Fedora_16_test_days |
IRC | #fedora-test-day (webirc) |
Mailing list | test |
What to test?[edit]
Today's instalment of Fedora Test Day will focus on Power Management
Who's available[edit]
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)
Note: jskarvad will be available at least from 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.
Prerequisite for Test Day[edit]
- PM Test Day LiveCD (md5sum: f470deed996574ab101d75b9eb5bf5c7) or an updated Fedora 16 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.
- 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[edit]
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?[edit]
It is focused especially on suspend, hibernate, power-consumption, LCD brightness control, tuned profiles. 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[edit]
- 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
- Install the PM Test Day support package by:
# yum install http://jskarvad.fedorapeople.org/pm-test-day-repo/pm-test-day-2-1.fc16.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.
Finally make sure you have all current updates (and temporal fixes) installed by:
# yum update
Test Cases[edit]
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 |
Tuned basic | Tests tuned-adm (tuned) basic functionality. | All | 5 minutes |
Tuned disabled idle | Measures power consumption of machine in active idle with tuned disabled. | Laptops only | 15 minutes |
Tuned powersave idle | Measures power consumption of machine in active idle with tuned laptop-battery-powersave profile. | Laptops only | 15 minutes |
Known Bugs / Workarounds[edit]
The following are the known bugs and workarounds. You do not need to report them, because the problems are known and most fixes are already in updates-testing repo.
- upower < 0.9.13-1 has unresolved symbol (g_unix_signal_add_watch_full) due to glib API change and doesn't start which cause fail of the pm-powersave test case. Upgrade to upower-0.9.13-1 (from pm-test-day repo) or newer by:
# yum update upower
- Then logout/login or start upower by hand:
# /usr/libexec/upowerd
- If you are using the latest LiveCD / USB (20110928 or newer) this workaround have been already installed for you.
- If the OSD in test case pm-powersave is not shown, patch the pmtd-osd by following command:
# echo 'echo "$STR" >> /tmp/pmtd-osd.log' >> /usr/bin/pmtd-osd
- and than read the OSD messages from /tmp/pmtd-osd.log
- If your system doesn't have /proc/acpi/battery/BAT0 directory but has there other sub-directory (e.g. BAT1) and you are going to run the Tuned disabled idle, Tuned powersave idle test cases, you will need to update your pm-test-day package to version 2.1-1 or newer by:
yum update pm-test-day
- If you cannot see the pm-test-day update, try to clear your yum caches by:
yum clean all
- If you are running from the LiveUSB, the Tuned disabled idle, Tuned powersave idle test cases can hang your computer. It is caused by the cache clear command - the reason why this happen is currently unknown. To workaround this, open /usr/bin/pmtd-measure script in any text editor and comment (by #) the line with the call of clear_caches function. With the pm-test-day-2-1 package it is the line 76, with the pm-test-day-2.1-1 package it is the line 95.
Test Results[edit]
If you have problems with any of the tests, report a bug to Bugzilla usually for the component pm-utils, 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.
Long comments[edit]
- ↑ Test passed, but I encountered RHBZ #742061 that was related to wlan. I had to install abrt-cli in order to report it, because the abrt-gui didn't handle it. All comments about it will be handled to abrt guys.
- ↑ My system doesn't suspend with docking station because GNOME3 is brain-damaged. RHBZ #719679, with patch here. Since this wastes power, I'm reporting it here for powersaving test day even though it is because "the designers wanted this behavior".
- ↑ Didn't hibernate, but a message AC POWER printed instead of it (like AC cable plugged in, but I didn't do anything with the cable). Run from LiveUSB.
- ↑ Didn't suspend when the lid was closed. But it works after reboot Before the reboot, PM features of the desktop were kind of missing. The battery icon was not there, no brightness control in "gnome-control-center power". This happens to me from time to time on regular basis, maybe some problem with ACPI. But I cannot reliably reproduce.
- ↑ (upowerd:5277): UPower-WARNING **: Failed to acquire org.freedesktop.UPower (upowerd:5277): UPower-WARNING **: Could not acquire name; bailing out, not working
- ↑ Some profile caused, that mouse was disabled and not working, tested with: for foo in
tuned-adm list 2>&1 |egrep "^- " |sed "s/- //"
; do tuned-adm profile $foo; sleep 1; tuned-adm active; done, after investigation I found that spindown-disc caused the problem with mouse - ↑ Gnome detected it properly but no OSD is shown and no file /tmp/pmtd-osd.log is created (not exists). Neither restarting upowerd does not solve this problem. However, when was battery low, OSD was shown.
- ↑ Increasing is not properly showed by Gnome. It works only from start to first half. In half of progress bar, backlight is in full state and increasing causing progress bar change but no backlight. When decreasing, other thing happens - backlight is set lower than should be and immediately light up (to correct level) - so it's causing unpleasant flashing.