D0Entry on resumption from Hibernation

Hi all,

Upon resumption from Hibernation, I see that my driver doesn’t get a D0Entry notification. Instead I see that the driver is getting a surprise removal notification. As per MSDN links, I see that upon failure from D0Entry, surprise removal gets invoked.

However, I in my case I see the D0Entry itself isn’t getting invoked. What could be the possible reasons for D0Entry “not” getting called and for surprise removal getting invoke?

thanks,
Vishnu

What kind of device is it? USB based ? Does it support D3Cold?

I have seen it on a platform which supports D3Cold. D3Cold device need
support from BIOS\ACPI to go D3Cold. While resuming from Hibernation if
BIOS\ACPI doed not turn on device correctly you may see this issue.

Refer this link details
https://msdn.microsoft.com/en-us/library/windows/hardware/ff543186(v=vs.85).aspx

Not sure if it matches what you looking for!

On Thu, Jul 13, 2017 at 7:05 PM, xxxxx@gmail.com <
xxxxx@lists.osr.com> wrote:

Hi all,

Upon resumption from Hibernation, I see that my driver doesn’t get a
D0Entry notification. Instead I see that the driver is getting a surprise
removal notification. As per MSDN links, I see that upon failure from
D0Entry, surprise removal gets invoked.

However, I in my case I see the D0Entry itself isn’t getting invoked. What
could be the possible reasons for D0Entry “not” getting called and for
surprise removal getting invoke?

thanks,
Vishnu


NTDEV is sponsored by OSR

Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

How are you verifying D0entry is not being called? Debug print statements are not sufficient as there may be lost prints when resuming. What does the wdf log say?

Bent from my phone


From: xxxxx@lists.osr.com on behalf of Sunil Kumar
Sent: Thursday, July 13, 2017 5:26:40 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] D0Entry on resumption from Hibernation

What kind of device is it? USB based ? Does it support D3Cold?

I have seen it on a platform which supports D3Cold. D3Cold device need support from BIOS\ACPI to go D3Cold. While resuming from Hibernation if BIOS\ACPI doed not turn on device correctly you may see this issue.

Refer this link details
https://msdn.microsoft.com/en-us/library/windows/hardware/ff543186(v=vs.85).aspxhttps:

Not sure if it matches what you looking for!

On Thu, Jul 13, 2017 at 7:05 PM, xxxxx@gmail.commailto:xxxxx > wrote:
Hi all,

Upon resumption from Hibernation, I see that my driver doesn’t get a D0Entry notification. Instead I see that the driver is getting a surprise removal notification. As per MSDN links, I see that upon failure from D0Entry, surprise removal gets invoked.

However, I in my case I see the D0Entry itself isn’t getting invoked. What could be the possible reasons for D0Entry “not” getting called and for surprise removal getting invoke?

thanks,
Vishnu


NTDEV is sponsored by OSR

Visit the list online at: http:>

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:>

To unsubscribe, visit the List Server section of OSR Online at http:>

— NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers! Details at To unsubscribe, visit the List Server section of OSR Online at</http:></http:></http:></mailto:xxxxx></https:>