https://bugzilla.novell.com/show_bug.cgi?id=579932
https://bugzilla.novell.com/show_bug.cgi?id=579932#c93
--- Comment #93 from Andreas Nordal
From http://en.wikipedia.org/wiki/HPET Since HPET compares the actual timer value and the programmed target value on equality rather than "greater or equal", interrupts can be missed if the target time has already passed when the comparator value is written into the chip's register. In the presence of non-maskable interrupts (such as System Management Interrupts) that do not have a hard upper bound on their execution time, this race condition requires time-consuming re-checks of the timer after setup and is hard to avoid completely. The difficulties are exacerbated if the comparator value is not synchronized with the timer immediately, but delayed by one or two ticks, as some chipsets do.
Could it be that the kernel goes to sleep with the alarm clock set to some time in the past? I guess SMI="System Management Interrupt", so that my 549µs SMI latency is relevant. But even if my bios is junk, wouldn't this problem still require a hole in some "time-consuming re-checks of the timer after setup", according to Wikipedia? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.