* Possible hint for "Clocksource tsc unstable" problem
@ 2011-10-18 15:00 Andreas Kinzler
2011-10-18 17:41 ` Dan Magenheimer
[not found] ` <FF93AF260AC2BB499A119CC65B092CF7311817E2@sg000713.corproot.net>
0 siblings, 2 replies; 4+ messages in thread
From: Andreas Kinzler @ 2011-10-18 15:00 UTC (permalink / raw)
To: xen-devel
Hello,
I made an interesting observation related to the "Clocksource tsc
unstable (delta = -2999660320319 ns)" problem. In the log of ntpd I found:
Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status
change 6001
Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status
change 2001
Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status
change 6001
Oct 5 05:46:09 greenville-dom0 ntpd[4020]: kernel time sync status
change 2001
Oct 5 06:54:30 greenville-dom0 ntpd[4020]: synchronized to
192.53.103.104, stratum 1
Oct 5 06:54:30 greenville-dom0 ntpd[4020]: kernel time sync status
change 6001
Oct 5 07:28:22 greenville-dom0 ntpd[4020]: kernel time sync status
change 2001
Oct 5 08:19:35 greenville-dom0 ntpd[4020]: synchronized to
192.53.103.108, stratum 1
Oct 5 10:53:26 greenville-dom0 ntpd[4020]: kernel time sync status
change 6001
Oct 5 11:27:32 greenville-dom0 ntpd[4020]: kernel time sync status
change 2001
Oct 5 12:01:41 greenville-dom0 ntpd[4020]: kernel time sync status
change 6001
Oct 5 12:18:44 greenville-dom0 ntpd[4020]: kernel time sync status
change 2001
Oct 5 13:09:58 greenville-dom0 ntpd[4020]: kernel time sync status
change 6001
Oct 5 13:27:04 greenville-dom0 ntpd[4020]: kernel time sync status
change 2001
Oct 5 15:26:37 greenville-dom0 ntpd[4020]: kernel time sync status
change 6001
Oct 5 15:43:41 greenville-dom0 ntpd[4020]: kernel time sync status
change 2001
Oct 5 17:43:11 greenville-dom0 ntpd[4020]: kernel time sync status
change 6001
Oct 5 19:08:31 greenville-dom0 ntpd[4020]: synchronized to
192.53.103.104, stratum 1
Oct 5 19:08:31 greenville-dom0 ntpd[4020]: kernel time sync status
change 2001
Oct 5 21:23:58 greenville-dom0 ntpd[4020]: no servers reachable
Oct 5 21:40:58 greenville-dom0 ntpd[4020]: synchronized to
192.53.103.104, stratum 1
Oct 5 21:40:58 greenville-dom0 ntpd[4020]: time correction of -3000
seconds exceeds sanity limit (1000); set clock manually to the correct
UTC time.
I had the problem twice on different machines but everytime I saw the
line "no servers reachable". Could ntpd and/or linux kernel make some
stupid stuff when ntp upstream servers are unreachable?
Regards Andreas
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Possible hint for "Clocksource tsc unstable" problem
2011-10-18 15:00 Possible hint for "Clocksource tsc unstable" problem Andreas Kinzler
@ 2011-10-18 17:41 ` Dan Magenheimer
[not found] ` <FF93AF260AC2BB499A119CC65B092CF7311817E2@sg000713.corproot.net>
1 sibling, 0 replies; 4+ messages in thread
From: Dan Magenheimer @ 2011-10-18 17:41 UTC (permalink / raw)
To: Andreas Kinzler, xen-devel
> I had the problem twice on different machines but everytime I saw the
> line "no servers reachable". Could ntpd and/or linux kernel make some
> stupid stuff when ntp upstream servers are unreachable?
Can you reproduce it by disconnecting the LAN and/or
somehow blocking the route to your ntp server?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Possible hint for "Clocksource tsc unstable" problem
[not found] ` <CABx4GKo7CBCW6cn49Kr2O+NTm78ms7Xnh_ub1EZ7pdt+Cmp=Lg@mail.gmail.com>
@ 2011-12-02 19:53 ` Andreas Kinzler
2011-12-07 7:13 ` Philippe.Simonet
0 siblings, 1 reply; 4+ messages in thread
From: Andreas Kinzler @ 2011-12-02 19:53 UTC (permalink / raw)
To: xen-devel; +Cc: tp, Olivier Hanesse, Philippe.Simonet
On 01.12.2011 08:49, Olivier Hanesse wrote:
> good news !
> Is your "test system" the same hardware as before ?
> For example, I don't have time issue with processor having the
> 'nonstop_tsc' flag.
> I got only time issue on older processor (Xeon L5420 for example)
Sorry, but my report was on a machine with Xeon E5620 (has nonstop_tsc).
I did some tests to reproduce the behavior by blocking NTP traffic via
iptables but the problem did not reproduce in a lab setting.
Regards Andreas
> *From:*Olivier Hanesse [mailto:olivier.hanesse@gmail.com
> <mailto:olivier.hanesse@gmail.com>]
> *Sent:* Wednesday, October 19, 2011 2:48 PM
> *To:* Thomas Pöhler
> *Cc:* Simonet Philippe, ITS-SDL-EIS-CNV-DLE-TLC; ml-xen-devel@hfp.de
> <mailto:ml-xen-devel@hfp.de>
> *Subject:* Re: [Xen-devel] Possible hint for "Clocksource tsc
> unstable" problem____
>
> __ __
>
> Hi,____
>
> __ __
>
> Same here.____
>
> I am using ntpd in dom0 too (lenny version so 4.2.4)____
>
> __ __
>
> Regards____
>
> __ __
>
> Olivier____
>
> __ __
>
> 2011/10/19 Thomas Pöhler <tp@turtle-entertainment.de
> <mailto:tp@turtle-entertainment.de>>____
>
> Hi Philippe,
>
> we are using ntpd in Dom0 too. (also ntpd - NTP daemon program -
> Ver. 4.2.6p2).
> We are monitoring ntp over a nagios plugin, check_ntp
>
> Regards
> Thomas
>
> -----Ursprüngliche Nachricht-----
> Von: Philippe.Simonet@swisscom.com
> <mailto:Philippe.Simonet@swisscom.com>
> [mailto:Philippe.Simonet@swisscom.com
> <mailto:Philippe.Simonet@swisscom.com>]
> Gesendet: Mittwoch, 19. Oktober 2011 14:40
> An: olivier.hanesse@gmail.com <mailto:olivier.hanesse@gmail.com>;
> Thomas Pöhler
> Cc: ml-xen-devel@hfp.de <mailto:ml-xen-devel@hfp.de>
> Betreff: RE: [Xen-devel] Possible hint for "Clocksource tsc
> unstable" problem____
>
>
> Hi Olivier and Thomas
>
> andreas ist using ntpd in DOM0, myself too (ntpd - NTP daemon
> program - Ver. 4.2.6p2)
>
> and you ?
>
> @andreas : how do you turn on your ntp logging ?
>
> Philippe
>
>
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com
> <mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-
> <mailto:xen-devel->
> > bounces@lists.xensource.com <mailto:bounces@lists.xensource.com>]
> On Behalf Of Andreas Kinzler
> > Sent: Tuesday, October 18, 2011 5:01 PM
> > To: xen-devel@lists.xensource.com
> <mailto:xen-devel@lists.xensource.com>
> > Subject: [Xen-devel] Possible hint for "Clocksource tsc unstable"
> problem
> >
> > Hello,
> >
> > I made an interesting observation related to the "Clocksource tsc
> > unstable (delta = -2999660320319 ns)" problem. In the log of ntpd
> I found:
> >
> > Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 6001
> > Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 2001
> > Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 6001
> > Oct 5 05:46:09 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 2001
> > Oct 5 06:54:30 greenville-dom0 ntpd[4020]: synchronized to
> > 192.53.103.104 <tel:192.53.103.104>, stratum 1
> > Oct 5 06:54:30 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 6001
> > Oct 5 07:28:22 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 2001
> > Oct 5 08:19:35 greenville-dom0 ntpd[4020]: synchronized to
> > 192.53.103.108 <tel:192.53.103.108>, stratum 1
> > Oct 5 10:53:26 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 6001
> > Oct 5 11:27:32 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 2001
> > Oct 5 12:01:41 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 6001
> > Oct 5 12:18:44 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 2001
> > Oct 5 13:09:58 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 6001
> > Oct 5 13:27:04 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 2001
> > Oct 5 15:26:37 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 6001
> > Oct 5 15:43:41 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 2001
> > Oct 5 17:43:11 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 6001
> > Oct 5 19:08:31 greenville-dom0 ntpd[4020]: synchronized to
> > 192.53.103.104 <tel:192.53.103.104>, stratum 1
> > Oct 5 19:08:31 greenville-dom0 ntpd[4020]: kernel time sync status
> > change 2001
> > Oct 5 21:23:58 greenville-dom0 ntpd[4020]: no servers reachable
> > Oct 5 21:40:58 greenville-dom0 ntpd[4020]: synchronized to
> > 192.53.103.104 <tel:192.53.103.104>, stratum 1
> > Oct 5 21:40:58 greenville-dom0 ntpd[4020]: time correction of -3000
> > seconds exceeds sanity limit (1000); set clock manually to the
> correct
> > UTC time.
> >
> > I had the problem twice on different machines but everytime I saw the
> > line "no servers reachable". Could ntpd and/or linux kernel make some
> > stupid stuff when ntp upstream servers are unreachable?
> >
> > Regards Andreas
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com <mailto:Xen-devel@lists.xensource.com>
> > http://lists.xensource.com/xen-devel____
>
> __ __
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Possible hint for "Clocksource tsc unstable" problem
2011-12-02 19:53 ` Andreas Kinzler
@ 2011-12-07 7:13 ` Philippe.Simonet
0 siblings, 0 replies; 4+ messages in thread
From: Philippe.Simonet @ 2011-12-07 7:13 UTC (permalink / raw)
To: ml-xen-devel, xen-devel; +Cc: tp, olivier.hanesse
[-- Attachment #1.1: Type: text/plain, Size: 9247 bytes --]
Hi
by me it's the same case : I have 2 productive machine type, the one with the AMD 6174
make problem 1 time per month, the one with the AMD 2384 didn't make any problem since 2 years
and different XEN / kernel version.
Philippe
processor : 23
vendor_id : AuthenticAMD
cpu family : 16
model : 9
model name : AMD Opteron(tm) Processor 6174
stepping : 1
cpu MHz : 1296464.014
cache size : 512 KB
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu de tsc msr pae mce cx8 apic mtrr mca cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid amd_dcm pni cx16 popcnt hypervisor lahf_lm cmp_legacy extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch nodeid_msr
bogomips : 4400.22
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate
processor : 7
vendor_id : AuthenticAMD
cpu family : 16
model : 4
model name : Quad-Core AMD Opteron(tm) Processor 2384
stepping : 2
cpu MHz : 2826450.137
cache size : 512 KB
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu de tsc msr pae mce cx8 apic mtrr mca cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch
bogomips : 5400.33
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate
> -----Original Message-----
> From: Andreas Kinzler [mailto:ml-xen-devel@hfp.de]
> Sent: Friday, December 02, 2011 8:53 PM
> To: xen-devel@lists.xensource.com
> Cc: Simonet Philippe, ITS-SDL-EIS-CNV-DLE-TLC; tp@turtle-entertainment.de;
> Olivier Hanesse
> Subject: Re: [Xen-devel] Possible hint for "Clocksource tsc unstable" problem
>
> On 01.12.2011 08:49, Olivier Hanesse wrote:
> > good news !
> > Is your "test system" the same hardware as before ?
> > For example, I don't have time issue with processor having the
> > 'nonstop_tsc' flag.
> > I got only time issue on older processor (Xeon L5420 for example)
>
> Sorry, but my report was on a machine with Xeon E5620 (has nonstop_tsc).
> I did some tests to reproduce the behavior by blocking NTP traffic via iptables
> but the problem did not reproduce in a lab setting.
>
> Regards Andreas
>
> > *From:*Olivier Hanesse [mailto:olivier.hanesse@gmail.com
> > <mailto:olivier.hanesse@gmail.com>]
> > *Sent:* Wednesday, October 19, 2011 2:48 PM
> > *To:* Thomas Pöhler
> > *Cc:* Simonet Philippe, ITS-SDL-EIS-CNV-DLE-TLC; ml-xen-devel@hfp.de<mailto:ml-xen-devel@hfp.de>
> > <mailto:ml-xen-devel@hfp.de>
> > *Subject:* Re: [Xen-devel] Possible hint for "Clocksource tsc
> > unstable" problem____
> >
> > __ __
> >
> > Hi,____
> >
> > __ __
> >
> > Same here.____
> >
> > I am using ntpd in dom0 too (lenny version so 4.2.4)____
> >
> > __ __
> >
> > Regards____
> >
> > __ __
> >
> > Olivier____
> >
> > __ __
> >
> > 2011/10/19 Thomas Pöhler <tp@turtle-entertainment.de
> > <mailto:tp@turtle-entertainment.de>>____
> >
> > Hi Philippe,
> >
> > we are using ntpd in Dom0 too. (also ntpd - NTP daemon program -
> > Ver. 4.2.6p2).
> > We are monitoring ntp over a nagios plugin, check_ntp
> >
> > Regards
> > Thomas
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Philippe.Simonet@swisscom.com<mailto:Philippe.Simonet@swisscom.com>
> > <mailto:Philippe.Simonet@swisscom.com>
> > [mailto:Philippe.Simonet@swisscom.com
> > <mailto:Philippe.Simonet@swisscom.com>]
> > Gesendet: Mittwoch, 19. Oktober 2011 14:40
> > An: olivier.hanesse@gmail.com<mailto:olivier.hanesse@gmail.com> <mailto:olivier.hanesse@gmail.com>;
> > Thomas Pöhler
> > Cc: ml-xen-devel@hfp.de<mailto:ml-xen-devel@hfp.de> <mailto:ml-xen-devel@hfp.de>
> > Betreff: RE: [Xen-devel] Possible hint for "Clocksource tsc
> > unstable" problem____
> >
> >
> > Hi Olivier and Thomas
> >
> > andreas ist using ntpd in DOM0, myself too (ntpd - NTP daemon
> > program - Ver. 4.2.6p2)
> >
> > and you ?
> >
> > @andreas : how do you turn on your ntp logging ?
> >
> > Philippe
> >
> >
> > > -----Original Message-----
> > > From: xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com>
> > <mailto:xen-devel-bounces@lists.xensource.com> [mailto:xen-devel-
> > <mailto:xen-devel->
> > > bounces@lists.xensource.com<mailto:bounces@lists.xensource.com>
> <mailto:bounces@lists.xensource.com>]
> > On Behalf Of Andreas Kinzler
> > > Sent: Tuesday, October 18, 2011 5:01 PM
> > > To: xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> > <mailto:xen-devel@lists.xensource.com>
> > > Subject: [Xen-devel] Possible hint for "Clocksource tsc unstable"
> > problem
> > >
> > > Hello,
> > >
> > > I made an interesting observation related to the "Clocksource tsc
> > > unstable (delta = -2999660320319 ns)" problem. In the log of ntpd
> > I found:
> > >
> > > Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 6001
> > > Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 2001
> > > Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 6001
> > > Oct 5 05:46:09 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 2001
> > > Oct 5 06:54:30 greenville-dom0 ntpd[4020]: synchronized to
> > > 192.53.103.104 <tel:192.53.103.104>, stratum 1
> > > Oct 5 06:54:30 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 6001
> > > Oct 5 07:28:22 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 2001
> > > Oct 5 08:19:35 greenville-dom0 ntpd[4020]: synchronized to
> > > 192.53.103.108 <tel:192.53.103.108>, stratum 1
> > > Oct 5 10:53:26 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 6001
> > > Oct 5 11:27:32 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 2001
> > > Oct 5 12:01:41 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 6001
> > > Oct 5 12:18:44 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 2001
> > > Oct 5 13:09:58 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 6001
> > > Oct 5 13:27:04 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 2001
> > > Oct 5 15:26:37 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 6001
> > > Oct 5 15:43:41 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 2001
> > > Oct 5 17:43:11 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 6001
> > > Oct 5 19:08:31 greenville-dom0 ntpd[4020]: synchronized to
> > > 192.53.103.104 <tel:192.53.103.104>, stratum 1
> > > Oct 5 19:08:31 greenville-dom0 ntpd[4020]: kernel time sync status
> > > change 2001
> > > Oct 5 21:23:58 greenville-dom0 ntpd[4020]: no servers reachable
> > > Oct 5 21:40:58 greenville-dom0 ntpd[4020]: synchronized to
> > > 192.53.103.104 <tel:192.53.103.104>, stratum 1
> > > Oct 5 21:40:58 greenville-dom0 ntpd[4020]: time correction of -3000
> > > seconds exceeds sanity limit (1000); set clock manually to the
> > correct
> > > UTC time.
> > >
> > > I had the problem twice on different machines but everytime I saw the
> > > line "no servers reachable". Could ntpd and/or linux kernel make some
> > > stupid stuff when ntp upstream servers are unreachable?
> > >
> > > Regards Andreas
> > >
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com> <mailto:Xen-<mailto:Xen-devel@lists.xensource.com>
> devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>>
> > > http://lists.xensource.com/xen-devel____
> >
> > __ __
> >
> >
[-- Attachment #1.2: Type: text/html, Size: 27346 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-12-07 7:13 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-10-18 15:00 Possible hint for "Clocksource tsc unstable" problem Andreas Kinzler
2011-10-18 17:41 ` Dan Magenheimer
[not found] ` <FF93AF260AC2BB499A119CC65B092CF7311817E2@sg000713.corproot.net>
[not found] ` <F1CD4AC5B4A5024AAB60E28A82A8450A046CE5EE@winexch1.office.turtle-entertainment.de>
[not found] ` <CABx4GKqodU4FLmX3adiCi3U-eKe5cDMVtNV2ZhzFAMsKL_1uTg@mail.gmail.com>
[not found] ` <FF93AF260AC2BB499A119CC65B092CF7311EE626@sg000713.corproot.net>
[not found] ` <CABx4GKo7CBCW6cn49Kr2O+NTm78ms7Xnh_ub1EZ7pdt+Cmp=Lg@mail.gmail.com>
2011-12-02 19:53 ` Andreas Kinzler
2011-12-07 7:13 ` Philippe.Simonet
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.