Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Hardware - Troubleshooting and Discussion > Mac Notebooks > Airport Causing Kernel Panics -- Anything I Can Do To Ensure A Fix?

Airport Causing Kernel Panics -- Anything I Can Do To Ensure A Fix?
Thread Tools
Fresh-Faced Recruit
Join Date: Oct 2005
Status: Offline
Reply With Quote
Dec 6, 2005, 06:36 PM
 
I have one of the new 17" DL PBs, and have for about a month. First Mac, and it's great. When it works. The problem is that it randomly experiences kernel panics. Grey screen, instructions to reboot, the whole deal. I tried everything I could to fix it--Reset PMU, PRAM, reinstalled OSX, stopped using my USB trackball mouse. No go. At one point it went a week without crashing, and I almost thought it was fixed. But, no, it did it a few more times. I contacted AppleCare. They walked me through a zero-format and reinstall. This worked for about three days, then it kernel panic'd. I contacted AppleCare again, they had me ship in the computer for repair. They had it for less than a day, and shipped it back out. There were some DHL issues in getting the computer delivered, but I finally got it back today.

They didn't do anything--returned it "Unable to duplicate issue." I put the panic logs (both from before and after the reformat--I thought to e-mail the panic log to myself before I reformatted a second time) on my desktop. I'd read them to the AppleCare guy on the phone. But apparently, since it didn't crash in the 12 hours or so that they had it, there was no fixable problem.

So I called AppleCare again, and after initially refusing to just ship it back and have them "keep it a while longer" so that they might fix it if they can actually see the system panic, they put me in contact with a product specialist who had me e-mail him the logs (first tech had told me they were already in the system), and said he'd specifically note them on the internal work order. So now I'm shipping it back. I've requested they call me if they again decide to ship it back unfixed, but I'm not sure what I could do from there.

I guess my issue is this--I've owned the computer for four weeks. Of those, one week so far has been spent entirely on getting the computer to/from Apple trying to get it fixed. I haven't installed any RAM, haven't installed any programs, every single kernel panic refers directly back to the Airport, and I'm completely at a loss as to how to ensure that this gets fixed. I can't rely on the PB because it could crash at any time, but I don't really want to keep sending it back to Apple trying to get them to duplicate the issue. Any advice? Anything else I could include or do to make sure it doesn't just get returned?
     
Fresh-Faced Recruit
Join Date: Oct 2005
Status: Offline
Reply With Quote
Dec 6, 2005, 06:38 PM
 
(duplicated post removed)
     
Moderator
Join Date: Oct 2001
Location: San Jose, CA
Status: Offline
Reply With Quote
Dec 6, 2005, 08:14 PM
 
Can you post the log? I was going to say a problem with your RAM, but if the log refers to Airport, it's possible you have a bad card or connection inside the machine. This is rare, but it could happen. What are you actually doing when you get the KPs? It still could be RAM and just happen to be failing when Airport is in use. Post the logs.

Steve
     
Fresh-Faced Recruit
Join Date: Oct 2005
Status: Offline
Reply With Quote
Dec 6, 2005, 08:25 PM
 
I ran the Apple Hardware test back before I called Apple the first time, and let it loop one day while I was at work--ran some 30+ times, found no errors, so I'm at a loss. Anyhow, panic logs (I don't have any from before the first format/reinstall, but I remember it referring to the com.apple.iokit.AppleAirPort thing):
Sun Nov 13 06:36:55 2005
panic(cpu 0 caller 0x000A8D00): Uncorrectable machine check: pc = 000000002255109C, msr = 0000000000149030, dsisr = 40000000, dar = 0000000017A17040
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 0000000000000000

Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8D00 0x000A7F90 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x2B886780)
PC=0x2255109C; MSR=0x00149030; DAR=0x17A17040; DSISR=0x40000000; LR=0x22550CCC; R1=0x0D72BC70; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x00000000 0x2257CF24 0x2257888C 0x2258CFB0 0x002CE900 0x002CD7C8
0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(402.6)@0x2254e000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x216270 00
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x1d88c000
Exception state (sv=0x1D8C0780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.2.2: Mon Aug 22 18:43:11 PDT 2005; root:xnu-792.5.11.obj~1/RELEASE_PPC

*********

Sat Nov 19 07:34:04 2005
panic(cpu 0 caller 0x000A8D00): Uncorrectable machine check: pc = 00000000006FF52C, msr = 0000000000149030, dsisr = 40000000, dar = 0000000017304040
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 0000000000000000

Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8D00 0x000A7F90 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x2E890A00)
PC=0x006FF52C; MSR=0x00149030; DAR=0x17304040; DSISR=0x40000000; LR=0x00714060; R1=0x0CF73D30; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x01756630 0x00714060 0x002CF960 0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(404.2)@0x6d5000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5a4000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x479000
Exception state (sv=0x20ACB780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC
*********

Sat Nov 19 07:36:44 2005
panic(cpu 0 caller 0x000A8D00): Uncorrectable machine check: pc = 0000000000704B90, msr = 0000000000149030, dsisr = 42000000, dar = 00000000E00F1000
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 00000000fffff1ff

Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8D00 0x000A7F90 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x20ABA780)
PC=0x00704B90; MSR=0x00149030; DAR=0xE00F1000; DSISR=0x42000000; LR=0x00704B88; R1=0x0CEFBC40; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x00704B88 0x006F5080 0x007184DC 0x006FF668 0x00714060 0x002CF960
0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(404.2)@0x6d5000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5a4000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x479000
Exception state (sv=0x25DCF000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC
*********

Mon Nov 21 05:39:08 2005
panic(cpu 0 caller 0x000A8D00): Uncorrectable machine check: pc = 00000000223D152C, msr = 0000000000149030, dsisr = 40000000, dar = 00000000179F7040
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 00000000c03c0000

Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8D00 0x000A7F90 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x23420C80)
PC=0x223D152C; MSR=0x00149030; DAR=0x179F7040; DSISR=0x40000000; LR=0x223E6060; R1=0x0D84BD30; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x02A1F318 0x223E6060 0x002CF960 0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(404.2)@0x223a7000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x215d70 00
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x1d882000
Exception state (sv=0x2766FC80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC

*********

Then I did the zero-out reformat, and it's since done:
Thu Nov 24 18:37:24 2005
panic(cpu 0 caller 0x000A8D00): Uncorrectable machine check: pc = 00000000006FC24C, msr = 0000000000149030, dsisr = 42000000, dar = 0000000001665000
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 0000000000000000

Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8D00 0x000A7F90 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x26779C80)
PC=0x006FC24C; MSR=0x00149030; DAR=0x01665000; DSISR=0x42000000; LR=0x00710FA8; R1=0x0D11BD40; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x0171E964 0x00710FA8 0x002CE900 0x002CD7C8 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(402.6)@0x6d2000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5a2000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x477000
Exception state (sv=0x26781A00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.2.2: Mon Aug 22 18:43:11 PDT 2005; root:xnu-792.5.11.obj~1/RELEASE_PPC

The KPs have occurred while browsing the internet, watching DVDs (though the AP was connected to a wireless network in the background), while trying to perform system updates. Once it did a KP, I rebooted, and immediately after I hit the button for more info on the error, it KP'd again. If it is a RAM issue, that's something I'm fairly certain I could address myself. I'd like Apple to replace the RAM if it's the problem, but if I can't get them to do that, at least I can get to the RAM itself. The Airport is more concerning because I really don't want to risk bending the case, and the local Apple store apparently doesn't do that sort of maintenence on-site.
     
Posting Junkie
Join Date: Oct 2005
Location: Houston, TX
Status: Offline
Reply With Quote
Dec 6, 2005, 09:29 PM
 
How much RAM did you order from Apple? Did you install the Airport update/fix from a week or two ago?

If Apple says there is no problem and you still get kernel panics, talk to your credit card company about a chargeback and file a complaint with the BBB.
     
Fresh-Faced Recruit
Join Date: Oct 2005
Status: Offline
Reply With Quote
Dec 6, 2005, 10:29 PM
 
I got the stock 17" model, so just 512MB RAM. The first two times I did install the Airport update (I believe the second time I did the download through Software Updater, had a panic, so went back and manually downloaded the update from Apple), but didn't bother the third time (This install is just 10.4.2 as it came on the install discs, no updates added.)
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 07:34 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2