On Nov 21, 2007 7:27 AM, David Leimbach <[EMAIL PROTECTED]> wrote: > On Nov 21, 2007 6:51 AM, andrey mirtchovski <[EMAIL PROTECTED]> wrote: > > that is probably correct. doesn't amd only "suggest" the clock > > frequency to be what they think the processor speed is when compared > > to the original 1GHz Athlon? > > Yeah their product numbers are not really the clock speed. My > understanding is they were saying an Athlon 2800 was clocked slower > but still about as fast as an Intel at 2800... but that might just be > my own bad memory. > > > > > what is the current time reported by the system? try running timesync > > and monitor the cpufreq for sudden increase/decreases. of course that > > may have nothing to do with your real problem, but i have experience > > high interrupt counts after timesync mangled my cpufreq :) > > > > Starting timesync from the live cd does cause a lot of interrupts yes. > But my network wasn't configured either, which is seemingly the same > thing going on with my plan 9 installation since I didn't configure > any network. > > perhaps timesync should not be on in the default installed > distribution, and users should turn that on themselves once they have > their network configured properly? > > > > > > > At this point I'm booted from the Plan 9 CD and it says I've an > > > AMD-Athlon 2080.... it is, in fact, an Athlon XP 2800+ > > > > > >
Ok another fresh install, I killed timesync, but am still getting thousands of interrupts. And I'm noticing I'm getting about 18 fossil instances and 14 venti instances. not sure if that's normal or not.
