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





------- Comment #4 from [EMAIL PROTECTED]  2008-08-12 21:38 -------
I'm not following the comments here...

Re comment #3: the patch from bug 11153 sets up a handler which will take care
of all RTC IRQs, and leaves it registered at all times ... so that the IRQ
enable/disable logic is controlled by updating the relevant RTC control
register.  It also changes the names of the hooks, since their functions have
changed ... so this "debug patch" won't work over that patch.  (Plus it ignores
several cases, like periodic alarms and alarms enabled when the alarm time is
being set.  If that's what you want to do, then the newish cmos_irq_enable and
cmos_irq_disable calls are what should be changed.)

Re comment #2 ... I think that what you're saying is that some systems issue
spurious wakeups, so the handler should be disabled when those systems go to
sleep unless the alarm should be triggering a "real" wakeup.  Is that true?  If
so, it's an issue I'll need to take into account.  BUT if that's your point,
then it's unrelated to bug 11312 (this one), which doesn't involve system sleep
states at all!

THIS bug is the handler spontaneously getting disabled.  No message of any kind
to say why that might have been done.  And in particular, the system did not
enter a sleep state, so it's not a spurious wakeup.

What would cause the RTC event handler to spontaneously become "invalid"?  Over
about six hours of system idleness.


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