Anyone good with Kernel panics? (airport related)

Discussion in 'macOS' started by Ben Kei, Dec 4, 2006.

  1. Ben Kei macrumors regular

    Joined:
    Oct 30, 2002
    Location:
    London UK
    #1
    Hello, I've had my iBook (12inch last revision) for a year an about 3 weeks (just outside of my apple care - typical huh?) and it's not had a single crash in that time - until yesterday.

    I've had about 10 kernel panics since then and they have all been connected to Airport activity by the looks of it.

    I was talking on Adium (using the AIM network) yesterday, as well as on Skype. Adium crashed, which somehow took Skype with it.
    Both rebooted fine, Adium crashed again so I left it off. After quitting Skype I got a kernel panic - maybe 10 minutes later while checking e-mails.

    I rebooted and got another one.. so I restarted and this time it crashed before it had even reached the login screen, crashed on the gray screen with the Apple logo.

    By the way.. I'm using 10.4.3 (all my apps work fine so I didn't update beyond this)

    This evening I've installed all the Airport updates availible (using the Mac via ethernet to connect to the internet) and then given it a try.. no joy.
    3 full on panics during start up, another 3 during use (one time not even doing anything online, viewing an image..)

    I've repaired permissions and done all the usual maintenance things but I'm still getting a panic within a few minutes when trying to use the Airport.

    anyway,
    I've posted up the report log it gives me when I restart.
    Dunno if this means anything to anyone.. if so I'd be hugely appreciative.
    I really haven't got the time to reinstall now :mad: I'm moving house next weekend and still have to pack..

    Thanks!



    panic(cpu 0 caller 0x000A8D00): Uncorrectable machine check: pc = 000000002767F9D0, msr = 0000000000149030, dsisr = 42000000, dar = 000000003AC0E000
    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=0x2DCA7780)
    PC=0x2767F9D0; MSR=0x00149030; DAR=0x3AC0E000; DSISR=0x42000000; LR=0x2767F8F0; R1=0x174FB490; XCP=0x00000008 (0x200 - Machine check)
    Backtrace:
    0x2767F8F0 0x2767FA6C 0x2767FD1C 0x27699930 0x276B985C 0x276B6F84
    0x276C98E0 0x275CA42C 0x275CA2AC 0x002D0018 0x275CA320 0x275C1240 0x275C1470 0x275C10FC
    0x275CA2AC 0x002D0018 0x275CA320 0x275C0FBC 0x0011DB9C 0x0011AFC8 0x0011B4D8 0x002819D0
    0x00281A84 0x0025ED20 0x0027DBE0 0x002A9BF4 0x000ABE30 0x63435170
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.iokit.AppleAirPort2(404.2)@0x2767a000
    dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x275be000
    dependency: com.apple.iokit.IOPCIFamily(1.7)@0x275ed000
    com.apple.iokit.IONetworkingFamily(1.5.0)@0x275be000
    Exception state (sv=0x2756EC80)
    PC=0x900020AC; MSR=0x0000F030; DAR=0xE008B000; DSISR=0x42000000; LR=0x000EB31C; R1=0xF0080400; XCP=0x00000030 (0xC00 - System call)

    Kernel version:
    Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPCModel: PowerBook6,7, BootROM 4.9.3f0, 1 processors, PowerPC G4 (1.2), 1.33 GHz, 1 GB
    Graphics: ATI Mobility Radeon 9550, ATY,M12, AGP, 32 MB
    Memory Module: DIMM0/BUILT-IN, 512 MB, built-in, built-in
    Memory Module: DIMM1/J7, 512 MB, DDR SDRAM, PC2700U-25330
    AirPort: AirPort Extreme, 404.2 (3.90.34.0.p16)
    Modem: Jump, , V.92, Version 1.0,
    Bluetooth: Version 1.6.6f22, 2 service, 0 devices, 1 incoming serial ports
    Network Service: Built-in Ethernet, Ethernet, en0
    PCI Card: pci106b,4318, sppci_othernetwork, SLOT-B
    Parallel ATA Device: MATSHITACD-RW CW-8124,
    Parallel ATA Device: TOSHIBA MK4025GAS, 37.26 GB
    USB Device: Bluetooth HCI, , Up to 12 Mb/sec, 500 mA
    USB Device: Apple Internal Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
     
  2. Frisco macrumors 68020

    Joined:
    Sep 24, 2002
    Location:
    Utopia
    #2
    I don't think it has anything to do with Airport, because you still get kernel panics when rebooting.

    Remove all peripherals from your computer. Not likely the cause, but it's a good first step to see if they continue.

    Install any new memory lately? Most kernel panics are the result of bad memory.

    Remove this Memory Module: DIMM1/J7, 512 MB, DDR SDRAM, PC2700U-25330. It's the only memory module that you can remove as the other one is built in.

    Let us know your status. Good luck!
     
  3. Catfish_Man macrumors 68030

    Catfish_Man

    Joined:
    Sep 13, 2001
    Location:
    Portland, OR
    #3
    No, it's definitely a crash in the AirPort driver. I got one like this when my card came half-unseated.
     
  4. Ben Kei thread starter macrumors regular

    Joined:
    Oct 30, 2002
    Location:
    London UK
    #4
    Thanks guys.. This is on my iBook and I only tend to plug in any peripherals if I need them at the time, I don't have any that plug in as standard.

    I have narrowed it down to the Airport because it runs perfectly fine connecting via ethernet, I've had to turn the Airport off for it to run fine.
    Plus in the crash report I'm presented with on restart has this section in it:

    Kernel loadable modules in backtrace (with dependencies):
    com.apple.iokit.AppleAirPort2(404.2)@0x2767a000
    dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x275be000
    dependency: com.apple.iokit.IOPCIFamily(1.7)@0x275ed000
    com.apple.iokit.IONetworkingFamily(1.5.0)@0x275be000
    Exception state (sv=0x2756EC80)
    PC=0x900020AC; MSR=0x0000F030; DAR=0xE008B000; DSISR=0x42000000; LR=0x000EB31C; R1=0xF0080400; XCP=0x00000030 (0xC00 - System call)


    Is the Airport card not built in in the iBook? Is it something that can actually come unseated?

    I'll try a reinstall of the OS I think but I'll be SEVERELY miffed if it's a hardware fault less than a month out of warranty. :mad:
     
  5. cblackburn macrumors regular

    Joined:
    Jul 5, 2005
    Location:
    London, UK
    #5
    Hi,

    I had a problem like this with my old Powerbook G4 12". Try to investigate if you can trigger a crash by tapping the underside of the computer with your fist. Not so hard that you risk any further damage but hard enough to see if your Airport card is loose :)

    With mine the airport card was half out and made a dodgy electrical contact. This meant that if I moved it at all then the PCI bus would crash and take down the kernel with it.

    Chris
     
  6. robbieduncan Moderator emeritus

    robbieduncan

    Joined:
    Jul 24, 2002
    Location:
    London
    #6
    It's an actual card in a special slot. It can easily come unseated. You can probably find instructions on how to get to the card as it should be a user serviceable part I think.
     
  7. Ben Kei thread starter macrumors regular

    Joined:
    Oct 30, 2002
    Location:
    London UK
    #7
    Thanks for your reply. I'll have a little search this evening when I get home.

    And thanks cblackburn, I'll give that a try first!
     
  8. robbieduncan Moderator emeritus

    robbieduncan

    Joined:
    Jul 24, 2002
    Location:
    London
    #8
    You can get a guide to fitting the card from Apple here.
     
  9. Angrist macrumors 6502

    Joined:
    Mar 11, 2005
    Location:
    MI or NJ
    #9
    I'd say,
    pull the airport card, and the RAM while you're at it.
    Clean them with a can of air and reconnect.
     
  10. mkrishnan Moderator emeritus

    mkrishnan

    Joined:
    Jan 9, 2004
    Location:
    Grand Rapids, MI, USA
    #10
    I'm also thinking it's most likely poorly seated / contacting hardware. Good luck!
     
  11. Ben Kei thread starter macrumors regular

    Joined:
    Oct 30, 2002
    Location:
    London UK
    #11

    Excellent! HUGELY appreciated.

    Let's hope it's that simple huh?

    Thanks again.

    Ben :D
     

Share This Page