Experiencing Kernel Panics
About every other day, my MBP has been experiencing kernal panics. I've tried to look for the log in the Library, and even attempted to get the report after the OS X restarts, but haven't been successful.
There is no log record in the Library/Logs/. Where is it?
What the hell is going on? This thing is less than a year old and this should not be happening.
There is no log record in the Library/Logs/. Where is it?
What the hell is going on? This thing is less than a year old and this should not be happening.
Comments
About every other day, my MBP has been experiencing kernal panics. I've tried to look for the log in the Library, and even attempted to get the report after the OS X restarts, but haven't been successful.
There is no log record in the Library/Logs/. Where is it?
What the hell is going on? This thing is less than a year old and this should not be happening.
Regardless of age, a machine should NEVER be kernel panicking. However, age does not define the likelyhood of a panic. Some machines panic out of the box, and some live for seven years without one. But I digress.
Try booting it off of an external HD, or at the very least, the restore DVD. See if it suffers the issue still. If so, you've got a hardware problem, take it to an Apple service center. If not, you have a software issue, backup and wipe your HD.
Here is where you get the kernel Debug Kit:
http://developer.apple.com/sdk/
I'd probably start with the hardware test and see if it raises any obvious errors. You haven't updated to 10.4.10 have you? It may be related to the buggy Airport drivers.
I'll give an update within a day or so.
Btw, thanks Marvin.
http://lists.apple.com/archives/Darw.../msg00021.html
Here is where you get the kernel Debug Kit:
http://developer.apple.com/sdk/
I'd probably start with the hardware test and see if it raises any obvious errors. You haven't updated to 10.4.10 have you? It may be related to the buggy Airport drivers.
You want him to install the debug kernel? And do two-machine debugging with gdb?
How about we ask him what hardware he has attached, and if he upgraded the memory.
No hardware is attached.
And the memory has not been upgraded.
You want him to install the debug kernel? And do two-machine debugging with gdb?
How about we ask him what hardware he has attached, and if he upgraded the memory.
I have updated to 10.4.10.
I'll give an update within a day or so.
Did these panics start happening only after 10.4.10 or do you remember having them on 10.4.9?
That's a bit odd that you get no panic log on every crash though. Just to make sure, you're checking the root library and not the user library?
And yes, I checked the root library.
Try this page, it generally gets good results and is regularly links to on discussions.apple.com.
They happened before 10.4.10, but not as consistantly. It's becoming more frequent as the weeks pass by.
And yes, I checked the root library.
I came across this:
http://lists.apple.com/archives/darw.../msg00082.html
"> As to why the backtrace doesn't show any more, it's because the
> framepointer linkage was terminated prematurely (zeroed)...could be
> stack corruption. If you can connect to the machine or examine a
> crashdump, you can try trawling the stack for traces. I'd also
> suggest verifying that you were, in fact, on the appropriate thread
> stack at the time of the panic.
Thank you. That was quite helpful. I imagine we're
doing something to induce random memory corruption,
which is not a good sign."
"Here's a simple thing. Set up a kernel coredump server on one of your
machines. It doesn't have to be fast, but it helps to have enough
hard disk space. On the client (i.e. panic-prone machine)
\tsudo nvram boot-args="debug=0xd44 _panicd_ip=10.0.40.2"
\t{and reboot for this to take effect.}
where you replace 10.0.40.2 with the IP address of your coredump
server. You must restart to enable this setting. Next time that
machine panics, you'll get a core dump."
It looks like a different issue but they still try to get a dump from the nvram to get at the panic info. Corrupted memory is still a possibility but it looks like it'll have to be a trial and error scenario. I've heard of people having overheating causing problems with ram slots - is this a Core Duo MBP and does it get particularly hot or are you doing something intensive before the KPs or is it completely random? Is it always while going online for example or has it happened using other programs?
Maybe try resetting your nvram by holding command-opt-p-r at boot (this resets the pram too) and see if you get a panic log the next time it crashes.
If you follow through the link in the previous post, that should help rule out some things. Try this app linked at that site to test out your memory:
http://www.kelleycomputing.net:16080/rember/
Nope.
No hardware is attached.
And the memory has not been upgraded.
Reseat the DIMMS just for good measure? And by no hardware attached, you mean nothing but the keyboard and mouse, right? No FireWire or USB thingies...