crazybyte Posted August 23, 2009 Share Posted August 23, 2009 Hello! I was triying snow leopard yesterday, but after a few minutes after the SO finish loading, it throw a kernel panic. This kernel panic are made by mdworker process (related to indexing service and spotlight). I don't want to disable Spothlight, but i can't solve this problem without disabling it. My dsdt are fully patched, have smbios injection and i only need 2 kext in the Extras folder (fakesmc and legacyhda). If i disable spotlight it works flawe . sly. Anyone can help me? Link to comment https://www.insanelymac.com/forum/topic/181306-mdworker-kernel-panic/ Share on other sites More sharing options...
tapper00` Posted August 24, 2009 Share Posted August 24, 2009 boot up in safe mode -x. Run kext utility. This will repair permissions and rebuild mkext for S/L/E and E/E. If it is successful, reboot. No more kernel panics. Link to comment https://www.insanelymac.com/forum/topic/181306-mdworker-kernel-panic/#findComment-1233478 Share on other sites More sharing options...
narcogen Posted September 10, 2009 Share Posted September 10, 2009 Hello! I was triying snow leopard yesterday, but after a few minutes after the SO finish loading, it throw a kernel panic. This kernel panic are made by mdworker process (related to indexing service and spotlight). I don't want to disable Spothlight, but i can't solve this problem without disabling it. My dsdt are fully patched, have smbios injection and i only need 2 kext in the Extras folder (fakesmc and legacyhda). If i disable spotlight it works flawe . sly. Anyone can help me? Multiple runs of kext utility, the standard suggestion for fixing kernel panics, didn't seem to help me. I did do two things, and since that, I haven't had any mdworker panics even though I've indexed several volumes more than once. I'm not sure which thing fixed the problem, or if it was both in combination. 1) Since I still had a working Leopard install, I deleted all the Spotlight information on all volumes, reset the exclusion list, and then rebuilt all the indexes in Leopard. (SL is still going to rebuild them but it seems to take less time than rebuilding from scratch in SL). 2) I boot into SL in 64 bit mode (-x64 -v). On reboot, the active mdworker process is a 64 bit process. There's also a 32 bit mdworker process, but it's idle. During indexing when booting in 64 bit mode I have yet to see another mdworker KP.. so far. Link to comment https://www.insanelymac.com/forum/topic/181306-mdworker-kernel-panic/#findComment-1259438 Share on other sites More sharing options...
Omakayd Posted April 30, 2010 Share Posted April 30, 2010 I had the same problem. in my case, the ram was not set to the correct (optimal) timing in the bios. I first thought the ram was defective because in win7 I was getting blue screens related to the memory. If the OP or anyone else has this kind of problem, first make sure the timing and voltages are correct in your bios. if that doesn't solve it, your ram may well be defective. Good Luck! Link to comment https://www.insanelymac.com/forum/topic/181306-mdworker-kernel-panic/#findComment-1459257 Share on other sites More sharing options...
Beerkex'd Posted April 30, 2010 Share Posted April 30, 2010 Try using Snow Leopard Cache Cleaner (google) to rebuild the Spotlight Index and do a deep cache clean while you're at it. It's a nice app for other maintenance tasks as well. I've used it since 10.5.2. Link to comment https://www.insanelymac.com/forum/topic/181306-mdworker-kernel-panic/#findComment-1459280 Share on other sites More sharing options...
Recommended Posts