Panic! At the MacBook Pro!

Posted by joy


(There’s a musical reference in that title…)

Since I’ve been writing about Apple products so much, I might as well give you the not so hot news. Or in this case let you know that I don’t allow MacBook Pros on my couch as they get *hot*.

While a few of my readers are happy MacBook Pro owners, one particular MacBook Pro I know of has been experiencing kernel panics at the rate of one or two a day. At first the thought was that perhaps running Parallels with Windows XP was causing the kernel panics, but then they started occurring when the MacBook Pro was in normal use… which is worrying at best.

Anyway, the MacBook Pro kernel panic log messages seem to reference the APIC controller and in my A+ Certified experience seems to mean that there’s something hardware related.

Has anyone else seen anything similar?

Update: There’s a log of the most recent panic contained in the full post.

Update 2 06/07/2006: At this time, it seems like the panics were caused by bad third party RAM.


Fri Jun 2 18:31:58 2006

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0×107e6c : 0×1343b7 (0×3583a30 0×360fb80 0×107e9c 0×3583a30)
0×107ecc : 0×134cc6 (0×3583a30 0×2 0×107f0c 0×4a2720)
0×107eec : 0×13fa02 (0×3583a30 0×0 0×107f1c 0×2)
0×107f2c : 0×38c7e0 (0×4a2720 0×389d3dc 0×0 0×3557620)
0×107f4c : 0×6ab5b2 (0×389d3c0 0×0 0×35c6080 0×0)
0×107f7c : 0×6ab673 (0×355e800 0×0 0×354e000 0×51)
0×107f9c : 0×61dc01 (0×355e800 0×0 0×354e000 0×51)
0×107fbc : 0×3ac62e (0×355cc00 0×0 0×355cb00 0×51)
0×107fec : 0×197c3e (0×51 0×24d6be98 0×24d6be98 0×2000007f)
0×24d6bf44 : 0×199021 (0×0 0×0 0xbffff158 0×216)

Backtrace continues…
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleAPIC(1.1.0)@0×6aa000
com.apple.driver.AppleACPIPlatform(1.0.3)@0×61c000
dependency: com.apple.iokit.IOPCIFamily(2.0)@0×565000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0×618000

Kernel version:
Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386
panic(cpu 0 caller 0×0019C437): Panic double fault (CPU:0, code:0×8, trace_trap:0×0),registers:
CR0: 0×8001003b, CR2: 0×0010f344, CR3: 0×00d5c000, CR4: 0×000006e0
EAX: 0×00000000, EBX: 0×00000003, ECX: 0×00000003, EDX: 0×00000000
ESP: 0×0010f348, EBP: 0×00107e6c, ESI: 0×03583a30, EDI: 0×00000000
EFL: 0×00010046, EIP: 0×03583b5c
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0×425efc : 0×128b5e (0×3bbeb8 0×425f20 0×131bbc 0×0)
0×425f3c : 0×19c437 (0×3c1194 0×0 0×8 0×0)
0×425fec : 0×1983fb (0×8 0×0 0×0 0xd62000) Backtrace terminated-invalid frame pointer 0×0

Kernel version:
Darwin Kernel Version 8.6.1: Tue Mar 7 16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386


4 Responses to “Panic! At the MacBook Pro!”

  1. me Says:

    Aren’t there horror stories around the net about MacBooks going down in flames, and / or randomly kernel panicking?

  2. bert Says:

    meh…it gets pretty hot while capturing video, but it’s not like I’m expecting spontaneous combustion. No kernel panics either, but I haven’t used Parallels myself though…boot camp is sufficient for when I need Windows.

  3. mike Says:

    After doing the Apple Hardware Test and running four iterations of memtest in single user mode, all of which came back clear, I reseated my 2×1GB DIMMS Friday evening and (knock on wood) haven’t had a panic!! since.

  4. Javier Says:

    Mike,

    It seems it’s a problem related to the airport extreme network card. More information at http://www.macfixit.com/article.php?story=2006060711410842

Leave a Reply