Bug 2534 - new acpi_wake_gpes_always_on kernel option didn't work
Summary: new acpi_wake_gpes_always_on kernel option didn't work
Alias: None
Product: ACPI
Classification: Unclassified
Component: Config-Interrupts (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Len Brown
Depends on:
Reported: 2004-04-17 16:40 UTC by Hermann Lauer
Modified: 2004-11-14 20:46 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.4.26
Tree: Mainline
Regression: ---

dmesg output (via syslog) (6.15 KB, text/plain)
2004-04-17 16:42 UTC, Hermann Lauer

Description Hermann Lauer 2004-04-17 16:40:08 UTC
Distribution: Debian testing
Hardware Environment:
Software Environment:
Problem Description:

The new "acpi_wake_gpes_always_on" kernel option didn't work. Without these
the LID switch on my laptop did not work any more (has worked with
2.4.25 and apci patches)

As you can see from the attached dmesg output, the kernel option
is recognized:
Apr 17 01:14:53 localhost kernel: ACPI: wake GPEs not disabled

But later on, there are wake GPEs found:

Apr 17 01:14:53 localhost kernel: evgpeblk-0926 [06] ev_create_gpe_block   :
Found 2 Wake, Enabled 1 Runtime GPEs in this block

If I understand linux-2.4.26/drivers/acpi/events/evgpeblk.c correct,
alls gpe are initialised as ACPI_GPE_TYPE_RUNTIME and in line 879ff only if the
"acpi_wake_gpes_always_on" kernel option is not set the GPEs are checked if they
have to be changed to ACPI_GPE_TYPE_WAKE -- so with this option set there should
be no wake GPEs.

Just guessing: maybe acpi_ut_init_globals() is called after 
acpi_wake_gpes_always_on_setup() ?

Thanks for all the work on acpi linux code.
Comment 1 Hermann Lauer 2004-04-17 16:42:48 UTC
Created attachment 2617 [details]
dmesg output (via syslog)
Comment 2 Luming Yu 2004-04-26 20:49:54 UTC
We will release a improved wakeup/runtime GPE implementation soon. 
Comment 3 Len Brown 2004-11-14 20:46:41 UTC
This was fixed early on in 2.4.28: 
and is also available in the 24-stable-release ACPI patch for 2.4.27. 

Note You need to log in before you can comment on or make changes to this bug.