diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/1410')
| -rw-r--r-- | results/classifier/zero-shot/108/other/1410 | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1410 b/results/classifier/zero-shot/108/other/1410 new file mode 100644 index 000000000..5f02a4735 --- /dev/null +++ b/results/classifier/zero-shot/108/other/1410 @@ -0,0 +1,29 @@ +graphic: 0.920 +boot: 0.843 +device: 0.740 +performance: 0.617 +PID: 0.458 +files: 0.410 +permissions: 0.380 +semantic: 0.377 +debug: 0.321 +socket: 0.264 +vnc: 0.165 +other: 0.120 +network: 0.036 +KVM: 0.016 + +system_powerdown only works once +Description of problem: +When the guest is configured to sleep on power button events, something in the ACPI states are not restored coming out of resume. The first call to `system_powerdown` succeeds, but the second after waking the system is rejected in `acpi_pm1_evt_power_down()` since `ar->pm1.evt.en` is zero coming out of the resume path. + +There is probably something deeper (or perhaps in seabios?) since removing the test in that handler doesn't cause a second sleep either. +Steps to reproduce: + +1. Boot a guest configured to sleep when it receives a power button event +2. `system_powerdown` from the monitor to tell it to sleep +3. `info status` to verify that it is suspended +4. Wake the guest, either with `system_wakeup` or moving the mouse or something +5. `system_powerdown` has no effect +Additional information: +This is using qemu-7.2.0 built from source with a Windows 10 guest and IGD GPU+audio passthrough. |