Search results

  1. H

    The "30% CPU at idle because of System + Interrupts" issue

    Here's what I used to get the ACPI trace logs: @echo off logman create trace acpi -ow -o c:\acpi.etl -p "Microsoft-Windows-Kernel-Acpi" 0xffffffffffffffff 0xff -nb 16 16 -bs 1024 -mode 0x2 -max 2048 logman start acpi echo Enter any key to stop tracing... pause logman stop acpi logman...
  2. H

    The "30% CPU at idle because of System + Interrupts" issue

    Since this is a wake GPE, my expectation would be for the OS to enable it just before putting the device to sleep. This GPE might be the same reason why the device wakes up on its own sometimes. If the status bit is stuck and the GPE is enabled when the device is put to sleep, it will probably...
  3. H

    The "30% CPU at idle because of System + Interrupts" issue

    I don't think it's the EC as it appears to be using GPE 0x38. To reproduce this issue in Linux you will have to enable interrupts for GPE 0x6D by writing 'enable' to /sys/firmware/acpi/interrupts/gpe6D and re-insert the SD card. The following GPEs seem to be valid: 0x09, 0x1E, 0x38 (EC), 0x61...
  4. H

    The "30% CPU at idle because of System + Interrupts" issue

    Traces from the Microsoft-Windows-Kernel-Acpi provider are filled with the following types of events while this issue is in effect: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <EventData> <Data Name="GpeRegister">0x0</Data> <Data...
Back
Top