Description of problem:
We have a Windows 2012R2 server that will periodically crash and reboot. Microsoft has analyzed the core dump and come back with the following response:
We have got the Dump analyzed and again we have found that it is the same driver (vioser.sys) which has caused the crash.
Here the KMDF Verifier has caught a possible race condition issue in "Red Hat VirtIO Serial driver (vioser.sys)"
Here this driver vioser.sys is completing a cancellable WDFRequest. This driver has a cancellation routine set for the request and it should have called WdfRequestUnmarkCancelable() before calling WdfRequestComplete(). But here the driver hasn't done so. So, after calling WdfRequestUnmarkCancelable() it has to check for the return status from the same routine and do a completion accordingly.
Please refer this msdn document => https://msdn.microsoft.com/en-us/library/windows/hardware/ff549983(v=vs.85).aspx
Last occurrence was on 6/1/2015 at 9:27 AM Eastern from within the Windows guest. RHEV logs will be in UTC.
vioser.sys version 188.8.131.5200
Could you provide a method for QE to reproduce and verify?
(In reply to lijin from comment #14)
> Hi Gal,
> Could you provide a method for QE to reproduce and verify?
Sorry, but I don't know how to reproduce it. The patch that should fix this issue is based only on a code review.
Could you give us a feedback once customer try the fixed version?So that we can make sure this issue is fixed and we may ship it in next official virtio-win package.
Thanks a lot.
From the customer:
We haven't had this issue again since we've updated the driver so it's probably safe to say it was a successful fix at this point. Can we keep this ticket open until this fix makes it into the official driver?
Thanks for your help on this case.
It looks like it was a success. Thank you and let's see about including this in official package.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.