Tino Keitel wrote:
On Mon, Dec 01, 2008 at 12:02:06 -0500, Mark Lord wrote:
Mark Lord wrote:
Fix month wrap issue with readback from /proc/acpi/alarm
This bug has been around *forever*.
$ echo '2008-12-01 10:36:20' > /proc/acpi/alarm
$ cat /proc/acpi/alarm
2008-11-01 10:36:20
Note how the readback above shows the month incorrectly.
But with this patch applied, it shows the correct month (12).
..
I should add, that the above test requires that the alarm
be set for any day of the *next* month from the current month.
My MythTV box does a readback test any time it programs a wakeup,
and noticed the bug over this past weekend (2008-11-30).
Why not just use the new RTC drivers and /sys/class/rtc/rtc0/wakealarm?
..
That question has nothing to do with fixing the bug in
the /proc/acpi/alarm code. The bug is still there whether
I personally use a different mechanism or not! :)
But in answer to your question, the new RTC drivers *also* fail
for some other reason. They did work up until the HPET integration
(back in 2.6.26 ?), but have not worked since.
My MythTV box always tries the new ones, and if the readback test
fails to agree with what was attempted, it then falls back to
the old yet more reliable /proc/acpi/alarm.
I haven't really had time to find the exact breakage point and patch it
in the new RTC code yet (I put about 10 hours into it back then,
with no useful result), but the old code does have a useful fix.
Thus this thread.
Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
