Hi
We have a driver package which usually works on W2K3.
We try to adapt it to W2K8.
One of our drivers is a filter driver over an HBA driver (bus filter driver).
When responding to QUERY_DEVICE_RELATIONs, the bus filter driver sometimes adds its own PDOs to the enumeration ("Dummy PDO").
During shutdown of the server we keep getting BSOD 0xa when handling POWER IRP with minor functios SET POWER (2).
The device object is one of our PDOs.
Here is the handling of the power IRPs:
NTSTATUS
FilterDispatchPower(
IN PDEVICE_OBJECT DeviceObject,
IN PIRP Irp
)
{
PDEVICE_EXTENSION deviceExtension;
deviceExtension = (PDEVICE_EXTENSION) DeviceObject->DeviceExtension;
PoStartNextPowerIrp(Irp);
IoSkipCurrentIrpStackLocation(Irp);
return PoCallDriver(deviceExtension->NextLowerDriver, Irp);
}
The NextLowerDriver is the HBA driver device object.
Here is the analyze -v of the BSOD:
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 00000001, Error Handling power IRP.
Arg2: 00000006, The system has failed to allocate a necessary power irp.
Arg3: 9cf0b7b0, target device object
Arg4: 00000001, device power irp
Debugging Details:
BUGCHECK_STR: 0xA0
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82010ada to 820c9759
STACK_TEXT:
ae876a7c 82010ada 000000a0 00000001 00000006 nt!KeBugCheckEx+0x1e
ae876acc 8201364d 9cf0b7b0 00000002 00000001 nt!PopAllocateIrp+0xa0
ae876afc 8327ab9e 9cf0b7b0 00000002 00000004 nt!PoRequestPowerIrp+0x62
ae876b30 8327b57d 9cf0b868 9dd0aa48 00000000 storport!RaidUnitSetSystemPowerIrp+0x55
ae876b50 8327b83c 9cf0b868 9dd0aa48 83281000 storport!RaidUnitSetPowerIrp+0xc4
ae876b6c 832779ef 9cf0b868 00000002 9dd0abac storport!RaUnitPowerIrp+0x9a
ae876b88 82012f45 9cf0b7b0 9dd0aa48 00000016 storport!RaDriverPowerIrp+0x60
ae876ba0 820541bf 9dd0aa48 9cf0b7b0 ae876bb8 nt!IopPoHandleIrp+0x28
ae876bb0 82010a29 ae876bd0 82d46727 9cf0b7b0 nt!IofCallDriver+0x55
ae876bb8 82d46727 9cf0b7b0 9dd0aa48 82d5e750 nt!IoCallDriver+0x10
ae876bd0 82012f45 9c68cd58 9dd0aa48 00000016 saactv!FilterDispatchPower+0x67 [l:\v4r4\svm5\v4r4.39.e2\win_agent\saactive\saactv.c @ 4632]
ae876be8 820541bf 9dd0abd0 9c68cd58 ae876c00 nt!IopPoHandleIrp+0x28
ae876bf8 82010a29 ae876c28 82d28a2f 9c68cd58 nt!IofCallDriver+0x55
ae876c00 82d28a2f 9c68cd58 9dd0aa48 9c7438c0 nt!IoCallDriver+0x10
ae876c28 82d28ac7 9c743808 9dd0abb4 0000000e CLASSPNP!ClasspPowerHandler+0x447
ae876c40 82d275b5 9c743808 9dd0aa48 9dd0abb4 CLASSPNP!ClassSpinDownPowerHandler+0x8c
ae876c5c 82d20342 9c743808 9dd0aa48 9dd0aa48 CLASSPNP!ClassDispatchPower+0x6c
ae876c70 82012f45 9c743808 9dd0aa48 00000016 CLASSPNP!ClassGlobalDispatch+0x20
ae876c88 820541bf 9dd0aa48 9c743808 ae876ca0 nt!IopPoHandleIrp+0x28
ae876c98 82010a29 ae876cb8 82d0cc6a 9c743808 nt!IofCallDriver+0x55
ae876ca0 82d0cc6a 9c743808 9dd0aa48 9b6d3008 nt!IoCallDriver+0x10
ae876cb8 82012f45 9c743600 9dd0aa48 00000016 safilter!SaFilterDispatchPower+0x4a [l:\v4r4\svm5\v4r4.39.e2\win_agent\safilter\filter.c @ 1571]
ae876cd0 820541bf 9c7433b8 9c743600 ae876ce8 nt!IopPoHandleIrp+0x28
ae876ce0 82010a29 ae876d0c 82c87d8d 9c743600 nt!IofCallDriver+0x55
ae876ce8 82c87d8d 9c743600 9dd0aa48 9c743300 nt!IoCallDriver+0x10
ae876d0c 82c85151 01743300 00000000 82112220 partmgr!PmPower+0xa8
ae876d20 82013e5e 9c743300 9dd0aa48 00000000 partmgr!PmGlobalDispatch+0x1d
ae876d7c 821b66d5 8971c2b8 889a8622 00000000 nt!PopIrpWorker+0x40f
ae876dc0 8209d6de 82013a4b 8971c2b8 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
storport!RaidUnitSetSystemPowerIrp+55
8327ab9e bb03010000 mov ebx,103h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: storport!RaidUnitSetSystemPowerIrp+55
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: storport
IMAGE_NAME: storport.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47918f7d
FAILURE_BUCKET_ID: 0xA0_storport!RaidUnitSetSystemPowerIrp+55
BUCKET_ID: 0xA0_storport!RaidUnitSetSystemPowerIrp+55
Followup: MachineOwner
1: kd> !irp 0x9dd0aa48
Irp is active with 9 stacks 7 is current (= 0x9dd0ab90)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[16, 2] 0 e1 9cf0b7b0 00000000 82d2776c-00000000 Success Error Cancel pending
\Driver\ql2300 CLASSPNP!ClasspStartNextPowerIrpCompletion
Args: 00016600 00000000 00000006 00000005
[16, 2] 0 e1 9c743808 00000000 822da7c3-90168178 Success Error Cancel pending
\Driver\disk nt!PopSystemIrpCompletion
Args: 00016600 00000000 00000006 00000005
[0, 0] 0 0 00000000 00000000 00000000-90168178
Args: 00000000 00000000 00000000 00000000
1: kd> dt _IO_STACK_LOCATION 0x9dd0ab90
nt!_IO_STACK_LOCATION
+0x000 MajorFunction : 0x16 ''
+0x001 MinorFunction : 0x2 ''
+0x002 Flags : 0 ''
+0x003 Control : 0xe1 ''
+0x004 Parameters :
+0x014 DeviceObject : 0x9cf0b7b0 _DEVICE_OBJECT
+0x018 FileObject : (null)
+0x01c CompletionRoutine : 0x82d2776c long CLASSPNP!ClasspStartNextPowerIrpCompletion+0
+0x020 Context : (null)
Thanks,
Michael