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 1000104 - W2K8R2-SP1 fails 2 WHQL HCK tests
Summary: W2K8R2-SP1 fails 2 WHQL HCK tests
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-qxl-xddm
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: David Blechter
QA Contact: SPICE QE bug list
URL:
Whiteboard: spice
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-22 17:08 UTC by Bill Sanford
Modified: 2019-10-10 13:51 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-09 20:23:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot of the error message (856.17 KB, image/png)
2013-08-22 17:10 UTC, Bill Sanford
no flags Details

Description Bill Sanford 2013-08-22 17:08:39 UTC
Description of problem:
Testing W2K8R2 SP1 with the new WHQL HCK studio results in two tests that fail. It is my understanding that the two test could be the same root cause and the one fix, will possibly fix both.

The error message in the command window is: 

Error: WDTF_PNP        : Result: Failed to recieve IRP_MN_REMOVE_DEVICE after receiving IRP_MN_SURPRISE_REMOVAL. Ensure that there are no open handlers or references to the test device (in user or kernel mode) preventing IRP_MN_REMOVE_DEVICE from being sent. You may need to terminate any processes or services that may have open user handles to this device.  ( 80004005 )

Version-Release number of selected component (if applicable):
Windows Server 2008 R2 SP1 (VM)
rhev-guest-tools-iso-3.3-3.noarch.rpm
qxl-win-unsigned-0.1-18

How reproducible:
100%

Steps to Reproduce:
1. Start the HCK test suite for QXL
2. Run 2089 Device Path Exerciser Test
3. Run 2079 Plug and Play Driver Test

Actual results:
Tests fail.

Expected results:
Tests pass.

Additional info:

Comment 1 Bill Sanford 2013-08-22 17:10:33 UTC
Created attachment 789279 [details]
Screenshot of the error message

Comment 2 David Blechter 2013-09-19 16:46:35 UTC
No HCK testing for 3.3, all qxl driver should pass WLK.

Moving to the future for now if we will switch to HCK

Comment 5 David Blechter 2015-09-09 20:23:50 UTC
no needs for keeping it for 2 years.

Comment 6 Prabhakar V 2017-10-30 13:29:50 UTC
I have faced this issue on my HLK testing for UART driver...

Im replacing the standard uart and loading my driver...

Could you please anyone help on this to resolve this error...

Im getting sfc verification failed ... got "Opening cbs.log failed! Will re-try after 30 seconds " result was "fail"....


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