On Oct 31, 2006, at 3:34 AM, Amos Waterland wrote:

I have seen this on a Maple now as well:

(XEN) reprogram_timer[00] Timeout in the past 0x00000038879D3833 > 0x00000038879CF88C (XEN) reprogram_timer[00] Timeout in the past 0x0000003887AE47A4 > 0x0000003887AD2018

This usually indicates a problem somewhere.
In this case we tried to set a timer about 432ms in the past (assuming 175MHz which is what my maple runs at). We should stick a WARN() or stack trace back in ths if in reporgram_timer() to figure out which timer it is.
We may just need out own definition of TIMER_SLOP?

Xen-ppc-devel mailing list

Reply via email to