first kernal panic

Discussion in 'Mac Basics and Help' started by JosephEsquivel, May 11, 2008.

  1. JosephEsquivel macrumors regular

    Joined:
    May 30, 2007
    #1
    anyone make any sense of this?


    Sun May 11 21:18:55 2008
    panic(cpu 1 caller 0x001A8C8A): Kernel trap at 0x00132c37, type 14=page fault, registers:
    CR0: 0x80010033, CR2: 0x05336000, CR3: 0x01057000, CR4: 0x00000660
    EAX: 0x00000014, EBX: 0x00000014, ECX: 0x00000078, EDX: 0x21067a80
    CR2: 0x05336000, EBP: 0x21067a58, ESI: 0x00000000, EDI: 0x05335fec
    EFL: 0x00010206, EIP: 0x00132c37, CS: 0x00000008, DS: 0x029c0010
    Error code: 0x00000000

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x21067778 : 0x12b0f7 (0x4581f4 0x210677ac 0x133230 0x0)
    0x210677c8 : 0x1a8c8a (0x461720 0x132c37 0xe 0x460ed0)
    0x210678a8 : 0x19ece5 (0x210678c0 0x246 0x21067a58 0x132c37)
    0x210678b8 : 0x132c37 (0xe 0x48 0x21060070 0x3e0010)
    0x21067a58 : 0x389f4e (0xb29974 0x21067a88 0x389ebd 0x21067a80)
    0x21067a98 : 0xb1f762 (0x2f8f762 0x15 0xb29974 0x14)
    0x21067b28 : 0x44de29 (0x44476e8 0x2b25b90 0x2b5069c 0x3c9a8c0)
    0x21067b78 : 0x450d2e (0x3a4f104 0x2b25b90 0x3c9a8c0 0x5119130)
    0x21067bb8 : 0x1dbb6a (0x2b25b90 0x3c9a8c0 0x5119130 0x21067e64)
    0x21067c18 : 0x1eb2f7 (0x3c9a8c0 0x21067d50 0x21067e64 0x21067e8c)
    0x21067c78 : 0x1e1b5f (0x21067d38 0x21067cec 0x21067e8c 0x3a4f104)
    0x21067d08 : 0x1e21de (0x3a4f104 0x21067d38 0xa00 0x21067e8c)
    0x21067f78 : 0x3dcf13 (0x33499d0 0x3a4f000 0x3a4f044 0x13d203)
    0x21067fc8 : 0x19f1c3 (0x426b880 0x0 0x10 0x426b880)
    No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xbfffd6b8
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.security.seatbelt(107.1)@0xb1a000->0xb30fff

    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: MacBook3,1 (Mac-F22788C8)
     
  2. IJ Reilly macrumors P6

    IJ Reilly

    Joined:
    Jul 16, 2002
    Location:
    Palookaville
    #2
    If it's a one-time event, don't worry about it, unless you've upgraded your RAM recently.
     
  3. matt90 macrumors member

    Joined:
    Feb 18, 2008
    Location:
    Los Alamos, New Mexico (Atomic City)
    #3
    Kernel panics are generally caused by hardware problems and, yes, usually happen only once. If it keeps happening, reinstall the OS.
     
  4. IJ Reilly macrumors P6

    IJ Reilly

    Joined:
    Jul 16, 2002
    Location:
    Palookaville
    #4
    This is wonderfully obtuse advice. Reinstall the OS to fix a hardware problem?

    Yes, most kernel panics are hardware issues, so no, do not reinstall OSX to fix a hardware issue.
     
  5. ElectricSheep macrumors 6502

    ElectricSheep

    Joined:
    Feb 18, 2004
    Location:
    Wilmington, DE
    #5
    The panic occurred inside some Virtual Filesystem code (the kernel was responding to an open() system call; and it looks like it was creating a new file).

    I would run Disk Utility from the Mac OS X install disk to verify and repair your disks.
     

Share This Page