Powerbook crash

Discussion in 'PowerPC Macs' started by Ih8reno, Aug 14, 2015.

  1. Ih8reno macrumors 65816


    Aug 10, 2012
    Hi guys,

    With these new threads on people buying powerbooks I thought I would fire up my 12 inch 1.5ghz 1.25gb ram laptop. It crashed after using a few programs and I recall it doing it last time I had it on as well. Could someone read the crash report and maybe see if they know what could be causing this?

    Interval Since Last Panic Report: 17971 sec
    Panics Since Last Report: 2
    Anonymous UUID: B03620A2-1950-46C4-8638-54A4D7424B09

    Fri Aug 14 20:42:22 2015
    panic(cpu 0 caller 0x000B0504): "Uncorrectable machine check: pc = 0000000000FDA390, msr = 0000000000149030, dsisr = 42000000, dar = 000000000757F000\n" " AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000\n" " L2FIR = 0000000000000000, BusFir = 0000000000000000\n"@/SourceCache/xnu/xnu-1228.15.4/osfmk/ppc/trap.c:975
    Latest stack backtrace for cpu 0:
    0x0009CC88 0x0009D63C 0x00029DA0 0x000B0504 0x000B0784 0x000B4278
    Proceeding back via exception chain:
    Exception state (sv=0x2a854280)
    PC=0x00FDA390; MSR=0x00149030; DAR=0x0757F000; DSISR=0x42000000; LR=0x00F77CE4; R1=0x2A573D10; XCP=0x00000008 (0x200 - Machine check)
    0x02906A40 0x00F77CE4 0x0036011C 0x0003F2A0 0x000B1DD4
    Kernel loadable modules in backtrace (with dependencies):
    dependency: com.apple.iokit.IO80211Family(216.1)@0xf4c000
    dependency: com.apple.iokit.IOPCIFamily(2.6)@0x7b2000
    dependency: com.apple.iokit.IONetworkingFamily(1.6.1)@0xeec000
    Exception state (sv=0x2495ea00)
    PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

    BSD process name corresponding to current thread: kernel_task

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC
    System model name: PowerBook6,8

    System uptime in nanoseconds: 1116931308000
    unloaded kexts:
    com.apple.driver.Apple02DBDMAAudio 2.5.8f1 - last unloaded 2149610376
    loaded kexts:
    com.apple.filesystems.autofs 2.0.2 - last loaded 671008021
    com.apple.iokit.IOBluetoothSerialManager 2.1.9f10
    com.apple.driver.AudioIPCDriver 1.0.6
    com.apple.GeForcePPC 5.4.8
    com.apple.driver.AppleTAS3004Audio 2.5.8f1
    com.apple.driver.InternalModemSupport 2.4.0
    com.apple.driver.MotorolaSM56K 1.3.9
    com.apple.driver.CSRUSBBluetoothHCIController 2.1.9f10
    com.apple.driver.AppleUSBMergeNub 3.5.2
    com.apple.driver.AppleADBButtons 3.0
    com.apple.driver.IOI2CADT746x 1.0.10f1
    com.apple.AppleOnboardDisplay 1.15.1
    com.apple.driver.Portable_PlatformMonitor 1.8.7d5
    com.apple.iokit.IOFireWireIP 1.7.7
    com.apple.driver.AppleVSP 2.2.2
    com.apple.driver.AppleThermal 1.0.1f2
    com.apple.driver.AppleSCCSerial 1.3.2
    com.apple.driver.AppleHWSensor 1.9d0
    com.apple.driver.AppleHWClock 1.5.2d0
    com.apple.driver.AppleTexasAudio 2.5.8f1
    com.apple.driver.AppleTexas2Audio 2.5.8f1
    com.apple.driver.AppleDACAAudio 2.5.8f1
    com.apple.driver.AppleK2Driver 1.7.2f1
    com.apple.driver.AppleI2S 1.0.1f1
    com.apple.nvidia.nv30hal 5.4.8
    com.apple.driver.AppleUSBTrackpad 1.7.4f1
    com.apple.driver.CSRHIDTransitionDriver 2.1.9f10
    com.apple.driver.AppleFileSystemDriver 1.1.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.1.1
    com.apple.iokit.SCSITaskUserClient 2.1.1
    com.apple.driver.AppleADBKeyboard 2.3.9
  2. weckart macrumors 601

    Nov 7, 2004
    Problem lies with your wifi.
  3. Dronecatcher macrumors 68020


    Jun 17, 2014
    Lincolnshire, UK
    You could try moving the Airport kexts out of the extensions folder so it can't activate the hardware - this is what I do with my iBook with the common faulty Airport card problem.
    If this cures it, you can then use a cheap USB wireless bud instead.
  4. Ih8reno, Aug 15, 2015
    Last edited: Aug 15, 2015

    Ih8reno thread starter macrumors 65816


    Aug 10, 2012
    So it's the files themselves and not the hardware?
  5. Dronecatcher macrumors 68020


    Jun 17, 2014
    Lincolnshire, UK
    In my case it's definitely the hardware - the OS can't load the drivers (kexts) so it doesn't 'see' my Airport card and therefore bypasses it. With the kexts in place, the Airport card is activated which quickly leads to kernel panic.
    I'm not saying that's your case but deactivating the hardware will narrow it down.
  6. flyrod macrumors 6502


    Jan 12, 2015
    re-seat the card? Mine has little plastic tabs glued in behind the card, so maybe they had problems like this before.
  7. Ih8reno thread starter macrumors 65816


    Aug 10, 2012
    Have a couple of extra cards so I switched them out and am presently using the powerbook to type this. Hopefully it was just a faulty card because I have the leopard install just the way I like it.

Share This Page