On Monday 09 May 2005 12:53, Bernd Paysan wrote: > On Sunday 08 May 2005 15:40, Andi Kleen wrote: > > Your system should be using the HPET timer to work exactly around > > this. AMD 8000 has HPET. Can you post a boot.log? > > Ok, boot.log attached. The only entry with hpet seems to indicate some > problems. I went through the BIOS setup, and found a disabled feature "ACPI 2.0", which I enabled. Now Linux finds the HPET timer. # grep -i hpet boot.log ACPI: HPET (v001 A M I OEMHPET 0x04000518 MSFT 0x00000097) @ 0x00000000e8ff3c30 ACPI: HPET id: 0x102282a0 base: 0xfec01000 time.c: Using 14.318180 MHz HPET timer. time.c: Using HPET based timekeeping. hpet0: at MMIO 0xfec01000, IRQs 2, 8, 0 hpet0: 69ns tick, 3 32-bit timers hpet_acpi_add: no address or irqs in _CRS and everything appears to work (though there's still no designated CPU to handle the timer interrupts). xntpd syncs quickly, I'm happy (so far ;-). So that explains why nobody sees this problem. But the TSC-based fallback timekeeping is still broken on SMP systems with PowerNow and distributed IRQ handling, which both together seem to be rare enough ;-). -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/
Attachment:
pgpdCTa19i1B5.pgp
Description: PGP signature
- Follow-Ups:
- References:
- False "lost ticks" on dual-Opteron system (=> timer twice as fast)
- From: Bernd Paysan <[email protected]>
- Re: [suse-amd64] False "lost ticks" on dual-Opteron system (=> timer twice as fast)
- From: Andi Kleen <[email protected]>
- Re: [suse-amd64] False "lost ticks" on dual-Opteron system (=> timer twice as fast)
- From: Bernd Paysan <[email protected]>
- False "lost ticks" on dual-Opteron system (=> timer twice as fast)
- Prev by Date: Re: [PATCH 2.6.12-rc3-mm3] connector: add a fork connector
- Next by Date: Kernel (2.6.11) deadlock in user mode when writing data through mmap on large files (64-bit systems, xfs or ext3)
- Previous by thread: Re: [suse-amd64] False "lost ticks" on dual-Opteron system (=> timer twice as fast)
- Next by thread: Re: [suse-amd64] False "lost ticks" on dual-Opteron system (=> timer twice as fast)
- Index(es):
 |