RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 663240 - [WHQL] pwrtest failed in the job "CHAOS-Concurrent Hardware And OS test"
Summary: [WHQL] pwrtest failed in the job "CHAOS-Concurrent Hardware And OS test"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: seabios
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Gleb Natapov
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 659172
Blocks: 580954
TreeView+ depends on / blocked
 
Reported: 2010-12-15 05:07 UTC by Qunfang Zhang
Modified: 2013-12-09 00:52 UTC (History)
9 users (show)

Fixed In Version: seabios-0.6.1.2-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 659172
: 674527 (view as bug list)
Environment:
Last Closed: 2011-05-19 13:04:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
pwrtest-rhel6 (2.73 KB, text/plain)
2010-12-15 05:12 UTC, Qunfang Zhang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0564 0 normal SHIPPED_LIVE seabios bug fix and enhancement update 2011-05-18 17:57:11 UTC

Comment 1 Qunfang Zhang 2010-12-15 05:12:43 UTC
Created attachment 468767 [details]
pwrtest-rhel6

virtio-win version:
1.1.16

Comment 3 Qunfang Zhang 2011-01-12 02:24:55 UTC
Update:
Same result in virtio-win-1.1.17.

DTM log:
 Start Test 1/11/2011 3:24:07.228 PM PwrTest
Message 1/11/2011 3:24:07.228 PM
Error 1/11/2011 3:24:07.228 PM ERROR: System does not support any sleep with RTC wakeup enable!
File:   d:\5429\base\power\tools\pwrtest\exe\sleep.cpp Line: 1789
Error Type:   NT_STATUS
Error Code:   0xc0000001
Error Text:   Error 0xc0000001
End Test 1/11/2011 3:24:08.228 PM PwrTest
Result:   Fail
Repro:   pwrtest /sleep /c:4 /d:300 /s:all

Comment 4 Eduardo Habkost 2011-01-12 19:49:02 UTC
According to Vadim it is a bios bug. Moving to seabios, assigning to Gleb.

Comment 5 Eduardo Habkost 2011-01-12 19:50:14 UTC
(In reply to comment #3)
> Update:
> Same result in virtio-win-1.1.17.

Could you confirm the version of packages on the host?

Especially:
- kernel
- qemu-kvm
- seabios
- vgabios

Comment 6 Qunfang Zhang 2011-01-13 01:58:52 UTC
(In reply to comment #5)
> (In reply to comment #3)
> > Update:
> > Same result in virtio-win-1.1.17.
> 
> Could you confirm the version of packages on the host?
> 
> Especially:
> - kernel
> - qemu-kvm
> - seabios
> - vgabios

kernel-2.6.32-95.el6.x86_64
qemu-kvm-0.12.1.2-2.129.el6.x86_64
seabios-0.5.1-3.el6.x86_64
vgabios-0.6b-3.4.el6.noarch

Comment 7 Gleb Natapov 2011-01-13 07:40:40 UTC
What I would like to know it why it worked before. We already signed drivers and didn't see the error. So what changed?

Vadim you had a patch ready. Can you send it?

Comment 8 Qunfang Zhang 2011-01-13 07:56:11 UTC
(In reply to comment #7)
> What I would like to know it why it worked before. We already signed drivers
> and didn't see the error. So what changed?
> 
> Vadim you had a patch ready. Can you send it?

Seems it did not work before. We passed whql and got the signatures because it is not a blocker. It is a failed child job though the parent(main) job got passed.

Comment 9 Vadim Rozenfeld 2011-01-13 08:08:48 UTC
(In reply to comment #7)
> What I would like to know it why it worked before. We already signed drivers
> and didn't see the error. So what changed?
> 
> Vadim you had a patch ready. Can you send it?

When applying the following changes, we can pass S4 test case.
But I have never tried to run the entire test.

for RHEL5:
diff --git a/bios/rombios32.c b/bios/rombios32.c
index 8928233..08fc369 100755
--- a/bios/rombios32.c
+++ b/bios/rombios32.c
@@ -1566,8 +1566,8 @@ void acpi_bios_init(void)
     fadt->plvl3_lat = cpu_to_le16(0xfff); // C3 state not supported
     fadt->gpe0_blk = cpu_to_le32(0xafe0);
     fadt->gpe0_blk_len = 4;
-    /* WBINVD + PROC_C1 + SLP_BUTTON + FIX_RTC */
-    fadt->flags = cpu_to_le32((1 << 0) | (1 << 2) | (1 << 5) | (1 <<
6));
+    /* WBINVD + PROC_C1 + SLP_BUTTON + FIX_RTC + RTC_S4*/
+    fadt->flags = cpu_to_le32((1 << 0) | (1 << 2) | (1 << 5) | (1 << 6)
| (1<<7));
     acpi_build_table_header((struct acpi_table_header *)fadt, "FACP",
                             sizeof(*fadt), 1);

for RHEL6:
diff --git a/src/acpi.c b/src/acpi.c
index 1962632..ae542e5 100644
--- a/src/acpi.c
+++ b/src/acpi.c
@@ -336,8 +336,8 @@ build_fadt(int bdf)
     fadt->plvl3_lat = cpu_to_le16(0xfff); // C3 state not supported
     fadt->gpe0_blk = cpu_to_le32(0xafe0);
     fadt->gpe0_blk_len = 4;
-    /* WBINVD + PROC_C1 + SLP_BUTTON + FIX_RTC */
-    fadt->flags = cpu_to_le32((1 << 0) | (1 << 2) | (1 << 5) | (1 <<
6));
+    /* WBINVD + PROC_C1 + SLP_BUTTON + FIX_RTC + RTC_S4*/
+    fadt->flags = cpu_to_le32((1 << 0) | (1 << 2) | (1 << 5) | (1 << 6)
| (1<<7));
 
     build_header((void*)fadt, FACP_SIGNATURE, sizeof(*fadt), 1);

Comment 14 Qunfang Zhang 2011-02-15 06:40:26 UTC
Verified pass on seabios-0.6.1.2-3.el6.
Run this job again after update the seabios to the fixed version. pass.

Comment 16 errata-xmlrpc 2011-05-19 13:04:39 UTC
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-2011-0564.html

Comment 17 Marc-Andre Lureau 2011-09-16 11:21:30 UTC
I launch "pwrtest /sleep /c:4 /d:300 /s:all" on win7dbg x64, host rhel6.1 with seabios-0.6.1.2-3.el6 and I still get the error.

My kvm line is:

/usr/libexec/qemu-kvm -M rhel6.1.0 -enable-kvm -m 4096 -smp 1,sockets=1,cores=1,threads=1 -name Win7x64-qxlw7 -uuid d03c4eb4-19bc-e4dc-dcb8-9faaba1abc46 -nodefconfig -nodefaults -monitor stdio -rtc base=utc -boot c -drive file=/dev/vg_kvm/debian,if=none,id=drive-ide0-0-0,format=raw,cache=none,aio=threads -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=20,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:d0:4d:60,bus=pci.0,addr=0x3 -chardev socket,host=localhost,port=4555,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -spice port=5909,addr=127.0.0.1,disable-ticketing -vga qxl -global qxl-vga.vram_size=9437184 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -snapshot

Am I missing some arguments or some update?

thanks


Note You need to log in before you can comment on or make changes to this bug.