View Full Version : Regular kernel panics

23rd January 2010, 06:11 AM
Hi guys,

I'm having an issue with my C2D blackbook that seems to be getting worse over time. Probably the first symptom, assuming they're related, is that flash video performance started to get really bad. I'm not talking about the high CPU usage, fans going nuts but video still playing smoothly that seems common across all Macs due to the fact Flash is a complete dog - but flash video would start skipping, the audio would degrade (sometimes switching the sound output to headphones then back to speakers would fix this, no idea why) and often beachballs. It's at the point where watching something in streaming video, or even just YouTube clips, is unbearable - I have installed Click2Flash, so that helps with YouTube, but even though Flash is bad I don't think it's meant to be THIS bad.

So I tried a clean install, thinking that maybe, in the upgrade from Leopard to Snow Leopard, that Flash somehow got a bit f'ed up. Even with a completely clean system, with nothing restored at all from backups, it didn't take long for the issue to reappear. It's particularly noticeable when streaming live video, such as live.twit.tv or Cnet's live streams.

I've also tried upgrading to the new beta version of Flash but that hasn't seemed to have fixed the problem.

Now, when I leave my computer on and walk away from it, I often comeback to find a Kernel Panic. It's happened 3-4 times in the past week or so, and is starting to really worry me. The computer is still under Applecare, but I'm starting to thing something may be up in the hardware.

Here's an example of some of the panics (think I've pasted the important bits, let me know if not):

Interval Since Last Panic Report: 2195137 sec
Panics Since Last Report: 3
Anonymous UUID: 9987151A-9133-4386-A308-FF4332C957B6

Fri Jan 22 19:56:50 2010
Panic(CPU 0): Unresponsive processor
EAX: 0x2034836f, EBX: 0x05b23b7c, ECX: 0x05b23b7c, EDX: 0x05b23b98
CR2: 0x005cd000, EBP: 0x0010be38, ESI: 0x05b23b98, EDI: 0x0084b7e0
EFL: 0x00000002, EIP: 0x002962db, CS: 0x00000008, DS: 0x055b0010
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x10bce8 : 0x2ae558 (0x10bd80 0x1 0x10bd18 0xef5bb078)
0x10bd18 : 0x2a7043 (0x2 0x10bd80 0x64 0x0)
0x10bd68 : 0x29dc8a (0x10bd80 0x51dfb7c 0x4c4b400 0x1)
0x10be38 : 0x223cf8 (0x5b23b98 0x5b23b7c 0x1db177b7 0x6a01)
0x10be78 : 0x231049 (0x84b7e0 0x5b23b7c 0x0 0x0)
0x10bec8 : 0x29583e (0x81e04c 0x680a47ac 0x6a01 0x547d9d)
0x10bf18 : 0x2a661c (0x0 0x97a42c 0x0 0x2afb7f)
0x10bf58 : 0x2ae599 (0x3596bc80 0x561d3a4 0x10bf88 0x574adb)
0x10bf88 : 0x2a7043 (0xde 0x3596bc80 0x306 0x1)
0x10bfd8 : 0x29db1e (0x3596bc80 0x0 0x0 0x29e93b)
0x3596bd48 : 0x9741a8 (0x53dac00 0x0 0x53dac00 0x0)
0x3596bd88 : 0x97c1d1 (0x53dac00 0x3596be6c 0x296a59 0x0)
0x3596bde8 : 0x973de8 (0x53dac00 0x3596be6c 0x312 0x94ba00)
0x3596be38 : 0x97a4ff (0x53dac00 0x3596be6c 0x3596be98 0x10)
0x3596be98 : 0x951807 (0x53dac00 0x59a6960 0x1 0x3596bed0)
0x3596bf08 : 0x5491b5 (0x5970e00 0x59a5dc0 0x1 0x0)
Backtrace continues...
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.ACPI_SMC_PlatformPlugin(4.0.1d0)@ 0x979000->0x987fff
dependency: com.apple.iokit.IOACPIFamily(1.3.0)@0x949000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x95d000
dependency: com.apple.driver.IOPlatformPluginFamily(4.0.1d0)@0 x96e000
dependency: com.apple.driver.AppleSMC(3.0.1d2)@0x94d000
dependency: com.apple.iokit.IOACPIFamily(1.3.0)@0x949000
com.apple.driver.IOPlatformPluginFamily(4.0.1d0)@0 x96e000->0x978fff

BSD process name corresponding to current thread: kernel_task


Interval Since Last Panic Report: 2021324 sec
Panics Since Last Report: 1
Anonymous UUID: 9987151A-9133-4386-A308-FF4332C957B6

Tue Jan 19 22:42:33 2010
panic(cpu 1 caller 0x28d2b4): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x67e4488 cpus_to_respond=0x1"@/SourceCache/xnu/xnu-1486.2.11/osfmk/i386/pmap.c:5019
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x2fdaba58 : 0x21b2bd (0x5cf868 0x2fdaba8c 0x223719 0x0)
0x2fdabaa8 : 0x28d2b4 (0x58dd98 0x67e4488 0x1 0xa)
0x2fdabb18 : 0x28ed7c (0x67e4488 0x15b6e000 0x1 0x29c50a)
0x2fdabb88 : 0x26bc3f (0x2f823 0x60 0x0 0x200c470)
0x2fdabd38 : 0x25bf56 (0x6b77250 0x0 0x0 0x8000)
0x2fdabe18 : 0x242bd2 (0x67df520 0x15b5f000 0x1 0x20000)
0x2fdabe58 : 0x21d65f (0x5f81d88 0x5271f98 0x10ec78 0xa07)
0x2fdabe98 : 0x2107f7 (0x5f81d00 0x0 0x6d83380 0x91b7e00)
0x2fdabef8 : 0x216a5a (0x5f81d00 0x0 0x0 0x0)
0x2fdabf78 : 0x292834 (0x8ea3688 0x0 0x0 0x0)
0x2fdabfc8 : 0x29e44d (0x8ea3684 0x7fff 0x10 0x8ea3684)

BSD process name corresponding to current thread: ScreenSaverEngin


Interval Since Last Panic Report: 2108673 sec
Panics Since Last Report: 2
Anonymous UUID: 9987151A-9133-4386-A308-FF4332C957B6

Thu Jan 21 09:57:48 2010
panic(cpu 0 caller 0x28d2b4): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x84b6e0 cpus_to_respond=0x2"@/SourceCache/xnu/xnu-1486.2.11/osfmk/i386/pmap.c:5019
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x2f7722f8 : 0x21b2bd (0x5cf868 0x2f77232c 0x223719 0x0)
0x2f772348 : 0x28d2b4 (0x58dd98 0x84b6e0 0x2 0x2905c0)
0x2f7723b8 : 0x28ed7c (0x84b6e0 0x4a25c000 0x0 0x84b724)
0x2f772428 : 0x28ee01 (0x3fb49 0x20 0x2f772468 0x20000)
0x2f772448 : 0x254438 (0x3fb49 0x20000 0x0 0x7)
0x2f7724d8 : 0x257b96 (0x0 0x84b6e0 0x4a2dc000 0x0)
0x2f772618 : 0x2a781f (0x68b08f8 0x4a2dc000 0x0 0x1)
0x2f7726f8 : 0x29d968 (0x2f772710 0x0 0x2f772878 0xdcecd5)
0x2f772708 : 0xdcecd5 (0xe 0x5af0048 0x2f770010 0x4f0010)
0x2f772878 : 0xdb3057 (0x249f5000 0x7066500 0x3f0 0xc)
0x2f7728b8 : 0xdcd04f (0x249f5000 0x7066500 0x2f772908 0


Any ideas what's going on or what course of action I should take to determine if there's any hardware issues? Thanks.

23rd January 2010, 10:49 AM
If you've paid for Applecare, why not use your warranty and ask the experts? Can't you email the above to a help desk or something? Whether its hardware or software related, you should be able to get some professional help rather than stressing and worrying, and possibly getting conflicting advice from (the admittedly normally 100% spot-on) mactalkers.

23rd January 2010, 12:10 PM
Good point, just didn't want to go to the trouble of trekking into the apple store if there was an easy solution I was missing.

Fair enough though, will shoot off an email or give Apple a call.