[illumos-Developer] "apic_timer_reprogram, request at ... too far in future" in VMware WS VM
Yuri Pankov
yuri.pankov at gmail.com
Sun May 1 21:04:58 PDT 2011
Hi,
>From time to time, I'm getting the following messages flooding my
console (and, eventually messages/dmesg):
[...]
May 2 07:26:58 illumos pcplusmp: [ID 624358 kern.notice] apic_timer_reprogram, request at 169431003906250 too far in future, current time 116670350666438
May 2 07:26:59 illumos pcplusmp: [ID 624358 kern.notice] apic_timer_reprogram, request at 169431003906250 too far in future, current time 116671350816257
May 2 07:26:59 illumos pcplusmp: [ID 624358 kern.notice] apic_timer_reprogram, request at 169431003906250 too far in future, current time 116671360828750
May 2 07:27:00 illumos pcplusmp: [ID 624358 kern.notice] apic_timer_reprogram, request at 169431003906250 too far in future, current time 116672300899495
[...]
I'm not sure how/why it is triggered, usually after a day or two,
workload doesn't seem to matter. The system is question is running
under VMware Workstation 7.1.4 (2/4 CPU cores, 4-8GB RAM, doesn't seem
to make difference).
Any hints on why it's happening or how can I debug it are appreciated. I
see that it's #ifdef'ed DEBUG in uts/i86pc/io/pcplusmp/apic_timer.c, but
knowing the source of problem would still be useful.
TIA,
Yuri
More information about the Developer
mailing list