Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: On certain platforms PageGuard is causing resume from Hibernate to take longer than expected #1303

Open
1 task done
Flickdm opened this issue Mar 13, 2025 · 1 comment
Assignees
Labels
state:needs-triage Needs to triaged to determine next steps type:bug Something isn't working urgency:high Significant with a critical impact

Comments

@Flickdm
Copy link
Member

Flickdm commented Mar 13, 2025

Is there an existing issue for this?

  • I have searched existing issues

Current Behavior

On certain platforms, PageGuard is causing Resume from Hibernate to take longer than expected.
Specifically, on my test platform resume took 17s with page guard on and 4s with it disabled.

There are a few factors at play here.

  1. Appears to be reentrant behavior on CpuDxe->SetMemoryAttributes (..) when Page Guard is used
  2. Code is diving into silicon provided code so the fault is not yet clear.

Expected Behavior

Page Guard should not be having a significant impact on resume from hibernate

Steps To Reproduce

  1. Resume from hibernate on a test platform with windows.
  2. Inspect eventlog Event ID 1, source "Power-TroubleShooter" and specifically under "Details" Look for HiberReadDuration
  3. Take note of the HiberReadDuration
  4. Disable PageGuard and reboot
  5. Resume from hibernate
  6. . Inspect eventlog Event ID 1, source "Power-TroubleShooter" and specifically under "Details" Look for HiberReadDuration
  7. Take note of the HiberReadDuration
  8. A significant difference indicates a problem

Build Environment

- OS(s): Windows
- Tool Chain(s): Clang
- Targets Impacted:
  - RELEASE / DEBUG

Version Information

release/202311
release/202405

Urgency

High

Are you going to fix this?

I will fix it

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

@Flickdm Flickdm added state:needs-triage Needs to triaged to determine next steps type:bug Something isn't working labels Mar 13, 2025
@github-actions github-actions bot added the urgency:high Significant with a critical impact label Mar 13, 2025
@makubacki
Copy link
Member

Is it known when this issue started occurring?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:needs-triage Needs to triaged to determine next steps type:bug Something isn't working urgency:high Significant with a critical impact
Projects
None yet
Development

No branches or pull requests

2 participants