> Some BIOSes do not lock SMM, and you *could* turn it off at the chipset
> level.
I don't see anything about SMM in my BIOS configuration even with the
advanced options enabled... Turning it off at the chipset level sounds
like a hardware hack - is it?
The gettimeofday patch for 2.6.13-rc3
> It's most likely bad SMM code in the BIOS that blocks the CPU too long
> and is triggered in idle.
Might a BIOS flash help, or is this something that's there to stay?
> No way to fix this, but you can work around it with very new kernels
> by compiling with a lower HZ than 1000.
Actually, it
It's most likely bad SMM code in the BIOS that blocks the CPU too long
and is triggered in idle.
Might a BIOS flash help, or is this something that's there to stay?
No way to fix this, but you can work around it with very new kernels
by compiling with a lower HZ than 1000.
Actually, it was
Some BIOSes do not lock SMM, and you *could* turn it off at the chipset
level.
I don't see anything about SMM in my BIOS configuration even with the
advanced options enabled... Turning it off at the chipset level sounds
like a hardware hack - is it?
The gettimeofday patch for 2.6.13-rc3 won't
Hi, I'm running an Athlon64 X2 4400+ (a dual core model) with an
nVidia GeForce 6800 Ultra on a Gigabyte GA-K8NXP-SLI motherboard and
getting nasty messages like these in my dmesg:
warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts
rip
Hi, I'm running an Athlon64 X2 4400+ (a dual core model) with an
nVidia GeForce 6800 Ultra on a Gigabyte GA-K8NXP-SLI motherboard and
getting nasty messages like these in my dmesg:
warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts
rip
6 matches
Mail list logo
