[Annette310]

I had my 1st kernal panic on my 1 week old C2d Macbook!

Here's what the log says:

Sun Nov 19 22:42:28 2006
panic(cpu 0 caller 0x0035AD9B): mbuf address out of range 0x6c483024
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0xb803ab8 : 0x128d08 (0x3c9a14 0xb803adc 0x131de5 0x0)
0xb803af8 : 0x35ad9b (0x3ea14c 0x6c483024 0xb803b68 0x1416ad)
0xb803b18 : 0x239999 (0x1 0x2 0x1d27fc00 0x2147c54)
0xb803c28 : 0x238541 (0x2c48710 0x28 0x1 0x402a8c0)
0xb803e08 : 0x22d264 (0x1d27fc00 0x14 0xf7c64f65 0xf53)
0xb803e48 : 0x22ecc5 (0x1d27fc00 0x14 0x6 0x0)
0xb803f58 : 0x21c441 (0x1d27fc00 0x1d27fc00 0x44407c 0x1a1f6f)
0xb803f98 : 0x202cfe (0x2329004 0x1d27fc00 0x1d0fb816 0x1)
0xb803fc8 : 0x19a6ec (0x0 0x0 0x19d0b5 0x1cd9f78) Backtrace terminated-invalid frame pointer 0x0

Kernel version:
Darwin Kernel Version 8.8.3: Wed Oct 18 21:57:10 PDT 2006; root:xnu-792.15.4.obj~4/RELEASE_I386

Does anyone know what went wrong?? And what can I do to prevent this from happening again??

BTW, I'm new to macs so be gentle Thanks!

[clairejr]

Hi Annette,

Welcome and congratulations on becoming a Mac user.

Kernel attacks happen, sometimes because of bad RAM or external devices, especially USB connectors. Did you connect anything to a USB port just before the attack? I sometimes had the problem with an LG memory stick that I finally traded for a more stable USB key.

Repair permissions on your MacBook with Disk Utility - that might clear up any system problems you're having. If you have another kernel attack, make a note of what you were doing just before it happened, and post back.

Claire

[osiris]

Or sometimes they inexplicably occur, at least once, to never appear again. I wouldn't worry too much, unless it happens again.

I also had a KP during the second day of my new MBP's life. It's been a few weeks now, and I have not turned it off once since then.

[rickey939]

Congratulations!

[TheoCryst]

I wouldn't be concerned. Like osiris said, sometimes they are spontaneous one-time errors, and you will never see them again. If it happens again, especially if it happens a few times in the next few days, then you might have cause for concern. But otherwise, welcome to the cult!

[awaspaas]

It's spelled kernel, with an e.

[drp]

panic(cpu 0 caller 0x0035AD9B): mbuf address out of range 0x6c483024
Backtrace, Format - Frame : Return Address (4 potential args on stack)

An mbuf is a type of kernel buffer that is primarily used by the network stack for storing network packets that are in the process of being sent or received.

Looks like the system was asked to process a buffer that was outside the region of memory mbufs are normally allocated in. (Given that mbufs are typically only within kernel space, the address could be pointing to user space or device space, but that's not really relevant)

In addition, the backtrace you got was pretty much garbage, that implies a corrupt stack or stack pointer.

Both of these taken together are unlikely to happen in normal operation. This would imply that there is a hardware issue going on. Most likely the memory itself was corrupted.

Of course, it could be completely random -- perhaps a stray alpha particle corrupting a bit in your memory

In real life, your best course of action is the run Apple's hardware diagnostics on the system. There is a checkbox to run extensive tests, which should be chosen in this case.

If the machine can pass the tests several times in a row, it was probably a fluke. If the tests fail, or you have additional panics over the next few days, you've probably got a hardware failure that Apple should fix.

[Annette310]

Thanks for the info! I haven't had a KP since then. Sorry for the spelling error I ran the apple hardware test and my macbook passed.