Results 1 to 8 of 8

Thread: Kernel panic info please...

  1. #1
    Join Date
    Feb 2012

    Default Kernel panic info please...

    I've just been emailed this report by a client after his 24" iMac shut down overnight.
    I'm no expert in reading this type of report, but it appears that it junked the msdos kext.
    Anyone care to have a stab at this? There are no 3rd party extensions in there so the field is fairly narrow.
    This may be a one-off or it may be heralding worse things to come. I have asked if there was a FAT32 external drive attached at the time but don't have an answer yet. It doesn't look like he had any version of Windoze running as there are no kexts for vmware or Parallels present.


    Interval Since Last Panic Report: 3714314 sec
    Panics Since Last Report: 1
    Anonymous UUID: B25A8E32-E6FF-4F63-8585-AA7E86071A4E

    Fri Mar 16 09:21:12 2012
    panic(cpu 1 caller 0x27adef): "vm_page_reactivate_local: count = 250, vm_page_local_count = 251\n"@/SourceCache/xnu/xnu-1504.15.3/osfmk/vm/vm_resident.c:3192
    Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
    0x795fb8d8 : 0x21b837 (0x5dd7fc 0x795fb90c 0x223ce1 0x0)
    0x795fb928 : 0x27adef (0x59812c 0xfa 0xfb 0x2aac45)
    0x795fb968 : 0x255ada (0x1 0x0 0x0 0x1bfaec)
    0x795fb9d8 : 0x2589af (0x81f7148 0xaab1414 0xa8000 0x1)
    0x795fbb28 : 0x2abcc7 (0xb447668 0xa8000 0x1 0x3)
    0x795fbc08 : 0x2a1a78 (0x795fbc20 0x0 0x795fbd38 0x2a2764)
    0x795fbc18 : 0x2a2764 (0xe 0x10048 0x10 0x70)
    0x795fbd38 : 0x266db0 (0xfab2034 0x4c0 0x0 0x0)
    0x795fbda8 : 0x266ffc (0x0 0xb68d7a8 0x795fbe38 0x227182)
    0x795fbe78 : 0x20e4a4 (0xb447668 0x795fbea8 0xfab2000 0xaf4b354)
    0x795fbec8 : 0x20eb26 (0x17e704a0 0x17e704b0 0x1 0xb447668)
    0x795fbf28 : 0x20f1b5 (0x17e70400 0xaa5b9e0 0xb447668 0x0)
    0x795fbf48 : 0x216dc2 (0x17e70400 0xaa5b9e0 0xb447668 0x0)
    0x795fbfa8 : 0x21711c (0x0 0x1 0x795fbfc8 0xb2fb124)
    0x795fbfc8 : 0x2a179c (0x0 0x0 0x10 0xb2fb124)

    BSD process name corresponding to current thread: ntpd

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
    System model name: iMac8,1 (Mac-F227BEC8)

    System uptime in nanoseconds: 135345706340261
    unloaded kexts: 1.6.3 (addr 0x12f9000, size 0x53248) - last unloaded 34016629278110
    loaded kexts: 1.8.3 - last loaded 33730214930034 2.1.0 1.9.3d0 3.5.7 1.0.20 6.3.6 2.0.5f14 6.3.6 1.5.1 1.57 4.7.0a1 17 170.0.46 7.0.0 1.1.6 303.8 2.6.8 31.1 eZlib 1.0.0d1 1.6.4 4.2.4 3.2.1b1 428.42.4 1.4.0 2.1.7 2.5.1 4.2.4 1.3.1 4.7.3 4.2.0 1.5 1.3.6 1.7 1.3.6 1.4 t 142.6.0 1 0 2.1.14 142.6.0 141.5 2.4.5f3 141.5 17 2.0.5f14 6.3.6 6.3.6 10 14 10 10 20 4.7.0a1 2.0.3 1.0.1 2.2.1 74.2 2.4.5f3 10.0.3 3.1.0d5 1.8.3fc2 1.3 41 2.0.5f14 2.2.1 2.0.5f14 2.6.8 2.4.5f3 2.4.5f3 2.4.5f3 162 4.2.0 162 2.6.7 4.2.4 3.9.0 2.6.8 1.6 1.6 1.6.1 402.1 2.5.1 2.6.8 4.2.4 320.1 1.10 2.0.6 2.5.1 4.2.6 1.4.0 4.2.4 1.6.6 1.1 1.0.0d1 6 289.1 1.6.3 1.3.6 2.6.5 1.3.0
    Model: iMac8,1, BootROM IM81.00C1.B00, 2 processors, Intel Core 2 Duo, 2.8 GHz, 6 GB, SMC 1.30f1
    Graphics: ATI Radeon HD 2600 Pro, ATI Radeon HD 2600 Pro, PCIe, 256 MB
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8C), Broadcom BCM43xx 1.0 (
    Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: WDC WD3200AAJS-40VWA1, 298.09 GB
    Parallel ATA Device: OPTIARC DVD RW AD-5630A
    USB Device: Maxtor 3200, 0x0d49 (Maxtor), 0x3200, 0xfa400000 / 2
    USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8502, 0xfd400000 / 2
    USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1a100000 / 2
    USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x820f, 0x1a110000 / 3
    USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x5d100000 / 2
    USB Device: Apple Optical USB Mouse, 0x05ac (Apple Inc.), 0x0304, 0x1d100000 / 2

  2. #2
    Join Date
    Jul 2003


    I'm no expert on these things, but I suspect these lines indicate something with the virtual memory, not a virtual machine:

    panic(cpu 1 caller 0x27adef): "vm_page_reactivate_local: count = 250, vm_page_local_count = 251\n"@/SourceCache/xnu/xnu-1504.15.3/osfmk/vm/vm_resident.c:3192

    Virtual memory involves "pages" and that's the reference that inclines me towards virtual memory issue rather than virtual memory.

    Now what's causing it I don't know. Disk? Bad RAM (getting dumped the HD)?

    That said, this is weird:
    BSD process name corresponding to current thread: ntpd
    ntpd is the network time protocal daemon

  3. #3
    Join Date
    Feb 2012


    I saw that as well and wondered whether it was referring to virtual memory, but couldn't see how that would cause a kernel panic.
    The RAM in the iMac is a couple of weeks old, I upgraded it from 2gb to 6gb and haven't had a peep out of it. Under normal circumstances, if there were repeated KPs I would look at the RAM, but I'm fairly confident that's not going to be the case here.
    I'm still waiting to find out if there was an external drive attached that could have caused an issue - as that unloaded kext is pointing at something...

  4. #4
    Join Date
    Mar 2001
    Virginia... where one Democrat CAN make a difference


    Any incompatible hardware item can cause a panic.

    How full is your boot drive? If it is extremely full then there is no room for VM to do its thing

    that said I suspect your new ram. 'upgrade and panic' usually means 'upgrade caused panic'

  5. #5
    Join Date
    Feb 2012


    I've not had any bad ram in probably 10 years, since I had a bad batch from OWC, and I doubt that it is the ram in this instance.
    The drive has about 100gb used of a 500gb drive, so it's not that either.
    The Mac was having problems when it came into me in the first place and those issues were fixed with a clean install of SL. As I said, it's a one-off in the three weeks since the ram was upgraded. I just wanted some more info on the kernel panic messages if I could get it.

  6. #6
    Join Date
    Feb 2001
    on the landline, Mr. Smith


    80+% of panics i see are RAM related, so fastest thing to diagnose, as long as you have some other RAM to test with. Maybe 10% are a bad RAM slot.

    The rest are PITA. Sometimes hardware (logic board, peripherals, etc.). Anything unusual or possibly damaged plugged in? Even bad USB stuff can cause issues once in a great while. Sometimes a specific OS update can wreak havoc on certain software versions, though usually not a KP.

    Does Safe Mode make any difference?

    I've never really mastered reading KP logs either........I can't add anything to what Eric ID'd.
    "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining." -- Jef Raskin

  7. #7
    Join Date
    Aug 2001
    Grangeville, ID USA


    Most of the KPs I see are incorrect driver or bad hard drive. Seen that a lot. Lots more often than bad ram. I guess I live in a different world than Unc, and this isn't in disagreement, cause he didn't say that 'most KPs are from RAM', but that most of them that he has seen appeared to have RAM being part of the problem.

    You have to check everything. Mostly they are mundane issues. Bad drive, incorrect driver, other bad component, bad memory module and so on. If the logs don't help - and frankly I haven't been helped by a kernel log in forever, then it is pulling parts, botting safe mode and standard music chairs diagnosis.

    molṑn labe'
    "I am a mortal enemy to arbitrary government and unlimited power. I am naturally very jealous for the rights and liberties of my country, and the least encroachment of those invaluable privileges is apt to make my blood boil."
--Ben Franklin

  8. #8
    Join Date
    Feb 2012


    As this is a one-off occurrence, so far, there's not much point in speculating on the cause. I just wondered if anyone knew more than I did about the log info and whether that could be useful in identifying issues that weren't ram related.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts