Brand-new Santa Rosa MBP, Kernel Panics related to Airport

Question

Brand new MBP (2.4GHz 15"), anytime I do anything online I get a kernel panic. I am connecting to a WPA-2 network that is supporting stable connections to several other computers, including another (albeit older) MBP. I have no third-party sw installed, I have no peripherals attached, I have installed all available updates, I have run disk verify/repair and permission repair via the install disk and the problem persists. I have also physically inspected the RAM modules to make sure they're situated properly.
The console log shows mbuf failures (I can only access the log if I have the airport off) that are similar to the problem Apple identified in 10.4.8 but were supposedly solved w/ 10.4.9 (see http://docs.info.apple.com/article.html?
artnum=303712).
So two questions: anyone else out there experiencing this on a WPA-2 or other network? If so, any fixes that don't involve me having to return this computer to Apple? If this is a QA issue that could have been prevented through better testing prior to release...

Answer 1

Hey Don (and others)
I bought a new Santa Rosa MPB yesterday and am suffering the same issues. My office uses WPA (not sure about the specifics) and within the first hour of ownership (of my FIRST Apple machine ever) I suffered kernel panics.
I get back to my workplace from the local Apple Store, get all set up and online. I run all the software updates fine. Next, I shut the lid and proudly carry my new Mac to a meeting. Open the lid and notice I can't get online. I stop and start the wireless and immediately get a kernel panic.
Restart, and it happens again.
Restart, and I can get online finally. With the help of some coworkers I get to the panic.log file and notice the panic happens around the Airport.
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2572b9f8 : 0x128d08 (0x3cc224 0x2572ba1c 0x131de5 0x0)
0x2572ba38 : 0x1a4a55 (0x3d2638 0x0 0xe 0x3d1e5c)
0x2572bb48 : 0x19aeb4 (0x2572bb60 0x2572bb68 0xb92ebbb4 0x6)
0x2572bbf8 : 0x3b3c5e1e (0x17 0x23e1a107 0x6 0x3e77a380)
0x2572bdd8 : 0x3b3c8059 (0x23b052c8 0x1 0x4b285c 0x6)
0x2572bf08 : 0x39b543 (0x23b05000 0x4174b00 0x1 0x3c341e8)
0x2572bf58 : 0x39a715 (0x4174b00 0x135eb4 0x0 0x3c341e8)
0x2572bf88 : 0x39a44b (0x40e9200 0x0 0xee6ae98 0x13818b)
0x2572bfc8 : 0x19ad2c (0x40e9200 0x0 0x19e0b5 0x42bee60) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(230.8.5)@0x3b394000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x634000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5a4000
dependency: com.apple.iokit.IO80211Family(160.2)@0x3b375000
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386
Later I discovered that the office uses WPA. So I bring the MBP home and connect via my WEP encrypted WiFi, and haven't had the same problem once (so far it's been over 24 hours, with many "sleeps" in the meantime).
I did have another panic, waking up out of a 'deep sleep' this morning (after having had the lid shut for 6 hours)...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleACPIPlatform(1.0.10)@0x606000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5f2000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x602000
ACPI seems to have crashed something, hoping I can recreate this tomorrow morning.
At this point, I'm just glad to see I'm not the only owner of a the new MBP's suffering the same WPA-related crashes. Also, I do wonder if I got a replacement if it would solve anything, though I'm up for trying and may try tomorrow.
Overall, a bit frustrated (especially since after craving a MBP for months and holding out for the new models, to have these issues).
Oh, I also have a 2.4ghz 15"
-r-