iMac G5 panicking, internal modem fault?

Discussion in 'PowerPC Macs' started by apfhex, Aug 18, 2006.

  1. apfhex macrumors 68030

    apfhex

    Joined:
    Aug 8, 2006
    Location:
    Northern California
    #1
    I thought this might go in here rather than Peripherals since it's relating to internal hardware.

    My mom's 2005 iMac G5 has been panicking when checking email (Mail 2.x, up-to-date install of Tiger). I got her to send me the contents of her panic log and quickly found this:
    Code:
    Kernel version:
    Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x00095718 0x00095C30 0x0002683C 0x000A8404 0x000ABD80
    Proceeding back via exception chain:
       Exception state (sv=0x29AC6C80)
          PC=0x00C64AB4; MSR=0x0000B030; DAR=0x42BA54DC; DSISR=0x40000000; LR=0x00C65558; R1=0x12563840; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x00C65558 0x00C65ECC 0x00C668F8 0x00C60C84 0x00B7CC34 0x00B72644
             0x00B4DB74 0x00B4D9F0 0x00B5481C 0x002D3544 0x0003C744 0x000A9914
          Kernel loadable modules in backtrace (with dependencies):
             com.apple.driver.MotorolaSM56K(1.3.3)@0xaf9000
                dependency: com.apple.iokit.IOSerialFamily(9.0.0d30)@0x4ba000
                dependency: com.apple.driver.AppleI2SModemFamily(1.1.4)@0x8fe000
       Exception state (sv=0x22687C80)
          PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    It's obvious what tipped me off that it was modem trouble. Every entry in the log was exactly the same too (com.apple.driver.MotorolaSM56K, etc.). So I'm wondering, anyone else with panics related to dialup internet access, any solutions? Could it be caused by a flakey connection?
     
  2. shudson2 macrumors newbie

    Joined:
    Feb 27, 2008
    #2
    I'm having the same problem. After a boot or reboot, the first connection attempt to the internet does not work. It either connects for about a minute without being able to transfer data and then disconnects itself, or I get a kernel panic:
    Code:
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000027AF99C4 PC=0x000000003BC584D8
    Latest crash info for cpu 0:
       Exception state (sv=0x3D1FF500)
          PC=0x3BC584D8; MSR=0x0000B030; DAR=0x27AF99C4; DSISR=0x40000000; LR=0x3BC58F74; R1=0x228337B0; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x3BC58FBC 0x3BC59134 0x3BC5986C 0x3BC5A908 0x3BC541E8 0x3BB8D488 
             0x3BB82698 0x3BBC4EB4 0x3BB5F850 0x3BB5F6C0 0x3BB65DBC 0x002D43D0 0x0003CA1C 0x000A9714 
          Kernel loadable modules in backtrace (with dependencies):
             com.apple.driver.MotorolaSM56K(1.3.9)@0x3bb0b000
                dependency: com.apple.iokit.IOSerialFamily(9.0.0d30)@0x3ba90000
                dependency: com.apple.driver.AppleI2SModemFamily(1.1.4)@0x3b970000
    Proceeding back via exception chain:
       Exception state (sv=0x3D1FF500)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x3ADA1000)
          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 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80 
    Proceeding back via exception chain:
       Exception state (sv=0x3D1FF500)
          PC=0x3BC584D8; MSR=0x0000B030; DAR=0x27AF99C4; DSISR=0x40000000; LR=0x3BC58F74; R1=0x228337B0; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x3BC58FBC 0x3BC59134 0x3BC5986C 0x3BC5A908 0x3BC541E8 0x3BB8D488 
             0x3BB82698 0x3BBC4EB4 0x3BB5F850 0x3BB5F6C0 0x3BB65DBC 0x002D43D0 0x0003CA1C 0x000A9714 
          Kernel loadable modules in backtrace (with dependencies):
             com.apple.driver.MotorolaSM56K(1.3.9)@0x3bb0b000
                dependency: com.apple.iokit.IOSerialFamily(9.0.0d30)@0x3ba90000
                dependency: com.apple.driver.AppleI2SModemFamily(1.1.4)@0x3b970000
       Exception state (sv=0x3ADA1000)
          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
    Does anyone have any suggestions for fixing this?

    Thanks,

    Steve
     
  3. ianimate3d macrumors member

    Joined:
    Dec 30, 2002
    Location:
    USA
    #3
    Not to thread crap, but you should probably pose this question in the proper forum for iMac related issues. This is the place for Power Mac and Mac Pro related discussions.
     
  4. Firefly2002 macrumors 65816

    Joined:
    Jan 9, 2008
    #4
    Whoa. A G5 on dial-up. That's like running a Porsche on vegetable oil. Hm.
     
  5. apfhex thread starter macrumors 68030

    apfhex

    Joined:
    Aug 8, 2006
    Location:
    Northern California
    #5
    Sheesh! It's not my fault the forums got reorganized after I made this post two years ago. :rolleyes: That said, if a mod wants to move it, that would be nice.

    Anyway, I don't she's had any KPs in a while, now running 10.4.11.
     
  6. Lynneandrob macrumors newbie

    Joined:
    Mar 9, 2008
    #6
    NewImac jams up while connecting to dial up

     
  7. shudson2 macrumors newbie

    Joined:
    Feb 27, 2008
    #7
    I called Apple support and they got me to try many things (delete network settings folder, reinstall OS X, etc.) and nothing helped. By then there was no doubt that it was a hardware problem. This wasted a lot of time and I probably wouldn't bother to call them in the future if I was fairly certain the issue was with the hardware.

    I took my iMac to my local authorized repair centre and they replaced the logic board, the power supply, and the modem. Thankfully my APP hadn't expired! The power supply would have been covered by a repair extension program, the modem was cheap, but the logic board was very expensive. The service was very fast: in Monday morning, out Tuesday afternoon.

    It works like new now.
     

Share This Page