Welcome to the MacNN Forums.

Buck_W · Dec 23, 2007, 01:07 PM

I just installed 10.5 on my daughter's iBook (G4/1.33 GHZ/1 GB Ram). She used it for about two days and all of a sudden she keeps getting a kernel panic that requires a restart. Here's the info that came up that we sent to Apple:

Sun Dec 23 13:39:47 2007
panic(cpu 0 caller 0x000AE584): "Uncorrectable machine check: pc = 000000002E4EE890, msr = 0000000000149030, dsisr = 42000000, dar = 0000000025615000\n" " AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000\n" " L2FIR = 0000000000000000, BusFir = 0000000000000000\n"@/SourceCache/xnu/xnu-1228.0.2/osfmk/ppc/trap.c:975
Latest stack backtrace for cpu 0:
Backtrace:
0x0009AD18 0x0009B6BC 0x00029DC4 0x000AE584 0x000AE804 0x000B22F8
Proceeding back via exception chain:
Exception state (sv=0x2474e500)
PC=0x2E4EE890; MSR=0x00149030; DAR=0x25615000; DSISR=0x42000000; LR=0x2E45F188; R1=0x1E79FD00; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x0046A140 0x2E45F188 0x00358D94 0x0003F8D8 0x000AFE54
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortBrcm43xx(305.25.82)@0x2e45 7000->0x2e583fff
dependency: com.apple.iokit.IO80211Family(200.7)@0x24909000
dependency: com.apple.iokit.IOPCIFamily(2.4)@0x1e65c000
dependency: com.apple.iokit.IONetworkingFamily(1.6.0)@0x248580 00
Exception state (sv=0x1e6bd780)
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:
9B18

Kernel version:
Darwin Kernel Version 9.1.0: Wed Oct 31 17:48:21 PDT 2007; root:xnu-1228.0.2~1/RELEASE_PPC
--------------------
Does anybody have a suggestion as to what the problem might be? I was able to boot into safe mode earlier today and repair all the permissions. But as soon as we restarted it, it crashed again with the above error message. Any suggestions as to how I should isolate the problem?

Thanks!

Big Mac · 01:24 PM

As you can see, it is the Airport card. Try re-seating it.

Art Vandelay · Dec 23, 2007, 01:14 PM

It's AirPort related. You can try reseating the AirPort card if it's user accessible on that model of iBook. You can also try resetting your AirPort prefs.

Cold Warrior · Dec 23, 2007, 01:24 PM

Good tips. Also consider an archive-install if the panics persist.

Buck_W · Dec 23, 2007, 01:56 PM

Originally Posted by Big Mac

As you can see, it is the Airport card. Try re-seating it.

I had checked on that and ran across a couple of documents that seemed to indicate that the Airport card is "built-in" and inaccessible in this particular iBook. Does anybody know for sure? Also, how do I reset the Airport prefs?

Thanks for the responses

Big Mac · Dec 23, 2007, 02:45 PM

Oh yeah, you're probably right. What kind of install of Leopard did you do?

Buck_W · Dec 23, 2007, 04:41 PM

Originally Posted by Big Mac

Oh yeah, you're probably right. What kind of install of Leopard did you do?

Wiped everything squeaky clean and installed a fresh copy.

Big Mac · Dec 23, 2007, 04:55 PM

That's strange then. Third party RAM perhaps?

Buck_W · Dec 24, 2007, 01:41 PM

Well, it appears that this is a pretty serious problem:

Apple - Support - Discussions - Airport kernel panic last revision ibook ...

IBook G4 1.33GHz - Appledefects

Bummer! I wonder what it takes for Apple to acknowledge that this appears to be faulty engineering on their part, and they need to take care of it?

@pplejaxkz · Dec 24, 2007, 05:20 PM

Is there any other action that you could take rather than just reporting it to Apple? I mean I was getting kernel panics regularly, but it wasn't always frequent.(It was very frequent when I would leave Azereus running all night) Should I take it to the Apple store? Is there really anything they can do? But on the other hand I don't want to part from my MacBook for very long.

I haven't been getting them as often as I was earlier, but I still think it's a problem. I do a lot of important projects for school on my MacBook and the possibility of losing some of it kinda sucks. Sorry to sort of hijack the thread. Thanks in advanced!

Buck_W · 05:37 PM

My comment about Apple acknowledging their responsibility is based on all the threads/posts about this specific hardware issue. It appears that quite a few iBook owners are experiencing the same problem. One thread was even sharing information regarding a possible class action suit. I have no idea how many computers have to run into problems before a case like that can be made, but from all the reading I've done about this over the past couple of days, the numbers seem to be fairly high and growing.

Chongo · Dec 24, 2007, 05:33 PM

Meet Colonel Panic

Buck_W · Dec 27, 2007, 08:13 AM

I've been looking at some Apple compatible adapters as a temporary fix. Anybody got an opinion on this one:

MA-WL-USB | Wireless-G USB Network Adapter Mac OS X 10.3.x and up | PowerMax