Brisc0 Posted February 18, 2009 Share Posted February 18, 2009 QUOTE(Layne_ @ Feb 8 2009, 01:38 AM) The problem is GenericCPUPowerManagement.kext, i have try for 2 week, with some test, and my computer crash after 12h, but now my computer are 4 days and 10:27 hour of continuation. I have GA-EP35-DS3RYou must delete GenericCPUPowerManagement.kext from Extensions Folder. This did not resolve the issue on my MSI Wind PC. I deleted the file last night after reading this post and experienced a panic due to "zalloc did gc" this morning. Well, I stand corrected. After I deleted "GenericCPUPowerManagement.kext", I did have a panic as stated above, but since that Panic I haven't had so much as a hick up in six days. My suggestion is to delete the kext as Layne suggests and then reboot. It has completely resolved the issue on my MSI Wind PC. Best of luck everyone! Link to comment Share on other sites More sharing options...
holyfield Posted February 18, 2009 Share Posted February 18, 2009 I installed my OSX86 again (iDeneb 1.4 - 10.5.6) and got great success, no crash any more. I had previously installed MacFUSE, it was required by some soft that i dont remember yet. Broably this might have related? I guess its related with this.. but might not. But one is sure, its not OSX related directly. something you have installed later causes it. Link to comment Share on other sites More sharing options...
MoonDogg Posted March 13, 2009 Share Posted March 13, 2009 I have the exact same kernel panic on a Dell e1505. I was on iDeneb 1.3 upgraded to 10.5.6 then I just blew it away with iPC 10.5.6 final and everything was working great... or so it seemed.. .and I am still getting this kernel panic. I was not getting it with 10.5.5. Any one figured it out to one thing yet? update... just read a few more post... I deleted the kext. now I am going to see what happens.. I'll report back.. update.... 25+ hours no panics.... so far so good... Link to comment Share on other sites More sharing options...
MoonDogg Posted March 30, 2009 Share Posted March 30, 2009 I have the exact same kernel panic on a Dell e1505. I was on iDeneb 1.3 upgraded to 10.5.6 then I just blew it away with iPC 10.5.6 final and everything was working great... or so it seemed.. .and I am still getting this kernel panic. I was not getting it with 10.5.5. Any one figured it out to one thing yet? update... just read a few more post... I deleted the kext. now I am going to see what happens.. I'll report back.. update.... 25+ hours no panics.... so far so good... well the panic has came back... any idea's? Link to comment Share on other sites More sharing options...
KirbySaysHi Posted March 31, 2009 Share Posted March 31, 2009 I've made at least a little progress. Previously, my machines were kernel panicking after 24hrs, like the first post said. Now, they panic about every 4 days. Luckily, my laptop is never on for that long, and my desktop I can force to reboot every few days. The key is that I was using Superhai's GenericCPUPowerManagement. When I replaced it with Superhai's newest power management kext, VoodooPower, my kernel panic frequency extended to 4.5ish days, which is where I am now. Until we discover the exact cause of what's going on here, I recommend everyone grab VoodoPower from Superhai. GenericCPUPowerManagement has been depricated. http://superhai.com/darwin.html Also.. sorry that I didn't reply for so long! I've had this solution for months, but once the new site updates were made, my account was literally broken. Password recovery just outright failed. Anywho, now I'm back! Link to comment Share on other sites More sharing options...
vrenlos Posted March 31, 2009 Share Posted March 31, 2009 I'm in the same boat, I get a zalloc KP every 3-4 days using Voodoo Power and the Voodoo 9.5 kernel. Link to comment Share on other sites More sharing options...
stellarola Posted April 4, 2009 Share Posted April 4, 2009 I know two other people who are having the same z allocation error. Link to comment Share on other sites More sharing options...
KirbySaysHi Posted April 5, 2009 Share Posted April 5, 2009 I know two other people who are having the same z allocation error. Have they any solutions? Link to comment Share on other sites More sharing options...
coldequation Posted April 11, 2009 Share Posted April 11, 2009 Have they any solutions? Depends on the version of VoodooPower and what type of machine you are using. On a MacBook Pro, I got zalloc panics (not zalloc did gc) and I uninstalled the kext (which was a damn shame as it kept my gonads from frying). On a gateway laptop, I was getting panics (zalloc did gc) about every 24 hours with 1.2.1 VoodooPower. I upgraded to VoodooPower 1.2.3 and deleted the OpenHaltRestart kext. I then installed the debug version of VoodooPower to get a trace for superhai. But all seems well (sofar!). So either the debug version doesn't cause zalloc issues, or OpenHaltRestart causes issues with VoodooPower, or I haven't given it enough time. I've just installed the non-debug version, and I'll leave it up over the next few days and see what happens. I'll update this thread if deleting OpenHaltRestart solves the zalloc did gc issue. Link to comment Share on other sites More sharing options...
vrenlos Posted April 22, 2009 Share Posted April 22, 2009 I completely removed VoodooPower and so far so good, I'll wait a few more days with my fingers crossed but I think that was it. Link to comment Share on other sites More sharing options...
Debil Posted April 27, 2009 Share Posted April 27, 2009 I'll update this thread if deleting OpenHaltRestart solves the zalloc did gc issue. So any update? I'm having this 24 hour panic problem too. Link to comment Share on other sites More sharing options...
dgoran Posted May 14, 2009 Share Posted May 14, 2009 So any update? I'm having this 24 hour panic problem too. For me with Dell 530 quad core the solution was to remove VoodooPower kext, now running smoothly or 72 straight and counting... Link to comment Share on other sites More sharing options...
audio_inside Posted May 31, 2009 Share Posted May 31, 2009 I'm almost certain it's power management. Here we have 3 options: it can be a bug in EFI v9, in patched DSDT or PowerManagement kexts. On my Dell Mini 9 N270 Atom system running 10.5.7 and built with DellEFI 1.1, removing the VoodooPower1.2.3z kext was enough to cure my problem. Here's what I have remaining: com.apple.kernel (9.7.0) com.apple.kpi.bsd (9.7.0) com.apple.kpi.dsep (9.7.0) com.apple.kpi.iokit (9.7.0) com.apple.kpi.libkern (9.7.0) com.apple.kpi.mach (9.7.0) com.apple.kpi.unsupported (9.7.0) com.apple.iokit.IONVRAMFamily (9.7.0) com.apple.driver.AppleNMI (9.7.0) com.apple.iokit.IOSystemManagementFamily (9.7.0) com.apple.iokit.ApplePlatformFamily (9.7.0) com.apple.kernel.6.0 (7.9.9) com.apple.kernel.bsd (7.9.9) com.apple.kernel.iokit (7.9.9) com.apple.kernel.libkern (7.9.9) com.apple.kernel.mach (7.9.9) com.apple.iokit.IOPCIFamily (2.6) com.apple.iokit.IOACPIFamily (1.2.0) com.apple.driver.AppleACPIPlatform (1.2.4) com.superhai.driver.SMBIOSResolver (1.0.7) com.apple.driver.decrypt (2.0.3) com.apple.iokit.IOGraphicsFamily (1.7.3) com.apple.BootCache (30.4) com.apple.iokit.IOHIDFamily (1.5.5) com.apple.security.TMSafetyNet (3) com.apple.nke.applicationfirewall (1.6.77) com.apple.security.seatbelt (107.12) com.apple.driver.AppleIntelCPUPowerManagement (76.0.0) com.apple.driver.AppleAPIC (1.4) com.apple.driver.AppleSMBIOS (1.4) com.apple.driver.AppleACPIButtons (1.2.4) com.apple.driver.AppleACPIPCI (1.2.4) com.apple.iokit.IOSMBusFamily (1.1) com.apple.driver.AppleACPIEC (1.2.4) com.apple.driver.AppleHPET (1.4) com.apple.driver.AppleRTC (1.2.3) com.apple.driver.AppleACPIBatteryManager (1.0.15) com.apple.driver.AppleACPIPS2Nub (1.0.0d1) com.apple.driver.ApplePS2Controller (1.1.0) com.apple.driver.ApplePS2Keyboard (1.2.0) com.apple.driver.AppleIntelIntegratedFramebuffer (5.3.0) com.apple.iokit.IONDRVSupport (1.7.3) com.apple.iokit.IOUSBFamily (3.4.3) com.apple.driver.AppleUSBUHCI (3.3.5) com.apple.iokit.IOATAFamily (2.0.1) com.apple.driver.AppleIntelPIIXATA (2.0.0) com.apple.driver.ApplePS2Trackpad (1.1.0) com.apple.driver.AppleEFIRuntime (1.2.0) com.apple.iokit.IONetworkingFamily (1.6.1) com.apple.driver.AppleIntelGMA950 (5.4.4) com.apple.driver.AppleUSBEHCI (3.4.3) com.apple.iokit.IOStorageFamily (1.5.6) IOSDHCIBlockDevice (1.0.0d1) com.apple.iokit.IOUSBUserClient (3.3.1) com.apple.driver.AppleUSBHub (3.4.0) com.apple.iokit.IOATABlockStorage (2.0.5) com.apple.iokit.IO80211Family (216.1) com.apple.driver.AirPortBrcm43xx (363.35.0) com.apple.driver.XsanFilter (2.7.91) com.psystar.driver.RealtekR1000 (1.8.1) com.apple.driver.AppleUSBComposite (3.2.0) com.apple.iokit.IOBluetoothFamily (2.1.6f8) com.apple.driver.AppleUSBBluetoothHCIController (2.1.6f8) com.apple.driver.AppleLPC (1.2.12) com.apple.driver.AppleSMC (2.2.1d2) com.apple.driver.IOPlatformPluginFamily (3.4.0d10) com.apple.driver.ACPI_SMC_PlatformPlugin (3.4.0d10) com.apple.driver.AppleUpstreamUserClient (2.7.5) com.apple.kext.OSvKernDSPLib (1.1) com.apple.iokit.IOAudioFamily (1.6.5fc3) com.apple.driver.AudioIPCDriver (1.0.6) com.apple.iokit.IOHDAFamily (1.3.3a1) com.apple.driver.AppleHDAController (1.3.3a1) com.apple.Dont_Steal_Mac_OS_X (6.0.3) com.apple.driver.AppleHDA (1.3.3a1) com.apple.driver.DiskImages (199) com.apple.iokit.IOSCSIArchitectureModelFamily (2.0.9) com.apple.filesystems.autofs (2.0.2) com.apple.iokit.IOSerialFamily (9.4) com.apple.iokit.IOBluetoothSerialManager (2.1.6f8) com.apple.driver.IOBluetoothA2DPAudioDriver (2.1.6f8) com.apple.driver.IOBluetoothSCOAudioDriver (2.1.6f8) com.superhai.driver.ClamshellDisplay (1.0.1) com.apple.driver.AppleUSBMergeNub (3.4.3) Link to comment Share on other sites More sharing options...
puffo83 Posted June 4, 2009 Share Posted June 4, 2009 Removed VoodooPower too… Still running after 2 1/2 days. Looks like an ok solution… Link to comment Share on other sites More sharing options...
Kunal2139 Posted June 6, 2009 Share Posted June 6, 2009 I'm having this issue too. How do you remove Voodoo Power? What seems to be the best fix? Thanks! Link to comment Share on other sites More sharing options...
puffo83 Posted June 8, 2009 Share Posted June 8, 2009 I'm having this issue too. How do you remove Voodoo Power?What seems to be the best fix? Thanks! Hi, VoodooPower is a Kernel Extensions (*.kext file) you add optionally to your system if you need better power management. If you didn't add it, you don't have it. To me removing VoodooPower helped a lot. No more kernel panics. Link to comment Share on other sites More sharing options...
Recommended Posts