Win8 HCK test failure for "PCI Root Port Surprise Remove Test (PCI devices only)"

OSR_Community_User · September 27, 2012, 5:15am

Hello,
I have a ACPI logic device (not actual hard device) which provide
some methods. I wrote a ACPI PnP WDM driver and expose a control device
object for user app’s IOCTL communication. Our driver is almost 99% same as
WDK’s sample code src\general\toaster\wdm\filter except a IOCTL is added
for invoke ACPI method. The driver pass Win7 WHQL testing.

But when I testing driver on win8’s HCK, I got failures as:

For X86
One of “PCI Root Port Surprise Remove Test (PCI devices only)” is
failed, error log is “Failed to receive IRP_MN_REMOVE_DEVICE after
receiving IRP_MN_SURPRISE_REMOVAL”.
For X64:
When running “PCI Root Port Surprise Remove Test”, BSOD is given
for ACPI.sys driver.The error stack is in below.

My questions:
1, Why our driver pass win7 WHQL but can not pass win8?
2, Our driver is major for ACPI logic device but not real hardware,
do we really need “PCI Root Port Surprise Remove Test”?

==========================
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at
an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880012385d3, address which referenced memory

Debugging Details:

READ_ADDRESS: 0000000000000000

fffff880`0305a7c8 fffff800`ff105369 : 00000000`0000000a 00000000`00000000
00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0305a7d0 fffff800`ff103be0 : 00000000`00000000 fffffa80`04fa7400
00000000`00000000 fffff880`0305a910 : nt!KiBugCheckDispatch+0x69
fffff880`0305a910 fffff880`012385d3 : fffffa80`04fa7400 00000000`00164d12
fffffa80`04fa7460 00000000`00000019 : nt!KiPageFault+0x260
fffff880`0305aaa0 fffff880`012312de : fffffa80`04fa7400 fffffa80`04fa7400
fffffa80`04fa7490 00000000`00000018 : ACPI!ACPIVectorDisable+0xf
fffff880`0305aad0 fffff880`01230a23 : 00000000`00000001 fffffa80`04fa7458
00000000`00008004 00000000`000007ff : ACPI!ACPIEcServiceDevice+0x92
fffff880`0305ab00 fffff880`01230aa9 : 00000000`00000001 fffffa80`088b3ba0
00000000`00000040 fffff880`01210c64 : ACPI!ACPIEcQueueEcIrp+0x11f
fffff880`0305ab40 fffff880`01216f0b : fffffa80`04f2b228 00000000`00000001
00000000`00000040 fffffa80`088b3b68 : ACPI!ACPIEcOpRegionHandler+0x4d
fffff880`0305ab90 fffff880`01216638 : fffffa80`088b3b68 00000000`00000000
00000000`00000000 fffff880`012128ab : ACPI!InternalOpRegionHandler+0x8f
fffff880`0305abe0 fffff880`0120cafe : fffffa80`088a4000 00000000`00000000
00000000`00008000 00000000`00000000 : ACPI!WriteCookAccess+0x1d4

–

Ken

Peter_Viscarola_OSR · September 27, 2012, 10:01am

Because the tests have changed?

Note that in the title of the test it says “(PCI devices only)” – This would mean, no… you do not have to pass this test because you are not writing a driver for a PCI device.

BUT… your driver ALSO shouldn’t Blue Screen on this test. That’s very odd.

I hope somebody with specific experience with this test will comment…

Peter
OSR

OSR_Community_User · September 27, 2012, 9:10pm

Thanks Peter’s answer.

Today, I used pnptest from WinDDK 7600.16385.1(windows7) to test my ACPI
driver. Because in pnptest, there is a test for “Test Surprise Removal”.
I selected my device XXX from ACPI category and click “Test Surprise
Removal”. It reports “ACPI\XXX can not be disabled -so Surprise Remove test
is being skipped”.
In simple words, I guess “surprise remove” test is skipped in windows 7
WHQL testing for my driver.

But why “Surprise remove” testing exist in Win8 HCK test for my device?

K

2012/9/27

>

>
> Because the tests have changed?
>
>

>
> Note that in the title of the test it says “(PCI devices only)” – This
> would mean, no… you do not have to pass this test because you are not
> writing a driver for a PCI device.
>
> BUT… your driver ALSO shouldn’t Blue Screen on this test. That’s very
> odd.
>
> I hope somebody with specific experience with this test will comment…
>
> Peter
> OSR
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

–

Best Regard
Ken
------------------
Hear and you forget; see and you remember; do and you understand.