Rick Jones wrote:
> *) is that just the T5120 or is it more generally the T5X20?
>
> *) is the T5X40 affected
I will affect any system that has spread-spectrum EMI mitigation. So,
I would guess that yes, they would all be affected, but I don't know
for sure, I only had access to the one system
Fran Horan wrote:
> Thanks Brian.
>
> Can you provide a firmware rev number where the fix was first introduced ?
> Is there a firmware tunable to disable frequency modulation ?
>
> Thanks,
>
> Fran Horan
> JHU/APL
>
>
No, I don't know when it was introduced, but since the problem was the
sp
>
> Do not even think about using NTP on a T1000, T2000, or T5120 until
> you have the latest firmware patch installed (nah-nah, wasn't hardware
> OR software. Or maybe both?). There is a bug in all three that
> causes the firmware to report an incorrect clock frequency to the
> kernel on boot u
Brian Utterback <[EMAIL PROTECTED]> wrote:
> Do not even think about using NTP on a T1000, T2000, or T5120 until
> you have the latest firmware patch installed (nah-nah, wasn't
> hardware OR software. Or maybe both?). There is a bug in all three
> that causes the firmware to report an incorrect cl
Brian,
Naughty Sun. Cheaper to wiggle the clock rather than shield the box. I
can understand the need to do this for the CPU clock, but I thought the
timer interrupt was driven by a different oscillator. The problem is
that the phase jitter would interfere with the TSC (or equivalent) timer
in
Hal Murray wrote:
> [drift > 500 ppm]
>
>> It's almost certainly a hardware problem. Ntpd is telling you that the
>> clock is gaining, or losing, more than about 43 seconds (500 parts per
>> million) per day. 500 PPM is the maximum that ntpd can handle.
>
> It could easily be a software screw
[drift > 500 ppm]
>It's almost certainly a hardware problem. Ntpd is telling you that the
>clock is gaining, or losing, more than about 43 seconds (500 parts per
>million) per day. 500 PPM is the maximum that ntpd can handle.
It could easily be a software screwup.
Unless you know it works on
Conan wrote:
> We are testing Solaris 10 images on a variety of hardware. We discovered a
> problem which seems to only appear on T5120 (Sun4V architecture) and darned
> if I can figure out why.
>
> Every 7 - 12 minutes I get these log entries
> 19 Jun 09:41:41 ntpd[21419]: system event 'event_
Conan,
Have you seen http://suport.ntp.org/Support and the 'Troubleshooting'
section there?
--
Harlan Stenn <[EMAIL PROTECTED]>
http://ntpforum.isc.org - be a member!
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/lis
We are testing Solaris 10 images on a variety of hardware. We discovered a
problem which seems to only appear on T5120 (Sun4V architecture) and darned
if I can figure out why.
Every 7 - 12 minutes I get these log entries
19 Jun 09:41:41 ntpd[21419]: system event 'event_peer/strat_chg' (0x04)
s
10 matches
Mail list logo
