Time going backwards 2005-12-12 - By Ed Wilts
Back
On Sun, Dec 04, 2005 at 11:29:03AM +0100, coyote@(protected) wrote:
> On Sat, 3 Dec 2005, Ed Wilts wrote:
>
> >Thanks, Arjan, I'll give that a try. What should the vendor be using
> >for time keeping if not the tsc counter? I'm not a developer, but I'd
> >like to tell him what he should have done instead.
> >
> >What are the drawbacks to adding notsc? I assume there would be some or
> >it would be the default, wouldn't it?
>
> Just a shot in the dark but since these machines are of course multi-cpu
> it comes to mind.. Are the cpu stepping/revision identical (or not) on the
> systems that exhibit these problems? I don't think this can be checked by
> using /proc/cpuinfo and you might have to look it up on the entire cpu
> module or on the chip itself..
>
> I remember quite vividly a quad-cpu PPro system where a clock jumping
> issue was solved when the 4th cpu was replaced with another (the latter
> with the same rev as the others).
BINGO! I swapped the CPUs around yesterday and the problem is now
resolved. Thank you VERY much for this pointer.
Apparently Windows reports mismatched steppings at boot time. It might
be nice to see a warning thrown into the messages file on Linux
systems... I'll log a call on this one.
We can all yell at Intel and/or HP too - there are NO external markings
on the CPUs telling you what the steppings are. Apparently they're
underneath the heatsink. Yup, that's useful...
Thanks again,
.../Ed
--
Ed Wilts, RHCE
Mounds View, MN, USA
mailto:ewilts@(protected)
Member #1, Red Hat Community Ambassador Program
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
