First kernel panic log included

Discussion in 'macOS' started by Saristeguieta, May 15, 2008.

  1. Saristeguieta macrumors newbie

    Joined:
    Apr 25, 2008
    #1
    the kernel panic happened just few minutes ago. I need help to interpret the meaning of the log.

    Thu May 15 14:38:16 2008
    panic(cpu 1 caller 0x001A8C8A): Kernel trap at 0x00132c37, type 14=page fault, registers:
    CR0: 0x80010033, CR2: 0x04ace000, CR3: 0x010d4000, CR4: 0x00002660
    EAX: 0x00000014, EBX: 0x00000014, ECX: 0x00000078, EDX: 0x343ffa80
    CR2: 0x04ace000, EBP: 0x343ffa58, ESI: 0x00000000, EDI: 0x04acdfec
    EFL: 0x00010206, EIP: 0x00132c37, CS: 0x00000008, DS: 0x04c20010
    Error code: 0x00000000

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x343ff778 : 0x12b0f7 (0x4581f4 0x343ff7ac 0x133230 0x0)
    0x343ff7c8 : 0x1a8c8a (0x461720 0x132c37 0xe 0x460ed0)
    0x343ff8a8 : 0x19ece5 (0x343ff8c0 0x246 0x343ffa58 0x132c37)
    0x343ff8b8 : 0x132c37 (0xe 0x48 0x343f0070 0x3e0010)
    0x343ffa58 : 0x389f4e (0xb3a974 0x343ffa88 0x389ebd 0x343ffa80)
    0x343ffa98 : 0xb30762 (0x440cbe2 0x15 0xb3a974 0x14)
    0x343ffb28 : 0x44de29 (0x3e14908 0x3e6db90 0x3e94654 0x55c65f0)
    0x343ffb78 : 0x450d2e (0x493e444 0x3e6db90 0x55c65f0 0x626a640)
    0x343ffbb8 : 0x1dbb6a (0x3e6db90 0x55c65f0 0x626a640 0x343ffe64)
    0x343ffc18 : 0x1eb2f7 (0x55c65f0 0x343ffd50 0x343ffe64 0x343ffe8c)
    0x343ffc78 : 0x1e1b5f (0x343ffd38 0x343ffcec 0x343ffe8c 0x493e444)
    0x343ffd08 : 0x1e21de (0x493e444 0x343ffd38 0x20202 0x343ffe8c)
    0x343fff78 : 0x3dcf13 (0x4697720 0x493e340 0x493e384 0x2c03)
    0x343fffc8 : 0x19f1c3 (0x48b66c0 0x0 0x1a20b5 0x48b66c0)
    No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xbfffec88
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.security.seatbelt(107.1)@0xb2b000->0xb42fff

    BSD process name corresponding to current thread: firefox-bin

    Mac OS version:
    9C7010

    Kernel version:
    Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
    System model name: MacBook4,1 (Mac-F22788A9)


    It never happened before. Any help and advice is most welcomed.

    Simon
     
  2. Eidorian macrumors Penryn

    Eidorian

    Joined:
    Mar 23, 2005
    Location:
    Indianapolis
    #2
    I hope you don't think the panic logs are hard to interpret. They're much easier in Leopard.

    Were you doing something in FireFox?
     
  3. Saristeguieta thread starter macrumors newbie

    Joined:
    Apr 25, 2008
    #3
    just the normal thing: surfing Macrumors and a Canon photography forum.

    I hope t doesn't happen again; very scary.


    Simon
     
  4. antibact1 macrumors 6502

    Joined:
    Jun 1, 2006
    #4
    These two lines:

    Code:
    No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xbfffec88
    make me think Firefox performed a buffer overflow and toasted the stack frame pointer.
     
  5. ElectricSheep macrumors 6502

    ElectricSheep

    Joined:
    Feb 18, 2004
    Location:
    Wilmington, DE
    #5
    Firefox can smash its own stack all that it wants, and the kernel will remain unaffected.

    What is more revealing is if you load a symbol-laden build of the kernel, and proceed through the backtrace. If you do that, what you see is that Firefox made an open() system call, a new vnode was allocated, and then a function which seems to be new to Leopard's kernel was called: mac_vnode_notify_create(). This called a string copy (snprintf) which tripped the page fault. That's bad, and it suggests that there is a bug in the 10.5 kernel.
     
  6. Saristeguieta thread starter macrumors newbie

    Joined:
    Apr 25, 2008
    #6
    Any way to fix that "bug in the 10.5 kernel"?

    thank you all for the help.

    Simon
     
  7. ElectricSheep macrumors 6502

    ElectricSheep

    Joined:
    Feb 18, 2004
    Location:
    Wilmington, DE
    #7
    Not without putting on your caffeine guzzling C hacker hat and chopping away that the kernel source code until the wee hours of the morning looking for the bug.

    Its entirely possible, and plausible, that its an obscure bug that Firefox is tripping and not any other application. I shouldn't be able to make a system call from userland and cause the kernel to go down in flames.
     

Share This Page