AsusFreak Posted February 1, 2015 Share Posted February 1, 2015 Yep, it works fine. Link to comment Share on other sites More sharing options...
Rampage Dev Posted February 1, 2015 Share Posted February 1, 2015 Sleep shouldn't work, period. Display sleep, sure. Has anyone tried updating with the Clover kernel patch for x99 to 10.10.2? No, that is incorrect. Sleep is not supported. That does not mean it will or will not work. Not working and not supported are two different things. Link to comment Share on other sites More sharing options...
Edkroket Posted February 2, 2015 Share Posted February 2, 2015 I have strange behavior with my X99-UD4 running BIOS F12 from the beginning I have it. From time to time my system just reboots without any error in console. It does it on any BIOS firmware and not when I run Windows 7 Restart takes a long time from OS to BIOS. I suspect my graphics card InoDB GTX970. I changed disks and SSD's different boot flags or whatsoever. The reboot comes just from time to time. The kernel patch in clover configurator works fine when upgrading to 10.10.2 Also sleep has worked for me in the beginning when I had this board. But now it won't sleep but I can live whit that. Not the random reboots. Does anyone have a clue? I'm lost and frustrated. Link to comment Share on other sites More sharing options...
jamiethemorris Posted February 2, 2015 Share Posted February 2, 2015 I have strange behavior with my X99-UD4 running BIOS F12 from the beginning I have it. From time to time my system just reboots without any error in console. It does it on any BIOS firmware and not when I run Windows 7 Restart takes a long time from OS to BIOS. I suspect my graphics card InoDB GTX970. I changed disks and SSD's different boot flags or whatsoever. The reboot comes just from time to time. The kernel patch in clover configurator works fine when upgrading to 10.10.2 Also sleep has worked for me in the beginning when I had this board. But now it won't sleep but I can live whit that. Not the random reboots. Does anyone have a clue? I'm lost and frustrated. use the debug=0x100 boot flag, it will show you a kernel panic message time instead of just rebooting Link to comment Share on other sites More sharing options...
Edkroket Posted February 2, 2015 Share Posted February 2, 2015 use the debug=0x100 boot flag, it will show you a kernel panic message time instead of just rebooting Thank you for that! It appears to be the GenericUSBXHCI kext . The one I needed to have Vm_ware running normally. With this one not being used I can't use VM-Ware but I need to run it. Do you know a different way to have VM-Ware working without this kext? Link to comment Share on other sites More sharing options...
jamiethemorris Posted February 2, 2015 Share Posted February 2, 2015 Thank you for that! It appears to be the GenericUSBXHCI kext . The one I needed to have Vm_ware running normally. With this one not being used I can't use VM-Ware but I need to run it. Do you know a different way to have VM-Ware working without this kext? I have no idea... Your USB3 is recognized natively right, or did you need the kexts? I mean there's a few other kexts you could install instead like the caldigit ones, but they would probably cause the same problem. Also do you have anything plugged into your USB3 ports? Link to comment Share on other sites More sharing options...
Edkroket Posted February 3, 2015 Share Posted February 3, 2015 I have no idea... Your USB3 is recognized natively right, or did you need the kexts? I mean there's a few other kexts you could install instead like the caldigit ones, but they would probably cause the same problem. Also do you have anything plugged into your USB3 ports? Yes of course USB-3 is recognized natively but than VM-Ware is to slow to use for anything. With the GenericUSB-3 kext it runs just fine for some reason. And no nothing in USB-3 ports or maybe my Apple-keyboard. When I use no kext USB shows like USB-3 HighSpeed or Superspeed. With the the Generic USB kext it shows like that Generic. I will try the one from RampageDev's X99 image and see if that's gonna work. Link to comment Share on other sites More sharing options...
jamiethemorris Posted February 3, 2015 Share Posted February 3, 2015 Yes of course USB-3 is recognized natively but than VM-Ware is to slow to use for anything. With the GenericUSB-3 kext it runs just fine for some reason. And no nothing in USB-3 ports or maybe my Apple-keyboard. When I use no kext USB shows like USB-3 HighSpeed or Superspeed. With the the Generic USB kext it shows like that Generic. I will try the one from RampageDev's X99 image and see if that's gonna work. I think RD's is the same one. Perhaps you could try removing AppleUSBXHCI and see if that solves the problem. Also plug your Apple keyboard into the 2.0 port if you can. Link to comment Share on other sites More sharing options...
Edkroket Posted February 3, 2015 Share Posted February 3, 2015 I think RD's is the same one. Perhaps you could try removing AppleUSBXHCI and see if that solves the problem. Also plug your Apple keyboard into the 2.0 port if you can. Ok I remove AppleUSBXHCI and put back GenericUSB3 you mean I think.? Try that tonight. Link to comment Share on other sites More sharing options...
Rampage Dev Posted February 3, 2015 Share Posted February 3, 2015 Any USB 3.0 Connections that use VIA Chips to make 2 ports into 4 Need the 3rd Party Driver. 1 Link to comment Share on other sites More sharing options...
jamiethemorris Posted February 4, 2015 Share Posted February 4, 2015 Ok I remove AppleUSBXHCI and put back GenericUSB3 you mean I think.? Try that tonight. Yes, that is what I meant. 1 Link to comment Share on other sites More sharing options...
Edkroket Posted February 5, 2015 Share Posted February 5, 2015 Any USB 3.0 Connections that use VIA Chips to make 2 ports into 4 Need the 3rd Party Driver. Ok that makes sense but do you have any idea why the USB-3 driver causes KP's on my system? It is the only way to use VM-Ware on my X99-UD4 If I don't use it VM-Ware is to slow to use and I need it to run. Yes, that is what I meant. I did this but when only using USB-3 kext it acts the same as with both of them. Causing KP and slow reboot and BIOS Errors. Not sure what else I can do. Would a DSDT extract and some edits solve this problem? And if so what should I look at and change so I don't need USB-3.kext and still have it's function to use VW-Ware. Link to comment Share on other sites More sharing options...
jamiethemorris Posted February 5, 2015 Share Posted February 5, 2015 Ok that makes sense but do you have any idea why the USB-3 driver causes KP's on my system? It is the only way to use VM-Ware on my X99-UD4 If I don't use it VM-Ware is to slow to use and I need it to run. I did this but when only using USB-3 kext it acts the same as with both of them. Causing KP and slow reboot and BIOS Errors. Not sure what else I can do. Would a DSDT extract and some edits solve this problem? And if so what should I look at and change so I don't need USB-3.kext and still have it's function to use VW-Ware. Type in this command when vmware is running: sudo powermetrics interrupts Just to confirm that you see high amounts of interrupts on XHCI without the kext installed. I have read this is the cause of the issue and the reason that installing the kext solves it. Try it both with and without the kext. You also have the option of (as a LAST resort workaround) disabling USB3 in the BIOS and using a third-party card that is natively supported. Well, at least I think that would work. I think it can be solved in ACPI tables by moving around IRQs or something, but I'm not sure. Also, what does the exact kernel panic message say? Anything useful? The slow reboot to my knowledge is a bug in the kext itself and is not directly related to your other problem. So yeah, post the output of that command while vmware is running, both with and without the kext installed, and post the exact kp message next time it happens. Also, can you get a full ACPI dump from Clover? I want to look to see if there's anything OS-specific in the ACPI tables related to USB3. The fix could literally be something as simple as telling the firmware to treat the OS the same as windows 8. Link to comment Share on other sites More sharing options...
Edkroket Posted February 5, 2015 Share Posted February 5, 2015 Type in this command when vmware is running: sudo powermetrics interrupts Just to confirm that you see high amounts of interrupts on XHCI without the kext installed. I have read this is the cause of the issue and the reason that installing the kext solves it. Try it both with and without the kext. You also have the option of (as a LAST resort workaround) disabling USB3 in the BIOS and using a third-party card that is natively supported. Well, at least I think that would work. I think it can be solved in ACPI tables by moving around IRQs or something, but I'm not sure. Also, what does the exact kernel panic message say? Anything useful? The slow reboot to my knowledge is a bug in the kext itself and is not directly related to your other problem. So yeah, post the output of that command while vmware is running, both with and without the kext installed, and post the exact kp message next time it happens. Also, can you get a full ACPI dump from Clover? I want to look to see if there's anything OS-specific in the ACPI tables related to USB3. The fix could literally be something as simple as telling the firmware to treat the OS the same as windows 8. Ok things are getting stranger..... I removed the GenericUSB3 kext and did a comboupdate of 10.10.2 Restarted and so on. I started VM-Ware and was expecting very slow start of my guest OS. But to my surprise it booted just instantly and whili it was booting I issued the your powermetrics. I could not use my mouse nor keyboard for half a minute and then it was back again. VM-Ware running and mouse and keyboard back. Here is the output: ----------------------------------------------------------------------------- unable to get battery node unable to get backlight node unable to get backlight node unable to get smc values Machine model: MacPro5,1 SMC version: 1.39f11 EFI version: MP51.007F.B03 OS version: 14C109 Boot arguments: npci=0x2000 nvda_drv=1 kext-dev-mode=1 debug=0x100 slide=0 Boot time: Thu Feb 5 21:13:38 2015 *** Sampled system activity (Thu Feb 5 21:18:35 2015 +0100) (5007.93ms elapsed) *** *** Running tasks *** Name ID CPU ms/s User% Deadlines (<2 ms, 2-5 ms) Wakeups (Intr, Pkg idle) vmware-vmx 534 761.34 4.99 2.40 0.00 45.93 0.00 kernel_task 0 22.64 0.00 0.00 0.00 1018.63 670.37 VMware Fusion 421 132.18 90.37 0.00 0.00 22.37 1.40 WindowServer 146 27.70 59.17 25.56 4.19 46.93 2.40 Dock 214 10.40 60.73 0.00 0.00 0.60 0.40 firefox 403 7.68 90.07 2.80 1.00 13.18 2.80 Console 211 3.90 79.67 0.00 0.00 1.20 0.80 DEAD_TASKS -1 2.49 51.25 0.00 0.00 0.00 0.00 cfprefsd 105 1.63 34.84 0.00 0.00 1.20 0.00 Terminal 498 1.53 88.29 0.00 0.00 2.80 0.40 Dropbox109 308 1.44 88.43 0.00 0.00 1.40 0.40 xrdd 61 0.53 23.62 165.74 0.00 166.54 3.59 discoveryd 49 0.84 47.10 0.20 0.00 2.00 0.40 powermetrics 538 0.76 17.72 0.00 0.00 0.20 0.00 coreservicesd 75 0.52 23.71 0.00 0.00 0.20 0.00 mds 33 0.53 50.34 0.00 0.00 2.00 0.20 configd 26 0.38 75.78 0.00 0.00 1.40 0.00 Mail 207 0.58 67.59 0.00 0.00 0.00 0.00 fseventsd 20 0.26 40.06 0.00 0.00 2.40 0.20 VMware Fusion Start Menu 500 0.25 78.89 0.00 0.00 2.00 0.20 Calendar 209 0.29 88.20 0.00 0.00 0.20 0.00 notifyd 73 0.43 49.34 0.00 0.00 0.00 0.00 CIJScannerRegister 372 0.20 24.35 0.00 0.00 3.59 0.20 mds_stores 162 0.28 58.12 0.00 0.00 0.00 0.00 dbfseventsd 359 0.24 23.62 0.00 0.00 0.00 0.00 dbfseventsd 362 0.22 6.18 0.00 0.00 0.00 0.00 opendirectoryd 46 0.24 48.37 0.00 0.00 0.20 0.00 mdworker 407 0.26 56.25 0.00 0.00 0.00 0.00 launchd 1 0.17 35.60 0.00 0.00 0.00 0.00 syslogd 17 0.12 55.32 0.00 0.00 0.40 0.00 cfprefsd 205 0.12 57.88 0.00 0.00 0.00 0.00 Finder 218 0.09 38.01 0.00 0.00 0.40 0.00 vmware-usbarbitrator 527 0.04 30.79 0.00 0.00 1.00 0.20 dbfseventsd 358 0.04 5.18 0.00 0.00 1.60 0.20 socketfilterfw 170 0.04 24.12 0.00 0.00 0.20 0.20 ocspd 147 0.03 28.35 0.00 0.00 0.80 0.20 launchservicesd 51 0.03 23.99 0.00 0.00 1.00 0.20 usernoted 223 0.06 37.30 0.00 0.00 0.40 0.00 nsurlsessiond 163 0.03 25.89 0.00 0.00 0.60 0.20 com.apple.WebKit.WebContent 337 0.05 45.13 0.00 0.00 0.60 0.00 nsurlstoraged 497 0.01 34.13 0.00 0.00 0.40 0.20 rpcsvchost 154 0.01 20.44 0.00 0.00 0.20 0.20 vmnet-natd 521 0.05 21.03 0.00 0.00 0.00 0.00 warmd 32 0.01 40.30 0.00 0.00 0.20 0.20 com.apple.WebKit.WebContent 280 0.04 55.93 0.00 0.00 0.20 0.00 com.apple.WebKit.WebContent 335 0.03 62.30 0.00 0.00 0.20 0.00 login 501 0.03 33.49 0.00 0.00 0.60 0.00 Spotlight 229 0.02 52.96 0.00 0.00 0.40 0.00 nsurlsessiond 224 0.03 24.31 0.00 0.00 0.40 0.00 ntpd 166 0.02 38.75 0.00 0.00 0.80 0.00 bird 234 0.02 17.90 0.00 0.00 0.40 0.00 powerd 27 0.02 19.11 0.00 0.00 0.60 0.00 SystemUIServer 217 0.01 77.30 0.00 0.00 0.20 0.00 networkd 169 0.02 15.55 0.00 0.00 0.40 0.00 vmnet-bridge 513 0.01 27.76 0.00 0.00 0.60 0.00 diskarbitrationd 39 0.01 13.00 0.00 0.00 0.20 0.00 UserEventAgent 16 0.01 24.39 0.00 0.00 0.40 0.00 airportd 30 0.01 14.03 0.00 0.00 0.20 0.00 securityd 53 0.01 63.36 0.00 0.00 0.00 0.00 coreaudiod 219 0.01 25.60 0.00 0.00 0.20 0.00 iconservicesagent 242 0.01 35.00 0.00 0.00 0.20 0.00 CVMServer 182 0.00 27.66 0.00 0.00 0.20 0.00 fontd 231 0.01 39.94 0.00 0.00 0.20 0.00 iconservicesd 37 0.01 36.32 0.00 0.00 0.20 0.00 com.apple.WebKit.Networking 279 0.00 27.53 0.00 0.00 0.20 0.00 networkd_privileged 173 0.00 30.71 0.00 0.00 0.20 0.00 ALL_TASKS -2 980.91 20.20 196.69 5.19 1349.66 685.51 **** Battery and backlight usage **** **** Network activity **** out: 10.18 packets/s, 1803.34 bytes/s in: 8.59 packets/s, 1454.69 bytes/s **** Disk activity **** read: 911.95 ops/s 125864.70 KBytes/s write: 2.60 ops/s 508.74 KBytes/s **** Interrupt distribution **** CPU 0: Vector 0x53(XHCI): 158842.39 interrupts/sec Vector 0x72(GLAN): 15.18 interrupts/sec Vector 0x74(SAT1): 914.55 interrupts/sec Vector 0x76(H000): 9.58 interrupts/sec Vector 0xdd(TMR): 60.50 interrupts/sec Vector 0xde(IPI): 96.05 interrupts/sec CPU 1: Vector 0xdd(TMR): 0.40 interrupts/sec Vector 0xde(IPI): 0.60 interrupts/sec CPU 2: Vector 0xdd(TMR): 211.86 interrupts/sec Vector 0xde(IPI): 11.98 interrupts/sec CPU 3: Vector 0xde(IPI): 2.00 interrupts/sec CPU 4: Vector 0xdd(TMR): 159.95 interrupts/sec Vector 0xde(IPI): 12.78 interrupts/sec CPU 5: Vector 0xdd(TMR): 0.20 interrupts/sec Vector 0xde(IPI): 1.20 interrupts/sec CPU 6: Vector 0xdd(TMR): 68.89 interrupts/sec Vector 0xde(IPI): 6.79 interrupts/sec CPU 7: Vector 0xdd(TMR): 0.20 interrupts/sec Vector 0xde(IPI): 2.80 interrupts/sec CPU 8: Vector 0xdd(TMR): 138.38 interrupts/sec Vector 0xde(IPI): 13.18 interrupts/sec CPU 9: Vector 0xdd(TMR): 0.20 interrupts/sec Vector 0xde(IPI): 4.19 interrupts/sec CPU 10: Vector 0xdd(TMR): 136.38 interrupts/sec Vector 0xde(IPI): 9.39 interrupts/sec CPU 11: Vector 0xde(IPI): 2.00 interrupts/sec **** Processor usage **** Intel energy model derived package power (CPUs+GT+SA): 57.97W LLC flushed residency: 0% System Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) Package 0 C-state residency: 0.00% (C2: 0.00% C3: 0.00% C6: 0.00% C7: 0.00% ) Core 0 C-state residency: 0.00% (C3: 0.00% C6: 0.00% C7: 0.00% ) CPU 0 duty cycles/s: active/idle [< 16 us: 44287.19/45027.02] [< 32 us: 43.13/0.00] [< 64 us: 86.66/0.00] [< 128 us: 19.37/0.00] [< 256 us: 16.37/0.00] [< 512 us: 517.98/0.00] [< 1024 us: 46.53/0.00] [< 2048 us: 5.79/0.00] [< 4096 us: 2.00/0.00] [< 8192 us: 0.80/0.00] [< 16384 us: 0.40/0.00] [< 32768 us: 0.80/0.00] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) CPU 1 duty cycles/s: active/idle [< 16 us: 1.20/0.60] [< 32 us: 0.60/0.00] [< 64 us: 0.20/0.20] [< 128 us: 0.00/0.00] [< 256 us: 0.00/0.00] [< 512 us: 0.00/0.00] [< 1024 us: 0.00/0.00] [< 2048 us: 0.00/0.00] [< 4096 us: 0.00/0.00] [< 8192 us: 0.00/0.00] [< 16384 us: 0.00/0.00] [< 32768 us: 0.00/0.20] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) Core 1 C-state residency: 0.00% (C3: 0.00% C6: 0.00% C7: 0.00% ) CPU 2 duty cycles/s: active/idle [< 16 us: 427.52/115.82] [< 32 us: 382.19/44.53] [< 64 us: 24.76/124.20] [< 128 us: 7.79/26.36] [< 256 us: 104.23/106.63] [< 512 us: 13.18/140.58] [< 1024 us: 5.39/326.88] [< 2048 us: 3.79/32.75] [< 4096 us: 0.60/22.56] [< 8192 us: 0.20/14.58] [< 16384 us: 2.40/11.58] [< 32768 us: 0.20/3.19] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) CPU 3 duty cycles/s: active/idle [< 16 us: 2.00/0.20] [< 32 us: 0.20/0.20] [< 64 us: 0.00/0.00] [< 128 us: 0.00/0.40] [< 256 us: 0.00/0.20] [< 512 us: 0.00/0.20] [< 1024 us: 0.00/0.00] [< 2048 us: 0.00/0.00] [< 4096 us: 0.00/0.00] [< 8192 us: 0.00/0.00] [< 16384 us: 0.00/0.20] [< 32768 us: 0.00/0.00] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) Core 2 C-state residency: 0.00% (C3: 0.00% C6: 0.00% C7: 0.00% ) CPU 4 duty cycles/s: active/idle [< 16 us: 362.63/80.67] [< 32 us: 196.69/26.96] [< 64 us: 17.77/93.45] [< 128 us: 8.59/19.77] [< 256 us: 62.10/61.30] [< 512 us: 13.58/82.67] [< 1024 us: 3.99/223.65] [< 2048 us: 2.20/34.15] [< 4096 us: 0.60/13.38] [< 8192 us: 0.80/16.37] [< 16384 us: 1.80/9.98] [< 32768 us: 0.00/3.79] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) CPU 5 duty cycles/s: active/idle [< 16 us: 3.19/0.80] [< 32 us: 0.20/0.20] [< 64 us: 0.00/0.20] [< 128 us: 0.00/0.00] [< 256 us: 0.00/0.40] [< 512 us: 0.00/0.00] [< 1024 us: 0.00/0.00] [< 2048 us: 0.00/0.00] [< 4096 us: 0.00/0.40] [< 8192 us: 0.00/0.00] [< 16384 us: 0.00/0.00] [< 32768 us: 0.00/0.20] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) Core 3 C-state residency: 0.00% (C3: 0.00% C6: 0.00% C7: 0.00% ) CPU 6 duty cycles/s: active/idle [< 16 us: 166.14/53.12] [< 32 us: 111.22/22.76] [< 64 us: 15.77/25.56] [< 128 us: 4.59/12.18] [< 256 us: 44.73/38.14] [< 512 us: 8.79/52.52] [< 1024 us: 3.59/120.01] [< 2048 us: 1.00/16.77] [< 4096 us: 0.00/6.19] [< 8192 us: 0.00/2.80] [< 16384 us: 1.00/2.00] [< 32768 us: 0.00/1.60] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) CPU 7 duty cycles/s: active/idle [< 16 us: 3.79/0.80] [< 32 us: 1.20/0.40] [< 64 us: 0.00/0.60] [< 128 us: 0.00/0.40] [< 256 us: 0.20/0.00] [< 512 us: 0.00/0.20] [< 1024 us: 0.00/0.00] [< 2048 us: 0.00/0.00] [< 4096 us: 0.00/0.20] [< 8192 us: 0.00/0.20] [< 16384 us: 0.00/0.00] [< 32768 us: 0.00/0.60] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) Core 4 C-state residency: 0.00% (C3: 0.00% C6: 0.00% C7: 0.00% ) CPU 8 duty cycles/s: active/idle [< 16 us: 256.39/74.28] [< 32 us: 169.53/17.57] [< 64 us: 12.78/50.12] [< 128 us: 9.58/15.18] [< 256 us: 60.90/56.71] [< 512 us: 4.79/85.86] [< 1024 us: 2.40/160.94] [< 2048 us: 1.60/20.77] [< 4096 us: 0.80/7.99] [< 8192 us: 0.00/8.39] [< 16384 us: 3.00/13.38] [< 32768 us: 0.00/4.99] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) CPU 9 duty cycles/s: active/idle [< 16 us: 4.39/0.60] [< 32 us: 1.20/0.40] [< 64 us: 0.40/1.20] [< 128 us: 0.00/0.40] [< 256 us: 0.00/0.40] [< 512 us: 0.00/0.00] [< 1024 us: 0.00/0.20] [< 2048 us: 0.00/0.00] [< 4096 us: 0.00/0.00] [< 8192 us: 0.00/0.20] [< 16384 us: 0.00/0.20] [< 32768 us: 0.00/0.20] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) Core 5 C-state residency: 0.00% (C3: 0.00% C6: 0.00% C7: 0.00% ) CPU 10 duty cycles/s: active/idle [< 16 us: 152.36/63.30] [< 32 us: 95.65/12.38] [< 64 us: 9.19/23.56] [< 128 us: 6.79/8.99] [< 256 us: 33.75/28.95] [< 512 us: 2.00/45.53] [< 1024 us: 3.59/82.67] [< 2048 us: 0.80/12.58] [< 4096 us: 0.80/5.59] [< 8192 us: 0.20/6.39] [< 16384 us: 1.80/7.19] [< 32768 us: 0.00/4.59] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) CPU 11 duty cycles/s: active/idle [< 16 us: 3.99/1.40] [< 32 us: 0.40/0.20] [< 64 us: 0.00/0.40] [< 128 us: 0.00/0.40] [< 256 us: 0.00/0.00] [< 512 us: 0.00/0.00] [< 1024 us: 0.00/0.00] [< 2048 us: 0.00/0.00] [< 4096 us: 0.00/0.00] [< 8192 us: 0.00/0.20] [< 16384 us: 0.00/0.00] [< 32768 us: 0.00/0.20] CPU Average frequency as fraction of nominal: 102.89% (3599.99 Mhz) *** Sampled system activity (Thu Feb 5 21:18:40 2015 +0100) (5003.72ms elapsed) *** ------------------------------------------------------------------------------------------------------- So as you can see a huge XHCI consumption. now a way to stop that would be nice. It is faster then before but still not very usable tough. Link to comment Share on other sites More sharing options...
jamiethemorris Posted February 5, 2015 Share Posted February 5, 2015 Ok things are getting stranger..... I removed the GenericUSB3 kext and did a comboupdate of 10.10.2 Restarted and so on. I started VM-Ware and was expecting very slow start of my guest OS. But to my surprise it booted just instantly and whili it was booting I issued the your powermetrics. I could not use my mouse nor keyboard for half a minute and then it was back again. VM-Ware running and mouse and keyboard back. Here is the output: ------------------------------------------------------------------------------------------------------- So as you can see a huge XHCI consumption. now a way to stop that would be nice. It is faster then before but still not very usable tough. Yeah that's pretty insane. Here's my MacMini6,2 at work for comparison: Vector 0x73(XHC1): 418.18 interrupts/sec The reason the KB+M froze is probably because you're plugged into the USB3 port. Can you post an ACPI dump from Clover? Press F4 at the Clover menu and you will find the files in EFI/EFI/Clover/ACPI/origin. Link to comment Share on other sites More sharing options...
Edkroket Posted February 5, 2015 Share Posted February 5, 2015 Yeah that's pretty insane. Here's my MacMini6,2 at work for comparison: Vector 0x73(XHC1): 418.18 interrupts/sec The reason the KB+M froze is probably because you're plugged into the USB3 port. Can you post an ACPI dump from Clover? Press F4 at the Clover menu and you will find the files in EFI/EFI/Clover/ACPI/origin. No KB+M are in black USB-ports but I noticed that I added FixUSB button in Clover configurator. I guess that's why VM-Ware was running. I now booted without it. Started my guest OS and it had KP in guest OS. I'm running OSX 10.6.8 server as guest. Here is ACPI dump ACPI dump origin .zip Link to comment Share on other sites More sharing options...
jamiethemorris Posted February 5, 2015 Share Posted February 5, 2015 No KB+M are in black USB-ports but I noticed that I added FixUSB button in Clover configurator. I guess that's why VM-Ware was running. I now booted without it. Started my guest OS and it had KP in guest OS. I'm running OSX 10.6.8 server as guest. Here is ACPI dump This section of your DSDT looks relevant: If (_OSI ("Windows 2009")) { Store (0x0C, OSYS) } If (_OSI ("Windows 2012")) { Store (0x0D, OSYS) } If (_OSI ("Linux")) { Store (0x01, OSYS) } If (_OSI ("FreeBSD")) { Store (0x02, OSYS) } If (_OSI ("HP-UX")) { Store (0x03, OSYS) } If (_OSI ("OpenVMS")) { Store (0x04, OSYS) } If (LGreaterEqual (OSYS, 0x0D)) { If (LEqual (XCNT, 0x00)) { ^PCI0.XHCI.XSEL (0x00) Store (0x84, IO80) Increment (XCNT) } } Else { If (LEqual (OSYS, 0x0C)) { If (LEqual (ECNT, 0x00)) { ^PCI0.XHCI.ESEL () Increment (ECNT) } } Else { Store (OSYS, IO80) } } } I don't really know what it's doing but there's obviously an operation related to XHCI that does not happen in OSs other than Windows 7 and 8. I'm posting a DSDT for you to try - This is only temporary just to test, but If this works hopefully Andrew can add it to the X99 SSDTs (I don't really know how to inject this with SSDT). Make sure GenericUSBXHCI is removed, then put the DSDT in /EFI/Clover/ACPI/patched and make sure the FixDarwin option is DISABLED in Clover. If it's enabled this patch will do absolutely nothing. BTW here's what I did: I just added this to the _INI method: If (_OSI ("Darwin")) { Store (0x0E, OSYS) } Since it's just checking for OSYS to be greater than or equal to 0x0D it should be able to use whatever that XHCI thing is that it's using for Windows 8. Let me know how it goes! DSDT_Edkroket.aml.zip Link to comment Share on other sites More sharing options...
Edkroket Posted February 5, 2015 Share Posted February 5, 2015 This section of your DSDT looks relevant: If (_OSI ("Windows 2009")) { Store (0x0C, OSYS) } If (_OSI ("Windows 2012")) { Store (0x0D, OSYS) } If (_OSI ("Linux")) { Store (0x01, OSYS) } If (_OSI ("FreeBSD")) { Store (0x02, OSYS) } If (_OSI ("HP-UX")) { Store (0x03, OSYS) } If (_OSI ("OpenVMS")) { Store (0x04, OSYS) } If (LGreaterEqual (OSYS, 0x0D)) { If (LEqual (XCNT, 0x00)) { ^PCI0.XHCI.XSEL (0x00) Store (0x84, IO80) Increment (XCNT) } } Else { If (LEqual (OSYS, 0x0C)) { If (LEqual (ECNT, 0x00)) { ^PCI0.XHCI.ESEL () Increment (ECNT) } } Else { Store (OSYS, IO80) } } } I don't really know what it's doing but there's obviously an operation related to XHCI that does not happen in OSs other than Windows 7 and 8. I'm posting a DSDT for you to try - This is only temporary just to test, but If this works hopefully Andrew can add it to the X99 SSDTs (I don't really know how to inject this with SSDT). Make sure GenericUSBXHCI is removed, then put the DSDT in /EFI/Clover/ACPI/patched and make sure the FixDarwin option is DISABLED in Clover. If it's enabled this patch will do absolutely nothing. BTW here's what I did: I just added this to the _INI method: If (_OSI ("Darwin")) { Store (0x0E, OSYS) } Since it's just checking for OSYS to be greater than or equal to 0x0D it should be able to use whatever that XHCI thing is that it's using for Windows 8. Let me know how it goes! Thanks I'll try that now. I tested it but does not change anything. Even without VW-Ware Running I have huge XHCI movements: **** Interrupt distribution **** CPU 0: Vector 0x53(XHCI): 186105.50 interrupts/sec Vector 0x72(GLAN): 175.49 interrupts/sec Vector 0x74(SAT1): 1160.87 interrupts/sec Vector 0x76(H000): 13.19 interrupts/sec Vector 0xdd(TMR): 77.15 interrupts/sec Vector 0xde(IPI): 1360.34 interrupts/sec So I guess I have to play in BIOS with some XHCI settings? There is section Peripherals: Legacy USB support - enabled XHCI Hand-off - enabled EHCI Hand-off - disabled Then Chipset section: XHCI Mode - Auto - Smart-auto - Off - Enabled So would it make sense to play with that? I also have constantly delays when opening finder or chose path to somewhere. here are the console errors: ReportCrash[415]: Invoking spindump for pid=61 wakeups_rate=179 duration=252 because of excessive wakeups Feb 5 22:41:18 Mac-Pro-van-Ed.local spindump[416]: Saved wakeups_resource.diag report for xrdd version ??? (???) to /Library/Logs/DiagnosticReports/xrdd_2015-02-05-224118_Mac-Pro-van-Ed.wakeups_resource.diag and this one most frequently: lock contention for shared file list item 0x610000174700 ?? Link to comment Share on other sites More sharing options...
jamiethemorris Posted February 5, 2015 Share Posted February 5, 2015 Then Chipset section: XHCI Mode - Auto - Smart-auto - Off - Enabled So would it make sense to play with that? I also have constantly delays when opening finder or chose path to somewhere. here are the console errors: ReportCrash[415]: Invoking spindump for pid=61 wakeups_rate=179 duration=252 because of excessive wakeups Feb 5 22:41:18 Mac-Pro-van-Ed.local spindump[416]: Saved wakeups_resource.diag report for xrdd version ??? (???) to /Library/Logs/DiagnosticReports/xrdd_2015-02-05-224118_Mac-Pro-van-Ed.wakeups_resource.diag and this one most frequently: lock contention for shared file list item 0x610000174700 ?? It's certainly worth a try to play with it. If you are having those interrupts without VMWare running (which I had already kind of assumed) this is probably causing issues for other things as well, not just VMs. It just might not be as noticeable. As for the console messages I have no idea what they mean or if they are even relevant to the problem. I know you're having KPs with genericusbxhci, but do you still have the interrupts when you're using it? Anyway try the kexts posted here instead of genericusbxhci and see if it helps http://www.insanelymac.com/forum/topic/286860-genericusbxhci-usb-30-driver-for-os-x-with-source/?p=2094519 Link to comment Share on other sites More sharing options...
davidahn Posted February 8, 2015 Share Posted February 8, 2015 Anyone try the Clover Haswell-E patch on anything other than an X99, like for example on an Intel C612 chipset? I'm struggling with a Supermicro X10DAX (C612) with dual Xeon E5-2699v3's. Maybe I'm not patching right, but from what I understand since r3131 Clover patches the kernel on the fly? I'm thinking the chipset is the problem rather than the CPU. I was using Clover 3142, Configurator 4.22.1, Haswell-E patch, and SkylineOSX's Yosemite/Clover guide. I now see Clover is up to r3156! I'll give it another try when I get to my other house. Is there an updated step-by-step tutorial on installing 10.10.1 or 10.10.2 using Clover? David Link to comment Share on other sites More sharing options...
jamiethemorris Posted February 8, 2015 Share Posted February 8, 2015 Anyone try the Clover Haswell-E patch on anything other than an X99, like for example on an Intel C612 chipset? I'm struggling with a Supermicro X10DAX (C612) with dual Xeon E5-2699v3's. Maybe I'm not patching right, but from what I understand since r3131 Clover patches the kernel on the fly? I'm thinking the chipset is the problem rather than the CPU. I was using Clover 3142, Configurator 4.22.1, Haswell-E patch, and SkylineOSX's Yosemite/Clover guide. I now see Clover is up to r3156! I'll give it another try when I get to my other house. Is there an updated step-by-step tutorial on installing 10.10.1 or 10.10.2 using Clover? David The haswell-e patch in clover should work, AFAIK it's the same cpu id. Dual 18 cores dude???? That thing is going to be a monster. Hopefully voodootscsync supports that many cores (in your case you would put 71 into the info.plist of the kext). Oh, and you'll probably need to use the mavericks version of appleacpiplatform and iopcifamily as well, just like the 5960x users. What is the error you're running into? I would really like to see a build like that working. Link to comment Share on other sites More sharing options...
davidahn Posted February 9, 2015 Share Posted February 9, 2015 @jamiethemorris, thanks for the pointers... I'll try the Mavericks versions of appleacpiplatform and iopcifamily. I modded the VoodooTSCsync to 35, wasn't sure what to do in the case of dual CPUs. I'll try 71 instead. As for the specific error I'm not sure... I run into KPs after Clover boot loader, before the installer's welcome screen. How do I get the info you all need when I get my kernel panic? Where do I find it? I've been taking photos of the screen, but I'm sure there's a log file somewhere? I've been studying this thread, I'm just not sure if I followed all the steps correctly. I wasn't sure if it was the chipset (C612), the CPU (E5-2699v3), or something I did wrong in creating my USB stick. I was really excited to find this thread because at least it's the right CPU class! I think I'll start over and remake my Clover installer USB stick. Any pointers on a step-by-step guide to the creation of my installer USB stick, or is SkylineOSX's guide OK? Since I can't load my Yosemite installer, would it be helpful to install Clover then 10.10.2 directly to the Hackintosh boot volume from my MacBook Pro rather than using a USB stick installer, then try adding kexts and post-installing? Link to comment Share on other sites More sharing options...
Rampage Dev Posted February 9, 2015 Share Posted February 9, 2015 Mac OS X has a hard code 32 Core/Thread Limit so pushing past that Limit issues appear. Not saying it will not work. Disable HT in the BIOS and go from there. Also use the install guide in my sig below. You will Need the kexts from the x99 DMG as well as the Clover Config. I would start with 10.9.5 first. 3 Link to comment Share on other sites More sharing options...
jamiethemorris Posted February 9, 2015 Share Posted February 9, 2015 @davidahn, post a picture of the kernel panic. Link to comment Share on other sites More sharing options...
davidahn Posted February 10, 2015 Share Posted February 10, 2015 Mac OS X has a hard code 32 Core/Thread Limit so pushing past that Limit issues appear. Not saying it will not work. Disable HT in the BIOS and go from there. Also use the install guide in my sig below. You will Need the kexts from the x99 DMG as well as the Clover Config. I would start with 10.9.5 first. Thank you, Rampage Dev. That's depressing. So of 72 threads I can use 32 (44%)? I guess 32 of 36 cores isn't too shabby, but no hyper-threading. Bummer. I'll still try though, 'cause I'm a raging optimist. I'll try your install guide, thank you! Link to comment Share on other sites More sharing options...
Recommended Posts