#1
|
|||
|
|||
AMD Dual-Core Optimizer for Snow Leopard
History
I have an AMD Athlon 64 X2 dual-core processor. If I boot into Snow Leopard as is, I get EXC_I386_DIV crashes across my entire system after a few hours. If I boot with the cpus=1 kernel flag, I do not receive the crashes but I lose my second core, of course. When I booted with both cores enabled, I saw a message in my kernel log saying I had an unsynchronized TSC (time stamp counter) so I deduced that that was the cause of my crashes. And it made sense since only after a few hours could the TSC become so unsynchronized so as to cause crashes (I don't know the specifics.). After I discovered this, I found the VoodooTSCSync project (http://code.google.com/p/voodootscsync/). I tried it and it synchronized my TSC at boot but I still got crashes! Then I realized that I needed my TSC to be synchronized constantly, just like the AMD Dual-Core Optimizer does for Windows users. So I took the VoodooTSCSync project and turned it into VoodooTSCSyncAMD. What it does VoodooTSCSyncAMD is basically AMD Dual-Core Optimizer for the Mac OS. It synchronizes the TSC across all processor cores every 10 seconds. This is for Athlon 64 FX, Athlon 64 X2, Opteron (first-generation and second-generation), Sempron X2, and Turion 64 X2. VoodooTSCSyncAMD is essential to prevent EXC_I386_DIV crashes on these processors, as well as problems with Adobe Flash Player, and system lag after a few hours. I would like to thank the original creators of VoodooTSCSync for their efforts. Last edited by fumoboy007; 04-01-2011 at 02:27 AM. |
#2
|
|||
|
|||
works!
reporting that it works on my AMD Athlon64 X2 5200+
no more ``EXC_I386_DIV`` crashes in console after 3+ hours so far Thank you ! |
#3
|
|||
|
|||
Will try this out ... Thanks !
|
#4
|
|||
|
|||
Sweet, any chance to get this working with other multi core processors?
I have a phenom II x4, i guess i could try and see if this works out of the box |
#5
|
|||
|
|||
Actually this isn't needed on the Phenom II's or Athlon II's, only older Amd x2's(not II X2's).
GA-Z68XP-UD3: Lion 10.7.3, Windows 7 Professional 64bit SP1 and FreeBSD 9-RELEASE, Core i5 2500K @ 3.3GHz, 16GB 1333 Mhz DDR3 ram(Soon), 1GB GDDR5 Nvidia Geforce GTX 560 Ti, 2X 1TB Samsung F3 SATA HDDs, 1X WDC Blue 500GB HDD; Dell Mini 10v: Obsidian Black, 2GB DDR2 533MHz Ram, 1.6GHz Intel Atom N270, 120GB HDD, 6-Cell, Mac OS X Snow Leopard 10.6.8 Build 10K549 |
#6
|
|||
|
|||
Ah, okay, thanks for pointing that out
|
#7
|
|||
|
|||
Thank you, fumoboy007, for the fix. I also have an older Athlon x2 64 CPU and experience similar random application and system crashes after some hours after start of the system.
Hopefully this kext will eliminate these sync issues altogether |
#8
|
|||
|
|||
You are my hero! It's been so aggravating having a system being so close to perfect except for one issue that ruins the experience. Now my computer's been running great without any crashing. Thank you so much!
|
#9
|
|||
|
|||
[quote=fumoboy007;51881]History
I have an AMD Athlon 64 X2 dual-core processor. If I boot into Snow Leopard as is, I get EXC_I386_DIV crashes across my entire system after a few hours. If I boot with the cpus=1 kernel flag, I do not receive the crashes but I lose my second core, of course. When I booted with both cores enabled, I saw a message in my kernel log saying I had an unsynchronized TSC (time stamp counter) so I deduced that that was the cause of my crashes. And it made sense since only after a few hours could the TSC become so unsynchronized so as to cause crashes (I don't know the specifics.). After I discovered this, I found the VoodooTSCSync project (http://code.google.com/p/voodootscsync/). I tried it and it synchronized my TSC at boot but I still got crashes! Then I realized that I needed my TSC to be synchronized constantly, just like the AMD Dual-Core Optimizer does for Windows users. So I took the VoodooTSCSync project and turned it into VoodooTSCSyncAMD. Does the following bootflag not work? - maybe it syncs only at boot also? Code:
"tscsync= Certain multi-core CPUs suffer from a timestamp counter drift between the cores causing unpredictable timing behaviour or audio stutters. The kernel automatically accounts for this. Use this option to enable or disable this feature. Pass 0 (zero) to disable or 1 (one) to enable tsc synchronization. Example: tscsync=0" |
#10
|
|||
|
|||
Quote:
💡 Deploy cloud instances seamlessly on DigitalOcean. Free credits ($100) for InfMac readers. |