On 12/14/05, Noah J Norris <[EMAIL PROTECTED]> wrote:
> On Thursday 15 December 2005 02:03 am, Richard Fish wrote:
> > I think if you were getting messages about lost ticks or got extra
> > ticks or something like that, these might be helpful, or if your
> > system seemed either to slow or too unresponsive.  Of course, if your
> > clock is defaulting to TSC (which would be bad, BTW), then I guess
> > these could have a big impact.
>
> i have gotton lost tick messages
> and apic errors mostly

Hmm, didn't you mention that somewhere already....oh yeah, your
orignal message!  (bangs head on desk).

Plus, you also said noapic fixes the problem, so forget everything I
said, and try these options.

> > Take a look at dmesg or /var/log/messages for the following lines:
> >
> > Using TSC for gettimeofday
> > Using HPET for gettimeofday
> > Using .* for high-res timesource
> Using pmtmr for high-res timesource

Looks good...pmtmr is what I get on my pentium-m laptop, and is the
default, and should be fairly reliable...

Did you try any other clock= options? Any better results?

> should an amd64 use HPET ? i do not have this enabled in kernel config  (note
> running in 32 bit mode )

Not sure about this one...just got my first AMD64 system this past
weekend, and I am still trying to get things setup...maybe someone
else can answer.

One other boot option that might help: no_timer_check

It is a x86_64 specific option (see
/usr/src/linux/Documentation/x86_64/boot-options.txt).  I don't think
this has anything to do with 32/64 bit code though...so maybe you have
this already (does your kernel build as x86_64/arch/boot/bzImage?)

> other thing i noticed in dmesg do i need to enable smp support in the kernel ?
> this is a single processor system that i know of . does amd do any type of
> hyperthreading ?

Nope, no hyperthreading in AMD.  And I think AMD is expected to
release their first dual-core mobile chips sometime next year. 
Unfortunately Intel is going to beat them to market and my wallet.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Reply via email to