http://bugzilla.kernel.org/show_bug.cgi?id=10932





------- Comment #10 from [EMAIL PROTECTED]  2008-07-08 10:06 -------
Well, I was busy the last weeks, but I had enough time to clone the git 
repository and run some tests. I wanted to run bisect, and so I checked the 
kernel versions 2.6.23, 2.6.24 and 2.6.25 from the repository again. Before 
booting a kernel, I detached the AC adapter and did not plug it in until all 
tests were finished. Then I booted the kernel, pressed FnF4 and resumed a few 
times.

With 2.6.23 the events were dead only few times (about 1 test of 6), using 
2.6.24 about half of the tests failed and with 2.6.25 the machine did never 
receive events after resuming.

Now I don't know how I could bisect the problem, since the issue is also 
existing in 2.6.23 and just became severe in 2.6.24. I may try to bisect the 
problem down to a specific commit, after which the failure rate of 1/6 turns 
into the 1/2 one, but I hardly believe that I will find origin of that 
behaviour.

With CONFIG_X86_UP_APIC and CONFIG_X86_UP_IOAPIC in 2.6.26-rc9 enabled I can
see 
that FnF4 fires gpe0B, after resuming the events are dead and pressing FnF4
does 
not fire a gpe0B anymore. FnF3 does not seem to fire a GPE. The value for gpe09 
is constantly rising, both with working acpi and with acpi being dead. 


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to