Skip to content

Leopard Kernel Panic

I’m really beginning to wonder about Leopard.  In all the time I had Tiger - on both a G4 Powerbook as well as on this Macbook Pro - not a single kernel panic, ever.

Just had my first one this morning on Leopard.  It looks like the Airport driver crashed hard.  Something else that is interesting -  Leopard apparently still uses the Darwin kernel.  I didn’t know that:

Tags: , , ,

5 Comments

  1. i have had several kernal panics on my mbp, too. itunes doesn’t work right. it’s slow and i am not happy with this upgrade if you can call it that. i almost want my money back and to go back to tiger!

    Posted on 01-Feb-08 at 7:13 pm | Permalink
  2. Funny thing is… I still have my G4 Powerbook running Tiger, and occasionally fire it up. Tiger is incredibly stable & Leopard is not, at least not yet.

    Hrmmp.

    Posted on 05-Feb-08 at 3:32 pm | Permalink
  3. jim

    My dual G5 on Leopard is very stable. My MacBook, on the other hand, kernel panics often. Here was the latest today:

    Sat Feb 9 10:06:31 2008
    panic(cpu 0 caller 0×001A7BED): Kernel trap at 0×00193343, type 14=page fault, registers:
    CR0: 0×8001003b, CR2: 0×00000000, CR3: 0×00fdc000, CR4: 0×000006e0
    EAX: 0xffffffff, EBX: 0×00000000, ECX: 0×0436f000, EDX: 0×00000000
    CR2: 0×00000000, EBP: 0×46e53978, ESI: 0×00000000, EDI: 0xffffffbf
    EFL: 0×00010246, EIP: 0×00193343, CS: 0×00000004, DS: 0×001a000c
    Error code: 0×00000000

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0×46e53778 : 0×12b0e1 (0×455670 0×46e537ac 0×133238 0×0)
    0×46e537c8 : 0×1a7bed (0×45ea20 0×193343 0xe 0×45e1d4)
    0×46e538a8 : 0×19e517 (0×46e538c8 0×1000 0×436fd24 0×2)
    0×46e538c0 : 0×193343 (0xe 0×48 0×53000c 0xc)
    0×46e53978 : 0×17cf7f (0×46cc7 0×40 0×0 0×0)
    0×46e539e8 : 0×3959a3 (0×3c9d240 0×0 0×1000 0×1b)
    0×46e53a38 : 0×1cd51d (0×3c9d240 0×0 0×1000 0xb)
    0×46e53b58 : 0×1ce80e (0×1855000 0×0 0×0 0×0)
    0×46e53ce8 : 0×1cf502 (0×5a67c60 0×46e53e9c 0×1855000 0×0)
    0×46e53d18 : 0×3253db (0×5a67c60 0×46e53e9c 0×1855000 0×0)
    0×46e53d98 : 0×1f4056 (0×46e53dcc 0×246 0×46e53df8 0×1d803e)
    0×46e53df8 : 0×1e9a21 (0×5a67c60 0×46e53e9c 0×0 0×4571fe4)
    0×46e53e48 : 0×388855 (0×3f3a380 0×46e53e9c 0×0 0×4571fe4)
    0×46e53ef8 : 0×388959 (0×4571fe4 0×3f3a380 0×916a30 0×0)
    0×46e53f78 : 0×3da847 (0×4555b90 0×4571ee0 0×4571f24 0×0)
    0×46e53fc8 : 0×19ea34 (0×45849e0 0×0 0×1a10b5 0×45849e0)
    Backtrace continues…

    BSD process name corresponding to current thread: Mail

    Mac OS version:
    9B18

    Kernel version:
    Darwin Kernel Version 9.1.0: Wed Oct 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386
    System model name: MacBook1,1 (Mac-F4208CC8)

    Posted on 09-Feb-08 at 8:16 am | Permalink
  4. Hmm, very interesting Jim. Maybe this is isolated to Leopard on Intel…

    Posted on 10-Feb-08 at 4:07 pm | Permalink
  5. djc

    It’s not just Intel - I got several of these this weekend on a Powerbook 1.67Ghz PowerPC running Leopard

    Posted on 31-Mar-08 at 8:16 am | Permalink

Post a Comment

Your email is never published nor shared.