Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1282592
| From | John Stultz <john.stultz@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Skylake (XPS 13 9350) TSC is way off |
| Date | 2015-12-03 00:40 +0100 |
| Message-ID | <qBpa9-5uf-1@gated-at.bofh.it> (permalink) |
| References | <qBlSX-3wb-37@gated-at.bofh.it> <qBoxu-50H-55@gated-at.bofh.it> <qBp0t-5qO-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski <luto@kernel.org> wrote: > In case it's at all useful, adjtimex -p says: > > mode: 0 > offset: 0 > frequency: 135641 > maxerror: 37498 > esterror: 1532 > status: 8192 > time_constant: 2 > precision: 1 > tolerance: 32768000 > tick: 10000 > raw time: 1449098317s 671243180us = 1449098317.671243180 > > this suggests a rather small correction, so I really have no idea what > "Adjusting tsc more than 11% (8039115 vs 7759462)" means. > > John, you wrote this code. What does the error message mean? Basally the internal correction adjustments are getting pulled further then it is supposed to (its concerning since in some cases we push the clocksource mult value to be quite large, and so making a large adjustment could possibly cause an overflow). Awhile back I had intended to cap the max adjustment, but out of caution I put in a warning instead to see how often this might occur. I've seen it reported sometimes while folks were running trinity or under a VM (suggesting that due to system delays timekeeping management may have been delayed and the internal time error had grown quite far, so the internal correction was being somewhat aggressive). Though more recently (3.17 era) we've changed the internal adjustment code to try to be more conservative to avoid over-steering w/ NOHZ, so I'd expect fewer of these. On a hunch, are you running chrony instead of ntpd? thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Skylake (XPS 13 9350) TSC is way off Andy Lutomirski <luto@kernel.org> - 2015-12-02 21:10 +0100
RE: Skylake (XPS 13 9350) TSC is way off "Brown, Len" <len.brown@intel.com> - 2015-12-03 00:00 +0100
Re: Skylake (XPS 13 9350) TSC is way off Andy Lutomirski <luto@kernel.org> - 2015-12-03 00:30 +0100
Re: Skylake (XPS 13 9350) TSC is way off John Stultz <john.stultz@linaro.org> - 2015-12-03 00:40 +0100
Re: Skylake (XPS 13 9350) TSC is way off Andy Lutomirski <luto@kernel.org> - 2015-12-03 00:50 +0100
Re: Skylake (XPS 13 9350) TSC is way off John Stultz <john.stultz@linaro.org> - 2015-12-03 01:00 +0100
Re: Skylake (XPS 13 9350) TSC is way off John Stultz <john.stultz@linaro.org> - 2015-12-03 00:50 +0100
Re: Skylake (XPS 13 9350) TSC is way off Andy Lutomirski <luto@kernel.org> - 2015-12-03 01:10 +0100
RE: Skylake (XPS 13 9350) TSC is way off "Brown, Len" <len.brown@intel.com> - 2015-12-03 04:30 +0100
csiph-web