Bug 466703
| Summary: | suspend test fails due to Error: could not verify suspend | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Nicole Dai <ndai> | ||||||||||||||||||||
| Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> | ||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Lawrence Lim <llim> | ||||||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||||||
| Priority: | medium | ||||||||||||||||||||||
| Version: | 5.2 | CC: | gnichols, rlandry, tools-bugs, tyan, ykun, yoyzhang | ||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||
| Hardware: | All | ||||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||
| Doc Text: |
Cause:
=======
The SUSPEND test always fails.
Consequence:
============
No successful SUSPEND test run.
Fix:
====
Change the test to parse the correct suspendMessage for "suspend" and "hibernate".
Result:
=======
The SUSPEND test works correctly now.
|
Story Points: | --- | ||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||
| Last Closed: | 2009-08-27 16:34:17 UTC | Type: | --- | ||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||
Did you press function key to suspend the system? Also, please attach the portion of /var/log/messages from when the test was run. The test prompted same failure whether I press function key (Fn) or not. Attached the /var/log/messages for your reference: Oct 14 01:36:06 dhcp-66-70-61 hts/runtests[21296]: Beginning test run. Oct 14 01:36:06 dhcp-66-70-61 kudzu[21357]: obsolete kudzu ddcProbe called Oct 14 01:36:07 dhcp-66-70-61 hts/runtests[21296]: suspend: begin Oct 14 01:36:07 dhcp-66-70-61 python: hts/runtests[21372]: suspend-OSCommand-mem: begin Oct 14 01:36:27 dhcp-66-70-61 python: hts/runtests[21372]: suspend-OSCommand-mem: end Oct 14 01:36:27 dhcp-66-70-61 python: hts/runtests[21372]: suspend-FunctionKey-mem: begin Oct 14 01:36:41 dhcp-66-70-61 python: hts/runtests[21372]: suspend-FunctionKey-mem: end Oct 14 01:36:41 dhcp-66-70-61 hts/runtests[21296]: suspend: end Oct 14 01:36:41 dhcp-66-70-61 kudzu[21971]: obsolete kudzu ddcProbe called Oct 14 01:36:41 dhcp-66-70-61 hts/runtests[21296]: info: begin Did the system actually suspend? Did pressing the function key actually suspend the system? In other words, can you suspend the system to memory via the function key? Reproduced this bug in hts-5.3-14 on RHEL5.3 Server i386 system with T60 laptop. Attached suspend/output.log and /var/hts/result.xml files. The system actually suspend for 4 times: 1-suspend to mem by itself, 2-suspend to disk by itself, 3-suspend to mem by function key(F4), 4-suspend to disk by function key(F12). All resumed successfully for these 4 times. Created attachment 329695 [details]
suspend/output.log
Created attachment 329696 [details]
/var/hts/results.xml
Reproduced this bug in hts-5.3-16 on RHEL5.3 Server i386/x86_64 system with T60 laptop. Attached rhel5.3-x86_64-laptop-suspend.log, rhel5.3-x86_64-laptop-suspend-result.xml, rhel5.3-i386-laptop-suspend.log, rhel5.3-i386-laptop-suspend-result.xml. actually suspend for 2 times: 1-suspend by itself, 2-suspend to mem by function key(F4). Both resumed successfully for these 2 times. Created attachment 335987 [details]
rhel5.3-i386-laptop-suspend.log
Created attachment 335989 [details]
rhel5.3-i386-laptop-suspend-result.xml
Created attachment 335990 [details]
rhel5.3-x86_64-laptop-suspend.log
Created attachment 335991 [details]
rhel5.3-x86_64-laptop-suspend-result.xml
Did the system actually suspend once (when you pushed the suspend-to-memory button), or twice (when the test said it was going to suspend the system)? (In reply to comment #13) > Did the system actually suspend once (when you pushed the suspend-to-memory > button), or twice (when the test said it was going to suspend the system)? It actually suspended twice. Reproduced this bug in hts-5.3-17.el5 on RHEL5.3 Server x86_64 system with T60 laptop. Attached hts-5.3-17.el5-x86_64-laptop.log and hts-5.3-17.el5-x86_64-laptop-result.xml actually suspend for 2 times: 1-suspend by itself, 2-suspend to mem by function key(F4). Both resumed successfully for these 2 times. Created attachment 341291 [details]
hts-5.3-17.el5-x86_64-laptop.log
Created attachment 341292 [details]
hts-5.3-17.el5-x86_64-laptop-result.xml
Created attachment 348955 [details]
suspend.py patch with some additional changes - rev 3
removed spurious edit @117
Verified PASS with v7-1.0-14.el5 on RHEL5.3-Server-i386 (normal kernel) Hardware: ThinkPad-T60 Attach results.xml for your reference Created attachment 357730 [details]
results.xml on T60
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: ======= The SUSPEND test always fails. Consequence: ============ No successful SUSPEND test run. Fix: ==== Change the test to parse the correct suspendMessage for "suspend" and "hibernate". Result: ======= The SUSPEND test works correctly now. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1234.html |
Description of problem: suspend tests failed in laptop with the following outputs: Running ./suspend.py: This test will suspend the operating system. Please resume by pressing the power button after suspend has completed. suspend? (y|n) y response: y Suspending in 5 sec Has resume completed? (y|n) y response: y Error: could not verify suspend This test will suspend the operating system. Please resume by pressing the power button after suspend has completed. Please press the function key (Fn) to suspend the system to mem (y|n) y response: y Has resume completed? (y|n) y response: y Error: could not verify suspend ...finished running ./suspend.py, exit code=1 recovered exit code=1 hts-report-result /HTS/hts/suspend FAIL /var/log/hts/runs/1/suspend/output.log saveOutput: /var/log/hts/runs/1/suspend/output.log Version-Release number of selected component (if applicable): RHEL5.2 Server hts-5.2-20.el5 How reproducible: Always Steps to Reproduce: 1. Execute #hts certify {-t | --test} suspend in laptop 2. 3. Actual results: FAIL Expected results: PASS Additional info: