[chucker]

I've just had my third. It should be noted that I've only had this machine since Friday afternoon, so that makes it an average of almost once per day. Not cool.

Now, at first I thought it would simply be a result of the SpeedIt kernel extension I've been using. It's clearly at early development stage, and it makes sense that it could cause issues. The first two panic logs gave no indication at all:

Sat May 6 17:12:30 2006 panic(cpu 0 caller 0x0034FBE6): mbuf address out of range 0x80 Backtrace, Format - Frame : Return Address (4 potential args on stack) 0x1454bb04 : 0x128b5e (0x3bbeb8 0x1454bb28 0x131bbc 0x0) 0x1454bb44 : 0x34fbe6 (0x3db914 0x80 0x1454bb64 0x198b25) 0x1454bb64 : 0x22e673 (0x1 0x2 0x0 0x0) 0x1454bc44 : 0x22d460 (0x4702228 0x34 0x1 0x2202a8c0) 0x1454be14 : 0x222007 (0x26320900 0x14 0x1454bf14 0x31caf506) 0x1454be54 : 0x223a8b (0x26320900 0x14 0x6 0x0) 0x1454bf64 : 0x211109 (0x26320900 0x26320900 0x42cb5c 0x135798) 0x1454bfa4 : 0x1f773d (0x3564004 0x26320900 0x26306816 0x1) 0x1454bfd4 : 0x197a21 (0x0 0x0 0x2ea1920 0x2a0a9000) Backtrace terminated-invalid frame pointer 0x0 Kernel version: Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386 ********* Mon May 8 02:07:53 2006 panic(cpu 0 caller 0x0019CAEF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers: CR0: 0x8001003b, CR2: 0x698be550, CR3: 0x01630000, CR4: 0x000006e0 EAX: 0x698be54c, EBX: 0x2621a100, ECX: 0x2621a144, EDX: 0x0d5b623c ESP: 0x698be550, EBP: 0x1463bc24, ESI: 0x00000000, EDI: 0x2621a100 EFL: 0x00010202, EIP: 0x0034fcbd, CS: 0x00000008, DS: 0x14630010 Backtrace, Format - Frame : Return Address (4 potential args on stack) 0x1463bac4 : 0x128b5e (0x3bbeb8 0x1463bae8 0x131bbc 0x0) 0x1463bb04 : 0x19caef (0x3c1340 0x0 0xe 0x3c10f8) 0x1463bbb4 : 0x197b53 (0x1463bbc8 0x1463bc24 0x34fcbd 0x350048) 0x1463bbc0 : 0x34fcbd (0x350048 0x2e90010 0x2e90010 0x14630010) 0x1463bc24 : 0x34ffe7 (0x2621a100 0x0 0x3b85aa8 0x1c91) 0x1463bc44 : 0x22d2ff (0x2621a100 0x1c48 0x1 0x2202a8c0) 0x1463be14 : 0x222007 (0x2621a100 0x14 0x1463bf14 0x32e4f506) 0x1463be54 : 0x223a8b (0x2621a100 0x14 0x6 0x0) 0x1463bf64 : 0x211109 (0x2621a100 0x2621a100 0x42cb5c 0x135798) 0x1463bfa4 : 0x1f773d (0x3571804 0x2621a100 0x26394816 0x1) 0x1463bfd4 : 0x197a21 (0x0 0x0 0x2e67ac8 0x2621a100) Backtrace terminated-invalid frame pointer 0x0 Kernel version: Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386

But now I've had another, and this time, it clearly puts the blame on AirPort.

Mon May 8 15:35:53 2006 panic(cpu 0 caller 0x0019CAEF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers: CR0: 0x8001003b, CR2: 0x7578493c, CR3: 0x00d56000, CR4: 0x000006e0 EAX: 0x75784938, EBX: 0x259b0100, ECX: 0x259b0144, EDX: 0x49381600 ESP: 0x7578493c, EBP: 0x13d2bce4, ESI: 0x00000000, EDI: 0x00000028 EFL: 0x00010202, EIP: 0x0034fcbd, CS: 0x00000008, DS: 0x03310010 Backtrace, Format - Frame : Return Address (4 potential args on stack) 0x13d2bb84 : 0x128b5e (0x3bbeb8 0x13d2bba8 0x131bbc 0x0) 0x13d2bbc4 : 0x19caef (0x3c1340 0x0 0xe 0x3c10f8) 0x13d2bc74 : 0x197b53 (0x13d2bc88 0x13d2bce4 0x34fcbd 0x3a0048) 0x13d2bc80 : 0x34fcbd (0x3a0048 0x10 0x10 0x3310010) 0x13d2bce4 : 0x34ffe7 (0x259b0100 0x23b2ad0 0x4a1000 0x1) 0x13d2bd04 : 0x93cac9 (0x259b5f00 0x880 0x0 0x95e36a) 0x13d2bd84 : 0x93cc4e (0x269e29c 0x269f938 0x70000 0x13d2bdb8) 0x13d2bdc4 : 0x9414b5 (0x122d6004 0x0 0x13d2be24 0x967679) 0x13d2be24 : 0x942bc6 (0x269e46c 0x0 0x13d2be74 0x19ab92) 0x13d2bf14 : 0x38d7dd (0x269e29c 0x27d3e80 0x1 0x253b280) 0x13d2bf64 : 0x38c989 (0x27d3e80 0x135d18 0x0 0x253b280) 0x13d2bf94 : 0x38c6ad (0x27d7600 0x3000006 0x0 0x450) 0x13d2bfd4 : 0x197a21 (0x27d7600 0x0 0x253b4f8 0x259b0100) Backtrace terminated-invalid frame pointer 0x0 Kernel loadable modules in backtrace (with dependencies): com.apple.driver.AirPortAtheros5424(102.4)@0x92000 0 dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x693000 dependency: com.apple.iokit.IOPCIFamily(2.0)@0x565000 dependency: com.apple.iokit.IO80211Family(112.1)@0x907000 Kernel version: Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386

(Emphasis mine.)

Now, there's still a slim chance that AirPort was merely active at the same time (I've been connected through it all along) and that the real culprit was, indeed, SpeedIt. But maybe there's an actual stability problem with AirPort? Does anyone else experience such hard crashes due to AirPort connectivity?

(15-inch MacBook Pro, 2 GHz, 1 GB single-slot memory, 7200 RPM 100 GB BTO hard drive, no additional hardware whatsoever, AirPort, playing iTunes music via Bonjour sharing, having various other things running, including a file transfer via SMB*. All the latest updates.)

*) So it could also be a problem with Samba, which is also implemented at the kernel level.

[alcimedes]

So what happens when you disable/uninstall SpeedIt?

[chucker]

Originally Posted by alcimedes So what happens when you disable/uninstall SpeedIt?

Well, I can't reproduce the kernel panic; it appears at random, while doing nothing unusual in particular. I have installed a different version of SpeedIt now and will see if it happens again: if it doesn't (within two or three days), I will assume that the old version was the culprit; if it does happen again, I'll try removing SpeedIt altogether, and then see what happens. But the AirPort reference in the backtrace has me flubbergusted.

[torifile]

chucker, I'm sure you've tried this already, but have you done the usual stuff like pulling out 3rd party RAM, starting over from scratch, etc?

[chucker]

Originally Posted by torifile chucker, I'm sure you've tried this already, but have you done the usual stuff like pulling out 3rd party RAM, starting over from scratch, etc?

There's no 3rd-party RAM; like I said, the hardware is all exactly what Apple sent me. No USB or FireWire devices attached. Just an AirPort network, a MagSafe cable, and an iPod's earphones

Starting from scratch, well, I could do that. The thing is, I haven't really done much that could possibly cause this. There's very little 3rd-party software.

I'll keep formatting as a last resort option, but I'd really rather not, as kernel panics aside, the experience is very good.

[TednDi]

I have been experiencing kernal panics now as well. I have had my MBP for 3 weeks now and I have had about 5 kernal panics.

The last one I was hardwired into a network with Airport off.

Safari was running. This leads me to believe that it might be Safari related.

This morning I had another. The only thing open was safari and I was connected to an airport network.

I have 2 gigs of ram and I have run all apple diagnostics with everything appearing ok as well.

[Engine Joe]

You guys are making me nervous; my new 17" MBP is supposed to be delivered today... after my steady as a rock iBook and PM (where combined I've seen maybe 5 KPs in the combined 3 years I've had them), the thought of such instabillity is worrying.

[billybobsky]

I can't say I have ever had a kernel panic on my PB...

Is there a way to report kernel panics like bugs?

[chucker]

Originally Posted by billybobsky Is there a way to report kernel panics like bugs?

Yep. You can report them to Apple in the same way you can report any application crash (as of Panther).

Since installing the different version of speedit, I have yet to experience any further kernel panics.

[Enki]

Originally Posted by chucker Since installing the different version of speedit, I have yet to experience any further kernel panics.

Ding! Ding! Ding! And now we have confirmation on why Apple discourages kernel extension drivers! Bugs there crash machines and can give Apple the black eye instead of the kext coder. Confirmation after the fact and initial complaint does little to make up for the bad press of "I've had xxx KPs!!!"

I don't want pick on you, Chucker, because overall your post was fairly balanced and asked the right questions before you finished it. But too many yaa-hoos are just going to cite your first line and ignore the rest.

I've got a similar problem.

brand new mac book pro, bought today. kernel panic about 8 times so far, in as many hours
same 'mbuf address out of range' in the panic log, and this only happens when using the airport.

is there a fix for this? a quick search on google suggests that a replacement logic board is needed, or something is wrong in 10.4.7.

[alcimedes]

I think it's a 10.4.7 issue with some MacBook Pro's. I have no idea if there's a way to downgrade it though.

Although if you just got it and you can live without it for a week or so, I'd send it back. If something is wrong with the logic board I'd want it replaced sooner rather than later.