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





------- Comment #6 from [EMAIL PROTECTED]  2008-08-12 23:56 -------
The bug is that the event was wrongly disabled (why?) ... the ff_rt_clk file is
just showing evidence of that failure.  The first 166 interrupts arrived just
fine, then something changed ... so that the next interrupt (never mind
thousands of later interrupts!) would never be delivered.

I get the point that, because of bugs in certain ACPI implementations, the RTC
event handler should be disabled when it's not needed.  That might make for a
somewhat simpler patch (for bug 11153) ... assuming I can enable/disable ACPI
event handlers in normal contexts.  (Sleeping will generally be a no-no...)

The goal here is to have all RTC interrupts delivered through ACPI, so that we
get real interrupts even when HPET "legacy replacement mode" is interfering
with normal irq 8 routing.  So the current patch treats it exactly like a
normal IRQ handler:  initialized and left active at all times.  (And never
disabled...)  That works for alarm interrupts, once-per-second update
interrupts, and 2^N Hz "periodic" interrupts.

The bug is that somehow, without my asking for it to be done, the RTC event
handler was disabled!  So the driver never again received its interrupts.  What
disabled it?  Why?  Would it ever re-enable it, to match the state that the IRQ
was left in by the driver?


-- 
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.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to