In the 24 hours since I upgraded to 10.6.2 I have had #3 Kernel Panic reports asking me to shutdown and re-start the computer. I have verified the disk and permissions and it says it is O.K, but the problem persists. I have not installed anything else. the problem seems to occur when I put my computer to sleep and then try to use it again. Any ideas, help, guidance?
I want to join this thread. I get the same
exact kernel panic issue as the OP about once a week. I noticed that some people posted kernel panic logs that are not related to the OP's kernel panic, so I'm ignoring those.
I've done a hardware test and nothing comes up. My machine was upgraded from 10.5.8. The hardware has remained the same. It happens about once/week.
While I have the MS Keyboard with the latest MS drivers, I wasn't able to reproduce the kernel panic by pressing the key combo given by someone. I will, however, uninstall some the MS and Logitech drivers to see if that resolves the problem. I have Parallels 5, but the issue was happening before I had Parallels 5.
=========================
Interval Since Last Panic Report: 529792 sec
Panics Since Last Report: 2
Anonymous UUID: <removed>
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10C540
Kernel version:
Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
System model name: MacBookPro4,1 (Mac-F42C89C8)
My kernel panics seem to occur only when time machine is backing up. I have no problems at work when my airport is not available even if my MBP goes to sleep. It only happens at home when airport backs up data. Has anyone else seen this correlation in their KP's?
icab --
You really should start your own new thread . . .
Each person with KP's needs to be helped individually.
BUT, if I were you, I'd be looking very suspiciously at my Microsoft Keyboard.
You might want to unplug and uninstall the driver to see if things are better.
Thanks. I'll keep that in mind for next time. I've been experimenting: uninstalled IntelliType and removed the MS keyboard I was using. I will post an update once I've been using the machine for a while with no problems.
I had been getting this panic (the CIJScannerRegist variety at sched_prim.c:1471) about once every 36 hours since updating to 10.6.2.
I tracked the cause to the Cisco VPN client. My suspicion (from reading this board) is that there may be more than one "trigger" program for this panic. The MS Intellipoint SW might also be a trigger.
If this line shows up in your panic list of kernel extensions, you might have the same problem I did.
com.cisco.nke.ipsec 2.0.1
To fix this you need to uninstall the Cisco VPN client and ALSO remove the CiscoVPN extension from /System/Library/Extensions.
I did this and have not had a panic for over four days (with heavy use, including VMWare Fusion 3).
I do actually have a Canon MX850 (InkJet Printer/Scanner/Fax) that I have used with this machine in the past, but it has not been connected in months. The driver and "MP Navigator EX 1.1" software is still installed, though.
I don't think this is the source of the problem despite the error message.
I upgraded to 10.6.2 a couple of weeks ago and have been suffering from occasional Kernel Panics in my aluminum MacBook -before that, I did not even know what a kernel panic was. I do have the Cisco VPN Client, so I'll remove it. I will report whether this puts an end to the panics.
Adding your post to the bottom of another thread without providing more information is not the best way to get your question answered. I would suggest you start your own thread and post a crash dump if you are having kernel panics. This will get your question the attention it deserves and provide the information necessary for us to help you.
Just up update: I've been using my laptop since Dec 17, 2009 without getting any kernel panics. The only changes in my setup are that I uninstalled IntelliType drivers and stopped using the MS keyboard (the latter one just because I couldn't stand the swapped behavior of ALT and COMMAND keyboard keys).
It's not necessarily conclusive that the MS drivers were a problem, but hey, no more kernel panics so far.
