OS X crash report help ?

[Platform]

I do not know how this happened (watching TV, Mac just on) But when I came back the fans were on full blast (good, preventing overheating, but first time I heard it) and no response at all, hit the power button restarted fine, but no internet connection what so ever, another restart and everything fine (actually a very fast re-boot fastest ever and RAM and CPU usage very low now...)

So could some smart people tell me what this is/was

Thanks in advance

I got this from the OS X crash reporter

panic(cpu 0 caller 0x0003FEA8): zalloc: "kalloc.16" (3397120 elements) retry fail 3
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x0003FEA8 0x0002BB0C 0x00303AC0 0x00303C3C 0x00301CFC
0x003002DC 0x002FF60C 0x002FF60C 0x002B6224 0x002EA074 0x0008B950 0x000291C0 0x000233AC
0x000AC02C 0x00004002
Proceeding back via exception chain:
Exception state (sv=0x3E462500)
PC=0x9000B0A8; MSR=0x0200D030; DAR=0xE06B1000; DSISR=0x42000000; LR=0x9000AFFC; R1=0xBFFFEBF0; XCP=0x00000030 (0xC00 - System call)

The rest was just system info

 

[Platform]

Anyone

 

[bankshot]

The "zalloc" and "kalloc" tell me that it had a problem allocating memory. This may be due to a bug, or due to a hardware problem. If it's frequent, you might try testing your memory with the hardware test CD that came with the machine. Although in my experience, the hardware test isn't generally rigorous enough to find bad memory even when it exists.

Beyond that, check out this article: http://developer.apple.com/technotes/tn2002/tn2063.html

It's very technical, but walks you through the process of decoding the backtrace into a list of functions that were called to get to the panic situation. Sometimes that may help in understanding what may have happened.

 

[Platform]

The "zalloc" and "kalloc" tell me that it had a problem allocating memory. This may be due to a bug, or due to a hardware problem. If it's frequent, you might try testing your memory with the hardware test CD that came with the machine. Although in my experience, the hardware test isn't generally rigorous enough to find bad memory even when it exists.

Beyond that, check out this article: http://developer.apple.com/technotes/tn2002/tn2063.html

It's very technical, but walks you through the process of decoding the backtrace into a list of functions that were called to get to the panic situation. Sometimes that may help in understanding what may have happened.

Thanks...It has only happen once in 4+ months so.....