Bug 1433 - Should be only 1 ACPI interrupt increment.
Summary: Should be only 1 ACPI interrupt increment.
Status: REJECTED INVALID
Alias: None
Product: ACPI
Classification: Unclassified
Component: Config-Interrupts (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Robert Moore
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-27 03:58 UTC by Luming Yu
Modified: 2005-04-27 00:55 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.0-test7,8
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
patch for fixing this issue. (564 bytes, patch)
2003-10-27 04:02 UTC, Luming Yu 		Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Description Luming Yu 2003-10-27 03:58:50 UTC 
Distribution:
RH 9 + base kernel 2.6.0-test7,test8

Hardware Environment:
IBM Thinkpad T21

Problem Description:
If you press fn+F4 , or other function keys, there should be only 1 ACPI
interrupt generated rather than 2.

Steps to reproduce:
a). boot up kernel with full ACPI features.
b). cat /proc/interrupts
....
11:      6        XT-PIC   acpi
....
c). press Fn+F4(or other function keys)
d). cat /proc/interrups
....
11:      8        XT-PIC   acpi
....
Comment 1 Luming Yu 2003-10-27 04:02:24 UTC 
Created attachment 1214 [details]
patch for fixing this issue.
Comment 2 Andy Grover 2003-10-30 10:03:03 UTC 
or can you just call acpi_clear_gpe from ec.c?
Comment 3 Robert Moore 2004-09-22 15:21:54 UTC 
Please explain how this patch fixes the problem.

Also -- with the major GPE changes in mid-2004, this problem *may* have gone 
away.
Comment 4 Len Brown 2004-11-16 23:49:22 UTC 
please verify that this is still a problem in 2.6.9
Comment 5 Luming Yu 2004-12-01 01:45:05 UTC 
I don't have access to T21 now. 
But I have T42. With 2.6.10-rc2, each FN+F4 cause 4 increment.
Comment 6 Robert Moore 2005-03-09 12:25:39 UTC 
Is this still a problem?
Comment 7 Luming Yu 2005-04-27 00:55:13 UTC 
The assumption should be wrong, because it depends on implementation.
Note You need to log in before you can comment on or make changes to this bug.