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 769163 - [WHQL]Lots of jobs failed due to "unexpected reboot"
Summary: [WHQL]Lots of jobs failed due to "unexpected reboot"
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-20 06:21 UTC by Mike Cao
Modified: 2014-07-11 06:48 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-10 13:58:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Mike Cao 2011-12-20 06:21:03 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
virtio-win-prewhql-0.1.20


How reproducible:
sometimes 

Steps to Reproduce:
1.win2k8R2 - CHAOS-Concurrent Hardware And OS Test (278)
2.win2k8_64 - Common Scenario Stress With IO(676)
3.win2k8_32 - Sleep_Stress_With_IO (672)
4.Win7_64_  - CHAO-Concurrent Hardware And OS Test (278)
  
Actual results:
job failed .and logs are similiar.

Root Cause 
2 12/19/2011 6:26:39 PM Execution Agent 20-7-BLK Task Cancelled Because of an Unexpected Reboot

Machine Rebooted Unexpectedly when Task "RunJob - Pnpdtest with concurrent IO in parallel with DevPathExer - Library Job" was running

 
Resolution 
This computer is found to have had an unexpected reboot. None of the tasks that were running before the reboot requested a reboot. 
The job will be cancelled as a result.  



Additional info:
1.this is not a regression or test blocker
2.hit this issue every cycle 
3.can not 100% reproduce .
Comment 2 Mike Cao 2011-12-20 08:41:41 UTC 
 job Common Scenario Stress With DiskIO(627) for win2k3_32 also failed with the same log
Comment 3 Vadim Rozenfeld 2011-12-20 13:16:15 UTC 
(In reply to comment #2)
>  job Common Scenario Stress With DiskIO(627) for win2k3_32 also failed with the
> same log

Hi Mike,

Could you please upload log files?
Btw, does it happen with viostor driver only?

Best regards,
Vadim.
Comment 4 Mike Cao 2011-12-21 05:57:37 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> >  job Common Scenario Stress With DiskIO(627) for win2k3_32 also failed with the
> > same log
> 
> Hi Mike,
> 
> Could you please upload log files?
> Btw, does it happen with viostor driver only?
> 
> Best regards,
> Vadim.

Hi, Vadim

I check all the failed job ,there is no task log for those jobs .
I check the history test results ,found that  win2k8-32 NDIS Test6.5(MPE) also hit this issue with virtio-win-prewhql-0-1-17.

Best Regards,
Mike
Comment 5 Mike Cao 2011-12-28 06:12:42 UTC 
Hit this issue when win2k8 32bit guest running sleep stress with IO during vioserial whql test .
But the failed job was deleted by some mistaken operations ,I will provide cpk file when hit this issue Next time
Comment 6 Mike Cao 2011-12-29 01:45:52 UTC 
Created attachment 549888 [details]
win2k8_32_unexpected_reboot error

the attachment is the cpk file of win2k8 32bit guest when running balloon .job Sleep Stress with IO hit this issue .
win2k8 64bit guest hit this issue too.
Comment 7 Vadim Rozenfeld 2012-01-05 09:18:56 UTC 
Looks like this problem is not related to any particular virtio driver,
but a generic problem mostly related to QEMU/DTM settings or whatever else.

But we need to figure out what's wrong here before we start
intensive WHQL testing.

Vadim.
Comment 8 Mike Cao 2012-02-08 05:35:10 UTC 
(In reply to comment #7)
> Looks like this problem is not related to any particular virtio driver,
> but a generic problem mostly related to QEMU/DTM settings or whatever else.
> 
> But we need to figure out what's wrong here before we start
> intensive WHQL testing.
> 
> Vadim.

FYI, this bug might related to bug https://bugzilla.redhat.com/show_bug.cgi?id=607510
Comment 9 Vadim Rozenfeld 2012-02-08 08:00:19 UTC 
(In reply to comment #8)
> (In reply to comment #7)
> > Looks like this problem is not related to any particular virtio driver,
> > but a generic problem mostly related to QEMU/DTM settings or whatever else.
> > 
> > But we need to figure out what's wrong here before we start
> > intensive WHQL testing.
> > 
> > Vadim.
> 
> FYI, this bug might related to bug
> https://bugzilla.redhat.com/show_bug.cgi?id=607510

Thank you.

Will keep my eyes open on this bug.

Vadim.
Comment 15 Ronen Hod 2012-07-10 09:13:56 UTC 
Mike,

Is this still an issue?
Does it also happen with HCK?

Thanks.
Comment 16 Mike Cao 2012-07-10 13:50:48 UTC 
(In reply to comment #15)
> Mike,
> 
> Is this still an issue?
> Does it also happen with HCK?
> 
> Thanks.

No. shall we close this as worksforme ?

Thanks,
Mike
Comment 17 Mike Cao 2012-08-20 03:09:34 UTC 
FYI ,I found this is a MSFT known issue . Detailed referring to http://msdn.microsoft.com/en-us/library/windows/hardware/hh852378.aspx#X-201205241641326
Power management tests may fail with "Task Cancelled because of an Unexpected Reboot" Error. This error applies to the following tests:

Device Tests:
Sleep and PNP (disable and enable) with IO Before and After (Certification)
Concurrent Hardware And Operating System (CHAOS) Test (Certification)
System Tests:
System - Sleep and PNP (disable and enable) with IO Before and After (Certification)
System - Sleep with IO Before and After (Certification)
Software Device (Filter) Tests:
Sleep and PNP (disable and enable) with IO Before and After (Certification - Software Device)
These tests may not produce any logs, and right clicking on "Run Test" task and clicking on "Error" option may show the following:

Cause: Machine Rebooted Unexpected when Task "Run Test" was running

Failure: Task Cancelled Because of an Unexpected Reboot"

If you see this error, please review event logs under "Windows Logs->System" from Event Viewer. If event logs contain the following log entry, then you may qualify for a manual errata:

"Windows failed to resume from hibernate with error status <status code>"

Please ensure that the log entry is from the precise time when the test was running.

After confirming the exact error string in event logs mentioned above, and confirming the timing of the log entry matches with when the test was running, please submit the HCKX file and event logs so we can manually confirm the same, and accept your submission for processing. Please refer to this note in the README file with the submission.

IMPORTANT: "Task Cancelled Because Of An Unexpected Reboot" error is also seen when the system bugchecks during the test run. This note does NOT apply to the case when the system bugchecks during the test run. If you do not see "Windows failed to resume from hibernate" message in event logs, please rerun the tests with the test system connected to a Kernel Debugger. This will cause the system to break into the debugger if your test system bugchecks during the test run.
Note You need to log in before you can comment on or make changes to this bug.