On Mon, Dec 21, 2015 at 12:10 AM, Jon Masters wrote:
> On 12/2/15, 6:55 PM, John Stultz wrote:
>>
>> On Wed, Dec 2, 2015 at 3:42 PM, Andy Lutomirski wrote:
>
>
On a hunch, are you running chrony instead of ntpd?
>>>
>>>
>>> Yes, this is indeed chrony.
>>
>>
>> Ok. I'll have to look closer.
On 12/2/15, 6:55 PM, John Stultz wrote:
On Wed, Dec 2, 2015 at 3:42 PM, Andy Lutomirski wrote:
On a hunch, are you running chrony instead of ntpd?
Yes, this is indeed chrony.
Ok. I'll have to look closer. The last time that message came up it
was in a report of a bug that chrony
On Mon, Dec 21, 2015 at 12:10 AM, Jon Masters wrote:
> On 12/2/15, 6:55 PM, John Stultz wrote:
>>
>> On Wed, Dec 2, 2015 at 3:42 PM, Andy Lutomirski wrote:
>
>
On a hunch, are you running chrony instead of ntpd?
>>>
>>>
>>> Yes, this is indeed
On 12/2/15, 6:55 PM, John Stultz wrote:
On Wed, Dec 2, 2015 at 3:42 PM, Andy Lutomirski wrote:
On a hunch, are you running chrony instead of ntpd?
Yes, this is indeed chrony.
Ok. I'll have to look closer. The last time that message came up it
was in a report of a bug
> >> [0.00] tsc: PIT calibration matches HPET. 2 loops
> >> [0.00] tsc: Detected 2399.975 MHz processor
> >> [0.090897] TSC deadline timer enabled
> >> [1.960034] tsc: Refined TSC clocksource calibration: 2400.007 MHz
> turbostat version 4.10 10 Dec, 2015 - Len Brown
>
On Wed, Dec 2, 2015 at 3:42 PM, John Stultz wrote:
> On Wed, Dec 2, 2015 at 3:38 PM, John Stultz wrote:
>> On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski wrote:
>>> In case it's at all useful, adjtimex -p says:
>>>
>>> mode: 0
>>>offset: 0
>>> frequency: 135641
>>>
On Wed, Dec 2, 2015 at 3:42 PM, Andy Lutomirski wrote:
> On Wed, Dec 2, 2015 at 3:38 PM, John Stultz wrote:
>> On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski wrote:
>>> In case it's at all useful, adjtimex -p says:
>>>
>>> mode: 0
>>>offset: 0
>>> frequency: 135641
>>>
On Wed, Dec 2, 2015 at 3:38 PM, John Stultz wrote:
> On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski wrote:
>> In case it's at all useful, adjtimex -p says:
>>
>> mode: 0
>>offset: 0
>> frequency: 135641
>> maxerror: 37498
>> esterror: 1532
>>status: 8192
On Wed, Dec 2, 2015 at 3:38 PM, John Stultz wrote:
> On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski wrote:
>> In case it's at all useful, adjtimex -p says:
>>
>> mode: 0
>>offset: 0
>> frequency: 135641
>> maxerror: 37498
>> esterror: 1532
>>status: 8192
On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski 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
[cc: John Stultz]
On Wed, Dec 2, 2015 at 2:52 PM, Brown, Len wrote:
> +adrian
>
>> [0.00] tsc: PIT calibration matches HPET. 2 loops
>> [0.00] tsc: Detected 2399.975 MHz processor
>> [0.090897] TSC deadline timer enabled
>> [1.960034] tsc: Refined TSC clocksource
+adrian
> [0.00] tsc: PIT calibration matches HPET. 2 loops
> [0.00] tsc: Detected 2399.975 MHz processor
> [0.090897] TSC deadline timer enabled
> [1.960034] tsc: Refined TSC clocksource calibration: 2400.007 MHz
> [1.960039] clocksource: tsc: mask: 0x
[0.00] tsc: PIT calibration matches HPET. 2 loops
[0.00] tsc: Detected 2399.975 MHz processor
[0.090897] TSC deadline timer enabled
[1.960034] tsc: Refined TSC clocksource calibration: 2400.007 MHz
[1.960039] clocksource: tsc: mask: 0x max_cycles:
[0.00] tsc: PIT calibration matches HPET. 2 loops
[0.00] tsc: Detected 2399.975 MHz processor
[0.090897] TSC deadline timer enabled
[1.960034] tsc: Refined TSC clocksource calibration: 2400.007 MHz
[1.960039] clocksource: tsc: mask: 0x max_cycles:
+adrian
> [0.00] tsc: PIT calibration matches HPET. 2 loops
> [0.00] tsc: Detected 2399.975 MHz processor
> [0.090897] TSC deadline timer enabled
> [1.960034] tsc: Refined TSC clocksource calibration: 2400.007 MHz
> [1.960039] clocksource: tsc: mask: 0x
> >> [0.00] tsc: PIT calibration matches HPET. 2 loops
> >> [0.00] tsc: Detected 2399.975 MHz processor
> >> [0.090897] TSC deadline timer enabled
> >> [1.960034] tsc: Refined TSC clocksource calibration: 2400.007 MHz
> turbostat version 4.10 10 Dec, 2015 - Len Brown
On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski 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
>
On Wed, Dec 2, 2015 at 3:42 PM, Andy Lutomirski wrote:
> On Wed, Dec 2, 2015 at 3:38 PM, John Stultz wrote:
>> On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski wrote:
>>> In case it's at all useful, adjtimex -p says:
>>>
>>>
[cc: John Stultz]
On Wed, Dec 2, 2015 at 2:52 PM, Brown, Len wrote:
> +adrian
>
>> [0.00] tsc: PIT calibration matches HPET. 2 loops
>> [0.00] tsc: Detected 2399.975 MHz processor
>> [0.090897] TSC deadline timer enabled
>> [1.960034] tsc: Refined TSC
On Wed, Dec 2, 2015 at 3:42 PM, John Stultz wrote:
> On Wed, Dec 2, 2015 at 3:38 PM, John Stultz wrote:
>> On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski wrote:
>>> In case it's at all useful, adjtimex -p says:
>>>
>>>
On Wed, Dec 2, 2015 at 3:38 PM, John Stultz wrote:
> On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski wrote:
>> In case it's at all useful, adjtimex -p says:
>>
>> mode: 0
>>offset: 0
>> frequency: 135641
>> maxerror: 37498
>>
On Wed, Dec 2, 2015 at 3:38 PM, John Stultz wrote:
> On Wed, Dec 2, 2015 at 3:25 PM, Andy Lutomirski wrote:
>> In case it's at all useful, adjtimex -p says:
>>
>> mode: 0
>>offset: 0
>> frequency: 135641
>> maxerror: 37498
>>
22 matches
Mail list logo