I have akpm's test10-mm1 patch applied, since it required no changes.


I'm not using speedstep or any voltage altering cpu code in the kernel.
I have an abit athlon based mobo.
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] 
(rev 03).

tsc was used as a high res timesource, this is the first kernel i've 
noticed this being done on.

Detected 1133.815 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Memory: 644968k/655296k available (1917k kernel code, 9596k reserved, 
597k data, 328k init, 0k highmem)
zapping low mappings.
Calibrating delay loop... 2228.22 BogoMIPS


I seemed to be getting a lot of crc dma errors on my hdd's cables in the 
later 2.6.0-test kernels that i never really got before.  Putting it 
down to udma2 instead of 4 solves this most of the time.  I suspect it's 
the timer code that is causing the problems.  Doing some strenuous video 
card testing seemed to pause the box for a long time while X decided to 
crash, introducing another string of dma-crc errors.  I just restarted 
everything and went on my business.  Then after recording a dozen cds 
and jumping through my desktops (i have distributed hardware evolution 
client running all the time in the background) caused X to lock for 15 
seconds or so and i recieved this message upon it coming back to life 
and coastering my cd.

Losing too many ticks!
TSC cannot be used as a timesource. (Are you running with SpeedStep?)
Falling back to a sane timesource.


I got no other message but things seem to be fine again, in fact maybe a 
bit better because jumping through desktops did not cause my buffer on 
the burning to go down as easily.

Here is my acpi initialization
ACPI: Subsystem revision 20031002
ACPI: IRQ5 SCI: Level Trigger.
spurious 8259A interrupt: IRQ7.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
Disabling VIA memory write queue (PCI ID 0305, rev 03): [55] 89 & 1f -> 09
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 12
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
PCI: Using ACPI for IRQ routing


I dont use any special kernel boot strings and besides this clock 
problem, I haven't had any issues with 2.6.  I also use ntpd.  If there 
is anything else i can give in the way of info, i'll be more than happy 
to give it. Since i got no other error messages and the kernel didn't 
oops, this is the only info i have right now.