VoodooLabs > News

VoodooTSCSync for Snow Leopard -- New Release

<< < (3/6) > >>

troe666:
Hi Guys
We really badly need a patch like this or ported version for AMD on Snow Leopard.
At the moment there are a few issues. Voodoo/derived kernels on 10.0.0 are detecting socket 939 clock speed fine. But 10.2.0 only detects fsb and bus and shows cpu speed as 0mhz. both 10.0.0 and 10.2.0 show no tsc synchronisation and this manifests in the mDNSResponder mach/absolute time mismatches in system.log with network activity and in general app instability at times.
Is there any way we can please get a Snow Leopard TSC Sync patch for AMD? I would do it but have no clue how.
Also the 10.2.0 onwards kernels are not showing the CPU speed properly.
Here's my full explanation thread posted from another forum:
--------
I know my TSC is out of sync due to the 10.2 darwin kernel reporting 'TSC unsynchronized' and also not showing any CPU clock speed, only FSB. as shown below:
5/01/10 11:15:07 PM   kernel   PAE enabled
5/01/10 11:15:07 PM   kernel   rtclock_init: Taking bus ratio path 1 (AMD Athlon)
5/01/10 11:15:07 PM   kernel   TSC: Verification of clock speed PASSED.
5/01/10 11:15:07 PM   kernel   TSC: Frequency = 0.0000MHz, FSB frequency = 241.7490MHz, bus ratio = 11
5/01/10 11:15:07 PM   kernel   Darwin Kernel Version 10.2.0: Tue Nov 17 01:24:40 EST 2009; annappirtrvh v2:xnu-1486.2.11/BUILD/obj/RELEASE_I386
5/01/10 11:15:07 PM   kernel   Unsynchronized TSC for cpu 1: 0x0000001182b50596, delta 0x45c29


furthermore, I know the Chocolate 10.0.0 kernel is still out of sync despite showing correct clock speed and not reported 'tsc unsynchronised', as I still get the trademark unsyc'd core problem with mDNSPlatformResponder time values in system log, shown below:
7/01/10 3:03:49 AM   kernel   TSC: Verification of clock speed PASSED.
7/01/10 3:03:49 AM   kernel   TSC: Frequency = 2651.90827MHz, FSB frequency = 241.8257MHz, bus ratio = 11
7/01/10 3:03:49 AM   kernel   Darwin Kernel Version 10.0.0: Mon Oct 12 04:06:05 AST 2009; anappirtrvh:xnu-1456.1.26/BUILD/obj/RELEASE_I386
7/01/10 3:03:49 AM   kernel   vm_page_bootstrap: 766473 free pages and 19959 wired pages
7/01/10 3:03:49 AM   kernel   standard timeslicing quantum is 10000 us
7/01/10 3:03:49 AM   kernel   mig_table_max_displ = 73
com.apple.driver.AppleIntelCPUPowerManagement
(e.g you can see how chocolate 10.0.0 kernel shows correct TSC clock speed when compared to later 10.2.0 version above).
and yet I still get (due to unsync'd TSC) in system.log whenever on internet, as well as native app crashes intermittent:

Jan 7 01:12:41 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: last_mach_absolute_time CA9D5BE6000000D0
Jan 7 01:12:41 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: this_mach_absolute_time CA9A758B000000D0
Jan 7 01:12:41 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: last_mach_absolute_time CAADC151000000D0
Jan 7 01:12:41 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: this_mach_absolute_time CAAA7E73000000D0
Jan 7 01:12:41 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: last_mach_absolute_time F01F7A66000000D0
Jan 7 01:12:41 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: this_mach_absolute_time F01CEA92000000D0
Jan 7 01:12:41 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: last_mach_absolute_time F6E4C5F1000000D0
Jan 7 01:12:41 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: this_mach_absolute_time F6E16D8F000000D0
Jan 7 01:12:42 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: last_mach_absolute_time 29563129000000D1
Jan 7 01:12:42 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: this_mach_absolute_time 29526FBC000000D1
Jan 7 01:12:42 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: last_mach_absolute_time 308D7B2B000000D1
Jan 7 01:12:42 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: this_mach_absolute_time 308A7E38000000D1
Jan 7 01:12:42 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: last_mach_absolute_time 39674F17000000D1
Jan 7 01:12:42 troes-iMac mDNSResponder[25]: mDNSPlatformRawTime: this_mach_absolute_time 39640853000000D1

I can fix all issues by running 10.0.0 kernel with 10.2.0 snow and then having CPUS=1 in my kernel flags, which of course allows CPU clock speed to detect properly (due to 10.0.0 kernel) and then prevents TSC sync problems by only using One of the two cores. (due to kernel flag cpus=1)
Overall though its a bit gay because im only running 1 core, and its already shame enough running maxmem=2048 ;p


would REALLY appreciate some input from the chocolate or xnu/xni kernel authors on this one...theres obviously been a change from 9.8 voodoo in terms of now we dont have TSC sync in our kernels nor are the later ones picking up TSC clock speed correctly from socket 939 boards.
These features are pretty critical to AMD users im afraid. A lot of people just wont be noticing the TSC problems in their boot messages or the side effects in their app stability and system.logs etc.

I highly recommend all AMD users on 10.6.2 run for now with cpus=1 kernel flag and the 10.0.0 chocolate kernel. people say the phenom has hardware tsc-sync but there are plenty reporting problems around the place I found when trying to research this problem. not sure what side effects are of running 10.0.0 kernel on 10.2.0 system but i noticed more errors in system.log hence am stuck between rock and a hard place until the TSC Sync patch is released And the new kernels correctly detect CPU clock speed again like 10.0.0's did :(
:(

Thanks for the awesome work though hope u dont think im complaining FAR from it :) just wanting some help! :)

Cho young jun:
i use it for my laptop xps m1210 which have t7200
it works...very well.
but, in my case, when i run activity monitoring, my laptop shutting down... :(
...
anyone else, having same case?
 

righteye:
same problem about Activity Monitor ... KP if i dare opening it when using voodootscsync but not the cpus=1 flag ...

dell 820 with T7400 cpu
so, that makes us 2 with same cpu and same problem; but what that means ?

someone ?

amdest:

--- Quote from: righteye on May 16, 2010, 04:28:08 PM ---same problem about Activity Monitor ... KP if i dare opening it when using voodootscsync but not the cpus=1 flag ...

dell 820 with T7400 cpu
so, that makes us 2 with same cpu and same problem; but what that means ?

someone ?

--- End quote ---

Confirmed. Activity Monitor leads to KP.
"Hard" software works fine: Photoshop, Lightroom, iMovie, FinalCut Express, Soundbooth etc.
All the other software works without problems also...

harom14:
The same panic here with a Dell D620.

* cpus=2 with VoodooTSCSync: kernel panic in 32bit and in 64bit mode too when I launch Activity Monitor
* cpus=1 with VoodooTSCSync: no problem
* cpus=2 without VoodooTSCSync: intolerable lagging

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version