InfiniteMac OSx86

InfiniteMac OSx86 (http://infinitemac.com/forum.php)
-   Leopard 10.5 (http://infinitemac.com/forumdisplay.php?f=85)
-   -   [Solved] AMD Dual Core Timing Issue AKA Mouse Bug (http://infinitemac.com/showthread.php?t=734)

R0GUE 06-20-2008 03:15 PM

iirc the system profiler does not correctly report the Bus Speed correctly. It states mine as being 200Mhz when in fact it should be 2Ghz (2 x 1000Mhz).

edit: Maybe I am wrong about the Bus Speed reading - I'm probably getting confused with the HT speed. :\

http://www.xbitlabs.com/images/cpu/a...0/cpu-3014.png

naquaada 06-20-2008 03:25 PM

No, the update from 10.5.1 -> 10.5.3 was not working. I have always errors on loginwindow, atsserver and mds.

R0GUE 06-20-2008 05:59 PM

22 hours of up time using CPUS=1 boot flag and my machine is still rock solid. I've spent some time in Photoshop creating artwork and applying filters with no visible sign of performance degradation.

Any Leo4All users experiencing this bug or is it just those of us using Zeph?

For now I can live with one core @3Ghz (though not ideal) until either A) I install Leo4All or B) my Intel kit arrives.

naquaada 06-20-2008 06:12 PM

Can you reduce the CPU clock speed in the BIOS? As I o'clocked my system to 3.06 GHz (on 10.5.2) it crashed, couldn't boot anymore. On 10.5.3 I can't have to stay beneath 3 GHz. The actual Macs also only have 3.06 Ghz max, could the high cpu speed be the problem?

R0GUE 06-20-2008 08:58 PM

@naquaada: I'll take a look at my bios settings in due course, but I first want to test this machine thoroughly before rebooting. So far it has been up for over 24 hours and I've hammered it without so much as a hitch. It's definitely a Dual Core problem as far as I am concerned.

StealthMode 06-20-2008 11:59 PM

It has to be, before I upgraded my A64 3200+ to my Opteron 165 x2 I didn't have this problem.

R0GUE 06-21-2008 12:22 AM

I've been speaking with JaS about this and he's convinced that this is a TSC timing issue. He's kindly going to find out about getting a patch to fix the timing issue. I'll keep you all posted.

http://developer.amd.com/assets/TSC_Dual-Core_Utility.pdf

Voyn1x 06-21-2008 12:18 PM

That's really good news! Rogue, after reading that pdf you linked, this would also explain those strange time correction entries in the console when running both cores. eg.

3/18/08 8:41:32 AM mDNSResponder[17] mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 206737245

naquaada 06-21-2008 12:28 PM

Vony1x: You also have a Socket AM2 board I presume. Could this be a problem, maybe because of the DDR2 RAM? Puttabong and me have Socket 939 and it's working fine here. Have you disabled Cool'n'Quiet in the BIOS? I have it enabled.

Voyn1x 06-21-2008 12:31 PM

nope socket 939... Cool'n'Quiet not sure if i have an option for that, i'll have a look