USB crash on IRP_MN_SET_POWER during shutdown.

During massive QA testing, some of machines (Windows 7) USB crash on
IRP_MN_SET_POWER when system shutdown. The crash is hard to reproduce. But
the problem is in there. The dump file result is as follow:

0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 8a471030, Physical Device Object of the stack
Arg3: 82f5eae0, Functional Device Object of the stack
Arg4: ad00cc30, The blocked IRP

Debugging Details:

DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: ad00cc30

DEVICE_OBJECT: 8a471030

DRIVER_OBJECT: 87c5fd48

IMAGE_NAME: usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c81c5d0

MODULE_NAME: usbhub

FAULTING_MODULE: 93c2d000 usbhub

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 82e726b2 to 82f165c4

STACK_TEXT:
82f5ea94 82e726b2 0000009f 00000003 8a471030 nt!KeBugCheckEx+0x1e
82f5eb00 82e71f46 82f5ebac 00000000 82f6b380 nt!PopCheckIrpWatchdog+0x1f5
82f5eb38 82eb542d 82f79aa0 00000000 977f7d18 nt!PopCheckForIdleness+0x73
82f5eb7c 82eb53d1 82f61d20 82f5eca8 00000001 nt!KiProcessTimerDpcTable+0x50
82f5ec68 82eb528e 82f61d20 82f5eca8 00000000
nt!KiProcessExpiredTimerList+0x101
82f5ecdc 82eb360e 0001638b 8a46b930 82f6b380 nt!KiTimerExpiration+0x25c
82f5ed20 82eb3438 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82f5ed24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_IMAGE_usbhub.sys

BUCKET_ID: 0x9F_IMAGE_usbhub.sys

The blocked IRP is actually in this thread:

THREAD aa2266e8 Cid 0004.1614 Teb: 00000000 Win32Thread: 00000000
WAIT: (Executive) KernelMode Non-Alertable
97d5d9d4 NotificationEvent
IRP List:
84f50288: (0006,01d8) Flags: 00060000 Mdl: 00000000
Not impersonating
DeviceMap 89c088d8
Owning Process 84ddf708 Image: System
Attached Process N/A Image: N/A
Wait Start TickCount 15011 Ticks: 76008
(0:00:19:45.732)
Context Switch Count 15
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address nt!PopIrpWorker (0x82e424d3)
Stack Init 97d5dfd0 Current 97d5d8b8 Base 97d5e000 Limit 97d5b000
Call 0
Priority 13 BasePriority 13 UnusualBoost 0 ForegroundBoost 0
IoPriority 2 PagePriority 5
ChildEBP RetAddr Args to Child
97d5d8d0 82eb9ee5 aa2266e8 00000000 8af09120 nt!KiSwapContext+0x26
(FPO: [Uses EBP] [0,0,4])
97d5d908 82eb87e3 aa2267a8 aa2266e8 97d5d9d4 nt!KiSwapThread+0x266
97d5d930 82eb26cf aa2266e8 aa2267a8 00000000
nt!KiCommitThreadWait+0x1df
97d5d9ac 93c2f6f2 97d5d9d4 00000000 00000000
nt!KeWaitForSingleObject+0x393
97d5d9f4 93c2f8de 8a404028 97d5da2c 97d5da20
usbhub!UsbhSyncSendCommand+0x1ac (FPO: [6,8,4])
97d5da38 93c4660a 8a404028 00000008 97d5da60
usbhub!UsbhQueryPortState+0xcc (FPO: [4,6,4])
97d5da68 93c46900 8a47146c 8a471030 8a471401
usbhub!UsbhSyncSuspendPdoPort+0x7c (FPO: [3,3,4])
97d5da8c 93c44b1a 8a471401 00000004 ad00cc30
usbhub!UsbhPdoSetDx+0x1e7 (FPO: [3,1,4])
97d5dab8 93c45125 8a404028 8a471030 ad00cc30
usbhub!UsbhPdoDevicePowerState+0x174 (FPO: [3,3,4])
97d5dad8 93c2eb92 8a471030 ad00cc30 ad00cc30
usbhub!UsbhPdoPower_SetPower+0x99 (FPO: [2,0,4])
97d5daec 82e42d17 8a471030 ad00cc30 00000016
usbhub!UsbhGenDispatch+0x4a (FPO: [2,0,4])
97d5db04 82e72b0c ad00cddc 8a471030 97d5db1c nt!IopPoHandleIrp+0x28
97d5db14 82e4504a 97d5db3c 888a8e67 8a471030 nt!IofCallDriver+0x55
97d5db1c 888a8e67 8a471030 ad00cc30 ad00cc30 nt!IoCallDriver+0x10
97d5db3c 888a7642 8787a3b8 00000000 8a475550
ACPI!ACPIFilterIrpSetPower+0x119 (FPO: [2,1,4])
97d5db6c 82e42d17 8787a3b8 856bfe60 00000016
ACPI!ACPIDispatchIrp+0x198 (FPO: [2,5,4])
97d5db84 82e72b0c 00000000 8787a3b8 97d5db9c nt!IopPoHandleIrp+0x28
97d5db94 82e4504a 97d5dbb8 93dad880 8787a3b8 nt!IofCallDriver+0x55
97d5db9c 93dad880 8787a3b8 ad00cc30 8a475550 nt!IoCallDriver+0x10
97d5dbb8 93dadc89 8a475550 ad00cc30 ad00cc30
usbccgp!DispatchFdoSetPower+0x1ce (FPO: [2,0,4])
97d5dbd4 93db68ba 8a475550 ad00cde4 ad00cc30
usbccgp!DispatchFdoPower+0x133 (FPO: [2,0,4])
97d5dbec 93da7620 8a475548 ad00cc30 8a474420 usbccgp!USBC_Power+0x68
(FPO: [2,0,0])
97d5dc1c 82e42d17 8a475490 0100cc30 00000016
usbccgp!USBC_Dispatch+0x1c6 (FPO: [2,5,4])
97d5dc34 82e72b0c ad00cc30 8a475490 97d5dc4c nt!IopPoHandleIrp+0x28
97d5dc44 82e4504a 97d5dcf8 889ab7be 8a475490 nt!IofCallDriver+0x55
97d5dc4c 889ab7be 8a475490 ad00cc30 ad00cc30 nt!IoCallDriver+0x10
97d5dcf8 82e42824 8a474368 ad00cc30 00000000
Filter!DispatchPower+0x12a (FPO: [Non-Fpo]) (CONV: stdcall)
97d5dd50 83046f9b 87b74688 8d064d55 00000000 nt!PopIrpWorker+0x351
97d5dd90 82ef9ae9 82e424d3 87b74688 00000000
nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

The filter driver in stack does not act as power policy owner at all, it
only passes down what it gets to USB stack. The blocked IRP also shows
filter driver doesn’t hold the IRP:

0: kd> !irp ad00cc30 1
Irp is active with 11 stacks 8 is current (= 0xad00cd9c)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
Flags = 00000000
ThreadListEntry.Flink = ad00cc40
ThreadListEntry.Blink = ad00cc40
IoStatus.Status = c00000bb
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = ad00cc70
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = 82f794f8
Tail.Overlay.ListEntry.Blink = 82f794f8
Tail.Overlay.CurrentStackLocation = ad00cd9c
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
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
[0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000

[16, 2] 0 e0 8a471030 00000000 888a6e32-888a652a Success Error Cancel
\Driver\usbhub ACPI!ACPIDeviceIrpDeviceFilterRequest
Args: 00016600 00000001 00000004 00000006
[16, 2] 0 e1 8787a3b8 00000000 82ec32d6-8a4fbc48 Success Error Cancel
pending
\Driver\ACPI nt!IopUnloadSafeCompletion
Args: 00016600 00000001 00000004 00000006
[16, 2] 0 e1 8a475490 00000000 82ec32d6-87a01630 Success Error Cancel
pending
\Driver\usbccgp nt!IopUnloadSafeCompletion
Args: 00016600 00000001 00000004 00000006
[0, 0] 0 0 00000000 00000000 00000000-aa2c2920

Args: 00000000 00000000 00000000 00000000
0: kd> dt nt!_IO_STACK_LOCATION 0xad00cd9c
+0x000 MajorFunction : 0x16 ‘’
+0x001 MinorFunction : 0x2 ‘’
+0x002 Flags : 0 ‘’
+0x003 Control : 0xe0 ‘’
+0x004 Parameters :
+0x000 Power :
+0x000 SystemContext : 0x16600
+0x000 SystemPowerStateContext : _SYSTEM_POWER_STATE_CONTEXT
+0x000 Reserved1 : 0y00000000 (0)
+0x000 TargetSystemState : 0y0110
+0x000 EffectiveSystemState : 0y0110
+0x000 CurrentSystemState : 0y0001
+0x000 IgnoreHibernationPath : 0y0
+0x000 PseudoTransition : 0y0
+0x000 Reserved2 : 0y0000000000 (0)
+0x000 ContextAsUlong : 0x16600
+0x004 Type : 1 ( DevicePowerState )
+0x008 State : _POWER_STATE
+0x000 SystemState : 4 ( PowerSystemSleeping3 )
+0x000 DeviceState : 4 ( PowerDeviceD3 )
+0x014 DeviceObject : 0x8a471030 _DEVICE_OBJECT
+0x018 FileObject : (null)
+0x01c CompletionRoutine : 0x888a6e32 long
ACPI!ACPIDeviceIrpDeviceFilterRequest+0
+0x020 Context : 0x888a652a

I think USB is attempting to suspend the port during the power management
transition but the synchronous
suspend operation doesn’t complete in specific time. However, I can’t find
why that suspend opertion can’t
be finished so that the IRP is blocked in that thread.
Is this because USB port on their system that is not responding to power
transition request appropriately or some
other drivers block that irp?

Any suggestion?

> Any suggestion?

Report it to MS via PSS. It is somewhat “normal” since XP times; power IRPs are sometimes blocked in USB stack and this BSOD follows. Win7 are much better than XP (even with SP3) in this aspect but as you can see, some bugs still remain.

Michal

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-462328-
xxxxx@lists.osr.com] On Behalf Of David Wu
Sent: Thursday, June 30, 2011 2:21 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] USB crash on IRP_MN_SET_POWER during shutdown.

During massive QA testing, some of machines (Windows 7) USB crash on
IRP_MN_SET_POWER when system shutdown. The crash is hard to
reproduce. But
the problem is in there. The dump file result is as follow:

0: kd> !analyze -v
**********************************************************
*********************
*
*
* Bugcheck Analysis
*
*
*
**********************************************************
*********************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 8a471030, Physical Device Object of the stack
Arg3: 82f5eae0, Functional Device Object of the stack
Arg4: ad00cc30, The blocked IRP

Debugging Details:

DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: ad00cc30

DEVICE_OBJECT: 8a471030

DRIVER_OBJECT: 87c5fd48

IMAGE_NAME: usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c81c5d0

MODULE_NAME: usbhub

FAULTING_MODULE: 93c2d000 usbhub

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 82e726b2 to 82f165c4

STACK_TEXT:
82f5ea94 82e726b2 0000009f 00000003 8a471030 nt!KeBugCheckEx+0x1e
82f5eb00 82e71f46 82f5ebac 00000000 82f6b380
nt!PopCheckIrpWatchdog+0x1f5
82f5eb38 82eb542d 82f79aa0 00000000 977f7d18
nt!PopCheckForIdleness+0x73
82f5eb7c 82eb53d1 82f61d20 82f5eca8 00000001
nt!KiProcessTimerDpcTable+0x50
82f5ec68 82eb528e 82f61d20 82f5eca8 00000000
nt!KiProcessExpiredTimerList+0x101
82f5ecdc 82eb360e 0001638b 8a46b930 82f6b380 nt!KiTimerExpiration+0x25c
82f5ed20 82eb3438 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82f5ed24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_IMAGE_usbhub.sys

BUCKET_ID: 0x9F_IMAGE_usbhub.sys

The blocked IRP is actually in this thread:

THREAD aa2266e8 Cid 0004.1614 Teb: 00000000 Win32Thread: 00000000
WAIT: (Executive) KernelMode Non-Alertable
97d5d9d4 NotificationEvent
IRP List:
84f50288: (0006,01d8) Flags: 00060000 Mdl: 00000000
Not impersonating
DeviceMap 89c088d8
Owning Process 84ddf708 Image: System
Attached Process N/A Image: N/A
Wait Start TickCount 15011 Ticks: 76008
(0:00:19:45.732)
Context Switch Count 15
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address nt!PopIrpWorker (0x82e424d3)
Stack Init 97d5dfd0 Current 97d5d8b8 Base 97d5e000 Limit 97d5b000
Call 0
Priority 13 BasePriority 13 UnusualBoost 0 ForegroundBoost 0
IoPriority 2 PagePriority 5
ChildEBP RetAddr Args to Child
97d5d8d0 82eb9ee5 aa2266e8 00000000 8af09120
nt!KiSwapContext+0x26
(FPO: [Uses EBP] [0,0,4])
97d5d908 82eb87e3 aa2267a8 aa2266e8 97d5d9d4
nt!KiSwapThread+0x266
97d5d930 82eb26cf aa2266e8 aa2267a8 00000000
nt!KiCommitThreadWait+0x1df
97d5d9ac 93c2f6f2 97d5d9d4 00000000 00000000
nt!KeWaitForSingleObject+0x393
97d5d9f4 93c2f8de 8a404028 97d5da2c 97d5da20
usbhub!UsbhSyncSendCommand+0x1ac (FPO: [6,8,4])
97d5da38 93c4660a 8a404028 00000008 97d5da60
usbhub!UsbhQueryPortState+0xcc (FPO: [4,6,4])
97d5da68 93c46900 8a47146c 8a471030 8a471401
usbhub!UsbhSyncSuspendPdoPort+0x7c (FPO: [3,3,4])
97d5da8c 93c44b1a 8a471401 00000004 ad00cc30
usbhub!UsbhPdoSetDx+0x1e7 (FPO: [3,1,4])
97d5dab8 93c45125 8a404028 8a471030 ad00cc30
usbhub!UsbhPdoDevicePowerState+0x174 (FPO: [3,3,4])
97d5dad8 93c2eb92 8a471030 ad00cc30 ad00cc30
usbhub!UsbhPdoPower_SetPower+0x99 (FPO: [2,0,4])
97d5daec 82e42d17 8a471030 ad00cc30 00000016
usbhub!UsbhGenDispatch+0x4a (FPO: [2,0,4])
97d5db04 82e72b0c ad00cddc 8a471030 97d5db1c
nt!IopPoHandleIrp+0x28
97d5db14 82e4504a 97d5db3c 888a8e67 8a471030 nt!IofCallDriver+0x55
97d5db1c 888a8e67 8a471030 ad00cc30 ad00cc30 nt!IoCallDriver+0x10
97d5db3c 888a7642 8787a3b8 00000000 8a475550
ACPI!ACPIFilterIrpSetPower+0x119 (FPO: [2,1,4])
97d5db6c 82e42d17 8787a3b8 856bfe60 00000016
ACPI!ACPIDispatchIrp+0x198 (FPO: [2,5,4])
97d5db84 82e72b0c 00000000 8787a3b8 97d5db9c
nt!IopPoHandleIrp+0x28
97d5db94 82e4504a 97d5dbb8 93dad880 8787a3b8 nt!IofCallDriver+0x55
97d5db9c 93dad880 8787a3b8 ad00cc30 8a475550 nt!IoCallDriver+0x10
97d5dbb8 93dadc89 8a475550 ad00cc30 ad00cc30
usbccgp!DispatchFdoSetPower+0x1ce (FPO: [2,0,4])
97d5dbd4 93db68ba 8a475550 ad00cde4 ad00cc30
usbccgp!DispatchFdoPower+0x133 (FPO: [2,0,4])
97d5dbec 93da7620 8a475548 ad00cc30 8a474420
usbccgp!USBC_Power+0x68
(FPO: [2,0,0])
97d5dc1c 82e42d17 8a475490 0100cc30 00000016
usbccgp!USBC_Dispatch+0x1c6 (FPO: [2,5,4])
97d5dc34 82e72b0c ad00cc30 8a475490 97d5dc4c nt!IopPoHandleIrp+0x28
97d5dc44 82e4504a 97d5dcf8 889ab7be 8a475490 nt!IofCallDriver+0x55
97d5dc4c 889ab7be 8a475490 ad00cc30 ad00cc30 nt!IoCallDriver+0x10
97d5dcf8 82e42824 8a474368 ad00cc30 00000000
Filter!DispatchPower+0x12a (FPO: [Non-Fpo]) (CONV: stdcall)
97d5dd50 83046f9b 87b74688 8d064d55 00000000
nt!PopIrpWorker+0x351
97d5dd90 82ef9ae9 82e424d3 87b74688 00000000
nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000
nt!KiThreadStartup+0x19

The filter driver in stack does not act as power policy owner at all, it
only passes down what it gets to USB stack. The blocked IRP also shows
filter driver doesn’t hold the IRP:

0: kd> !irp ad00cc30 1
Irp is active with 11 stacks 8 is current (= 0xad00cd9c)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
Flags = 00000000
ThreadListEntry.Flink = ad00cc40
ThreadListEntry.Blink = ad00cc40
IoStatus.Status = c00000bb
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = ad00cc70
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = 82f794f8
Tail.Overlay.ListEntry.Blink = 82f794f8
Tail.Overlay.CurrentStackLocation = ad00cd9c
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
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
[0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
>[16, 2] 0 e0 8a471030 00000000 888a6e32-888a652a Success Error Cancel
\Driver\usbhub ACPI!ACPIDeviceIrpDeviceFilterRequest
Args: 00016600 00000001 00000004 00000006
[16, 2] 0 e1 8787a3b8 00000000 82ec32d6-8a4fbc48 Success Error Cancel
pending
\Driver\ACPI nt!IopUnloadSafeCompletion
Args: 00016600 00000001 00000004 00000006
[16, 2] 0 e1 8a475490 00000000 82ec32d6-87a01630 Success Error Cancel
pending
\Driver\usbccgp nt!IopUnloadSafeCompletion
Args: 00016600 00000001 00000004 00000006
[0, 0] 0 0 00000000 00000000 00000000-aa2c2920

Args: 00000000 00000000 00000000 00000000
0: kd> dt nt!_IO_STACK_LOCATION 0xad00cd9c
+0x000 MajorFunction : 0x16 ‘’
+0x001 MinorFunction : 0x2 ‘’
+0x002 Flags : 0 ‘’
+0x003 Control : 0xe0 ‘’
+0x004 Parameters :
> +0x000 Power :
> +0x000 SystemContext : 0x16600
> +0x000 SystemPowerStateContext : _SYSTEM_POWER_STATE_CONTEXT
> +0x000 Reserved1 : 0y00000000 (0)
> +0x000 TargetSystemState : 0y0110
> +0x000 EffectiveSystemState : 0y0110
> +0x000 CurrentSystemState : 0y0001
> +0x000 IgnoreHibernationPath : 0y0
> +0x000 PseudoTransition : 0y0
> +0x000 Reserved2 : 0y0000000000 (0)
> +0x000 ContextAsUlong : 0x16600
> +0x004 Type : 1 ( DevicePowerState )
> +0x008 State : _POWER_STATE
> +0x000 SystemState : 4 ( PowerSystemSleeping3 )
> +0x000 DeviceState : 4 ( PowerDeviceD3 )
> +0x014 DeviceObject : 0x8a471030 _DEVICE_OBJECT
> +0x018 FileObject : (null)
> +0x01c CompletionRoutine : 0x888a6e32 long
> ACPI!ACPIDeviceIrpDeviceFilterRequest+0
> +0x020 Context : 0x888a652a
>
> I think USB is attempting to suspend the port during the power management
> transition but the synchronous
> suspend operation doesn’t complete in specific time. However, I can’t find
> why that suspend opertion can’t
> be finished so that the IRP is blocked in that thread.
> Is this because USB port on their system that is not responding to power
> transition request appropriately or some
> other drivers block that irp?
>
> Any suggestion?
>
>
> —
> 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

NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately.
Thank You!
AuthenTec, Inc. http://www.authentec.com/