http://bugzilla.kernel.org/show_bug.cgi?id=11312
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
------- Comment #8 from [EMAIL PROTECTED] 2008-08-13 01:22 -------
Hi, Dave,
(In reply to comment #6)
> The bug is that the event was wrongly disabled (why?) ...
Agree.
> the ff_rt_clk file is just showing evidence of that failure.
No, there is a bug in the previous code.
The ff_rt_clk is always "invalid" if you have not read this file when it's
enabled. In order to verify the problem, please try the patch in comment #7.
> 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.
With your patch applied, the RTC event should always be enabled. right?
IMO, No ACPI code will disable it any more.
> The bug is that somehow, without my asking for it to be done, the RTC event
> handler was disabled!
I'm not sure about this.
Please retry with the patch applied.
--
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
