Re: usb device failed to start after the system resumed from hibernation
- From: "fat_boy" <zzebowa@xxxxxxxxxxx>
- Date: 28 Aug 2006 01:26:45 -0700
It looks like your device is failing to respond to the D3->D0
transition called by your S3 -> S0 completion routine (where
PoRequestPowerIrp() for the device is called from)
WilliamX wrote:
Hi,
I encountered a odd issue when testing our device for hibernation. It is a
usb composite device and we developed the the loader with cypress ez-usb.
At first, it is working well, hibernating, resuming, hibernating again,
resuming ... But after about 36 ~ 38 times, the device could not be
started.
At that time, the loader was downloaded, but the renumeration is failed. I
have no idea about this issue.
Could you give me some advice to do the further debug or test?
Let me describe something more for this issue. After failure, regardless
which port I attached the usb device to, it is the same results. It will
be prompted to install driver if the port is fresh for the device, but
after installed, it still did not work. There is a exclamation point
before the device with 'code 10' for the device status in device
managerment. Still in device managerment, I saw the 'Current Power State'
is D3 in details of the device properties page.
After reboot the windows, this issue could be settled and the device
worked well again.
Is there some solution to fix this issue? Or Is there somebody could
explain for me what caused the issue?
Advance thanks, very much.
William
.
- Follow-Ups:
- References:
- Prev by Date: Re: NDIS IM filter driver binding
- Next by Date: Re: Physical memory topology when locking virtual memory
- Previous by thread: usb device failed to start after the system resumed from hibernation
- Next by thread: Re: usb device failed to start after the system resumed from hibernation
- Index(es):
Relevant Pages
|
