Help - Search - Members - Calendar
Full Version: Kernel panic after long periods of use...
InsanelyMac Forum > OSx86 Project > Post-Installation Discussion > OSx86 Leopard (10.5)
blkhockeypro19
OK, so I have a totally vanilla system using boot-132/EFI partition guide whcih loads the boot-132 files off that EFI system partition.

So the only modified kexts I use for my dell e520-

IOATAFamily.kext (necesary for my system to boot and detect hard drives.) On EFI partition.

IntelCPUMDisabler.kext (Necesary obviously) On EFI partition.

dsmos.kext (necesary obviously) On EFI partition.

SMBIOSEnabler.kext (Replacement for modified AppleSMBIOS.kext) On EFI partition.

HDAEnabler.kext (used in place of ALCinject.kext) On EFI Partiton.

IONetworkingFamily.kext (Used to fix "Backup volume not found" time machine error) In REAL extensions folder because it doesnt load properly from the EFI partion.

AppleHDA.kext (sigmatel stac9227 patched kext) In REAL extensions folder because it wont load properly from the EFI partition...if anyone knows of a plist patch for stac9227 audio so I can load it from the EFI partition, please tell me =P


************************************************************

Ok, so here my problem. I have NEVER kernel paniced before the past 2 days, but I've been leaving my computer running for 24-48 hours on end downloading a torrent in vmware fusion 2.0 windows XP 32-bit pro. I go to school, I come home and the system is locked up and I'm asssuming it kernel paniced. The first time it kernel paniced was when it had been on for a little over 24 hours. I was using ichat and all of the sudden about a quarter of the kernel panic screen appeared. it froze before the panic "banner" could make it all the way down the screen. The last 2 times I have come home from school after about 30 hours of continuous use in vmware and I notice that the "flurry" screen saver it frozen and the system is un usable so I'm ASSUMING that it kernel paniced. Anyways, I figured I'd take a pic of my console/ You can see that it has been locked up (paniced?) since 7:23:00 AM this morning. I got home from school and rebooted and you can see because thats around 2:24:00 PM. Does anyone know whats causing these panics? (See attatched pic)





pax1234
I think type in "debug=0x100" in the Darwin boot up prompt will give you a better indication of what caused the kernel panic when it happens. It will give you a back trace message along with the grey screen. Not all the times but most of the times when I had my kernel panic problems. The console didn't have anything on it.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.