read this Kernal Panic Log?

Discussion in 'Mac Basics and Help' started by Consultant, Jul 13, 2010.

  1. Consultant macrumors G5

    Consultant

    Joined:
    Jun 27, 2007
    #1
    The trusty PowerMac G4 DP 800 has been crashing a lot lately.
    Not sure what's going on, but here are the Panic logs... Any thoughts?

    PPC, 10.4.11

    Code:
    Sat Jul 10 23:56:13 2010
    
    
    Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000000000054 PC=0x0000000000859714
    Latest crash info for cpu 1:
       Exception state (sv=0x49D0B280)
          PC=0x00859714; MSR=0x00009030; DAR=0x00000054; DSISR=0x40000000; LR=0x0085966C; R1=0x21F4BB50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0085966C 0x0086090C 0x00861F5C 0x00855A84 0x00864E98 0x00864D88 
             0x008493C8 0x0086DD08 0x0003CA1C 0x000A9714 
          Kernel loadable modules in backtrace (with dependencies):
             com.apple.iokit.AppleAirPort2(405.1)@0x82a000
                dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5a3000
                dependency: com.apple.iokit.IOPCIFamily(1.7)@0x491000
    Proceeding back via exception chain:
       Exception state (sv=0x49D0B280)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x00C2BA00)
          PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
    panic(cpu 1 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 1:
          Backtrace:
             0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80 
    Proceeding back via exception chain:
       Exception state (sv=0x49D0B280)
          PC=0x00859714; MSR=0x00009030; DAR=0x00000054; DSISR=0x40000000; LR=0x0085966C; R1=0x21F4BB50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0085966C 0x0086090C 0x00861F5C 0x00855A84 0x00864E98 0x00864D88 
             0x008493C8 0x0086DD08 0x0003CA1C 0x000A9714 
          Kernel loadable modules in backtrace (with dependencies):
             com.apple.iokit.AppleAirPort2(405.1)@0x82a000
                dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5a3000
                dependency: com.apple.iokit.IOPCIFamily(1.7)@0x491000
       Exception state (sv=0x00C2BA00)
          PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
    
    *********
    Code:
    Tue Jul 13 21:55:03 2010
    
    
    Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000000000030 PC=0x0000000000859714
    Latest crash info for cpu 1:
       Exception state (sv=0x37C65000)
          PC=0x00859714; MSR=0x00009030; DAR=0x00000030; DSISR=0x40000000; LR=0x0085966C; R1=0x21EE3B50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0085966C 0x0086090C 0x00861F5C 0x00855A84 0x00864E98 0x00864D88 
             0x008493C8 0x0086DD08 0x0003CA1C 0x000A9714 
          Kernel loadable modules in backtrace (with dependencies):
             com.apple.iokit.AppleAirPort2(405.1)@0x82a000
                dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5a3000
                dependency: com.apple.iokit.IOPCIFamily(1.7)@0x491000
    Proceeding back via exception chain:
       Exception state (sv=0x37C65000)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x379A8A00)
          PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
    panic(cpu 1 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 1:
          Backtrace:
             0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80 
    Proceeding back via exception chain:
       Exception state (sv=0x37C65000)
          PC=0x00859714; MSR=0x00009030; DAR=0x00000030; DSISR=0x40000000; LR=0x0085966C; R1=0x21EE3B50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0085966C 0x0086090C 0x00861F5C 0x00855A84 0x00864E98 0x00864D88 
             0x008493C8 0x0086DD08 0x0003CA1C 0x000A9714 
          Kernel loadable modules in backtrace (with dependencies):
             com.apple.iokit.AppleAirPort2(405.1)@0x82a000
                dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5a3000
                dependency: com.apple.iokit.IOPCIFamily(1.7)@0x491000
       Exception state (sv=0x379A8A00)
          PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
    
    *********
     
  2. Scottapotmas macrumors newbie

    Joined:
    Jul 13, 2010
    #2
    im not absolutely certain, but its to do with a crash in the airport kexts or plists...

    Kernel loadable modules in backtrace (with dependencies):
    com.apple.iokit.AppleAirPort2(405.1)@0x82a000
    dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5a3000
    dependency: com.apple.iokit.IOPCIFamily(1.7)@0x491000

    is a givaway, com.apple.iokit..AppleAirPort2 is the problem and the following means that IONetworking family and IOPCIFamily require or call to it...

    So the Airport2 driver is missing something or something and then the networking and PCI stuff won't work...


    I guess you could try backing it up and removing it, or updating... but its PPC, so im not quite sure if there would be a newer one... I guess i diagnosed, but don't know how to help
     
  3. Consultant thread starter macrumors G5

    Consultant

    Joined:
    Jun 27, 2007
    #3
    Thanks Scott, I thought that was the problem. Maybe it's corrupted.

    Already had Airport turned off. Guess I have to reinstall / re-update.
     

Share This Page