Kernel Panics: Corrupt Skip Lists

I recently upgraded my eMac's hard drive to a 160 GB hard drive. Before my eMac was very stable. I experienced maybe one or two kernel panics before upgrading. Now, they are a frequent experience. The curious thing is that all report the same error- "Corrupt Skip Lists". Yet, I cannot find any reference to this error anywhere. Also, I was running Panther before upgrading and switched to Tiger after installing the new drive. I suppose this could also be a factor. The odd thing is that these occur even when it's not running (has booted) off the new internal drive sometimes.
Here are some screen shots I've taken:
http://gamoe.net/imagebank/Other/eMacError/KernelPanic1.jpg
http://gamoe.net/imagebank/Other/eMacError/KernelPanic2.jpg
Any clues on this?

Interesting. A topic probably only for the more technically minded. Thank you for your response. I hadn't gotten any leads until now, even though I've posted about this elsewhere. Of course I added more RAM, it's the only decent thing to do, given Apple's traditional skimping on built-in/included RAM.
So I did as you suggested. I dug up the Apple Hardware Test CD, but it came up with nothing. I then downloaded and ran Memtest in the suggested single user mode under root. I had no idea it would take as long as it did, though I should have known, as it is an thorough test. I used the default suggested 3 passes. Results are as follows.
Test 1 gave me:
Bit Flip: FAILURE: 0xfffff3ff != 0xfffff7ff at offset 0x02c53b8b.
Test 3 gave me:
Stuck Address: FAILURE: possible bad address line at offset 0x00e52b8b.
Resulting in these conclusions:
* Address Test Failed * One or more DIMM address lines are non-functional.
* Memory Test Failed * Please check logfile for details.
Actually, I really have had no way of knowing if it was the hard drive or not. When I upgraded I also switched to Tiger, so it could be either. I must say that I am more a little surprised at the results, given that I installed this memory almost immediately after I bought the eMac, and it is Crucial RAM, which is known for quality, and it is the same RAM Apple uses for Macs. I've had absolutely no problems like this in the two years plus I've been using my eMac, under different versions of Mac OS X.
Given these results, can one reasonably conclude that the memory is responsible for the kernel panics? And, provided that the eMac has panicked even when it has not been booted up from the new internal drive, would you completely rule out the internal hard drive as the cause?-- Or can there be more to this?

Similar Messages

  • IBook G4 having "Corrupt Skip List" error

    Hello everybody, i'm having some problems with my little 12" iBook G4 800Mhz (128+128mb Ram memory).
    I've recently installed a 512mb Crucial PC2700 Ram module, in the original 128mb Apple memory slot.
    Since then, i'm getting kernel panics, the "Corrupt Skip List" error:
    "cpu-0 code= 00000007 corrupt skip list
    backtrace terminated - frame not mapped or invalid
    proceeding back via exception chain
    waiting for remote debugger connection."
    I tried to replace the Crucial memory with the original one, and it works fine.
    I've already repaired permissions, run Disk Utility and reset PRAM/NVRAM, as read in some old forum posts.
    No problems revealed, and nothing worked so far.
    Have you got any advice?
    Thank you in advance

    When did this happen? I guess I should hang around the Lounge more often. Just can't justify taking the time when I can't even make my rounds in the forums to which I subscribe on a regular basis. In any case, you have done well; I rejoice greatly.
    cornelius

  • Crash - "Corrupt Skip Lists"

    Hi,
    I had a system crash recently, the kind in which everything freezes and you get a failure report on top of the current screen. It read, among others, "Corrupt Skip Lists". (I made a photo of this, so I have other details)
    Somewhere on the net someone suggested that one of my RAMs might be broken, so I tried running the computer with only one at a time, but still it's not running very well. The main problems are crashes in InDesign and Photoshop, but occasionaly a system crash happens as well. Oh, and the Apple Hardware Test doesn't work from the system CD either - I don't even get the option to start it via restart/alt.
    Anybody any ideas of what else might be wrong, or what I might could try?
    Thanks,
    B.
    Power PC G4 Mac OS X (10.4.8)
    Power PC G4   Mac OS X (10.4.5)  

    It probably wouldn't hurt to run Disk Utility, and check out the hard drive. Also, repair permissions from Disk utility is also good to do.
    Having removed RAM, it would be wise to reset the PRAM/NVRAM. This is adviseable anytime hardware is added, or removed. Here is how to:
    http://docs.info.apple.com/article.html?artnum=2238
    OnyX is fairly good for maintenance routines, but can't really help in isolating trouble. A good, all purpose utility is TechTool. It checks most everything.
    If the crash issue continues, and no other hardware problems can be found, you may want to reinstall the OS.
    G4 AGP(450)Sawtooth   Mac OS X (10.4.8)   2ghzPPC,1.62gbSDRAM, ATI9800, DVR-109,(IntHD)120&160,LaCie160,23"Cinema Display

  • Kernel panic - corrupt stack

    My iBook g4 has a kernel panic (below text).
    It did a '3 beeb, flash light 5 times' crash last week but then re-booted fine. About 4 months ago, this happened repeatedly and the 'power down now' error message appeared on a black screen. Finally it refused to boot up at all and we took it apart and found a loose connection inside (I don't know what it was), reattached it and it has worked fine since.
    Am worried as I have stupidly not backed up recently and have a website on there that is due to posted. Please help!
    <start>
    System failure: cpu=0; code=00000001 (Corrupt stack)
    Latest crash info for cpu 0:
    Exception state (sv=0x19DC1000)
    PC=0x000940A0; MSR0x00001030; DAR=0x00000000; DSIR=0x42000000; LR=0x00093F8C; R1=0xFFFFFEE0; XCP=0x00000098 (System failure)
    Backtrace:
    backtrace terminated - frame not mapped or invalid: 0xFFFFFEE0
    Proceeding back via exemption chain:
    Exception state (sv0x19DC1000)
    PC=0x00094160; MSR=0x00001030; DAR=0x00000000; DSISR=0x42000000; LR=0x0009413C; R1=0x00000000; XCP=0x00000000C (0x300 - Data access)
    Exception state (sv0x19B6CC80)
    PC=0x90026BC8; MSR=0x0200F030; DAR=0x003B7018; DSISR=0x42000000; LR=0x90008DC0; R1=0xBFFFEB40; XCP=0x000000030 (0xC00 - System call)
    Kernel version:
    Darwin kernel version 7.9.0:
    Wed Mar 30 28:11:17 PST 2005; root:xnu/xnu-517.12.7.obj-1/RELEASE_PPC
    Memory access exception (1,0,0)
    ethernet MAC address: 00:00:00:00:00:00
    ip address: 0.0.0.0
    Waiting for remote debugger connection
    <end>
    iBook G4   Mac OS X (10.4.10)  

    First, sorry for the delay, I only work a few days a week
    Second, there is no panic.log on any of the machines. I looked in the console and system profiler programs in all the directories and searched in terminal using 'find / -name panic.log 2> /dev/null'. That is one reason I had to take a picture of it. I will try hard to get a panic.log.
    Keep in mind that these are very hard lockups so I am wondering if the kernel even CAN sync the log to disk in this situation. However, I come from the Linux world and am fairly new to Macs so perhaps I am expecting it to be a hardware problem when software really can make a Mac Kernel lockup.
    Furthermore they are networked together, we use LDAP/NFS home directories but each machine was prepared with it's own local copy of CS2. There is no sharing of the application.
    Also, i tried a boot with apple-v but all went well and there were no out of place message.
    Since my first posting I have also tried an fsck which revealed nothing but a clean FS.
    Also, we do use radmind to help clone machines. The OS was installed manually with our application loaded using radmind templates.
    We do use our Macs very heavily and use many applications at once using all RAM and heavy swap. Do the Mac Minis not like to be exercised hard? I think I may try to use a 1GB stick in a machine and see if that helps.
    Also, could CS2 really cause a complete lockup of the machine with a corrupt stack? To me an application-level program should never cause the machine to freeze or should never be able to corrupt memory it doesnt own unless the OS lets it meddle with hardware.

  • PowerMac G5 - Crashing, Hanging & Having Kernel Panics

    Okay, I've got quite a situation here folks. I bought a used PowerMac G5 1.6GHz. The first time I fired it up the fans sounded like a jet engine. After a quick thermal calibration that issue was solved. I'm only mentioning it in case it could having something to do with today's issue.
    So now what I've started getting with this machine is steady hanging (the screen freezes and everything is unresponsive) and kernel panics (both the fancy new "Please hold the power button" ones and the good old text ones). After I started experiencing this, I did some research. Almost everything pointed to bad RAM.
    I opened up the machine and found that the memory was installed in the following configuration:
    ---Slot 1--- 256MB PC2700 Chip with (M) logo (I believe this is Apple standard)
    ---Slot 2--- 256MB PC2700 Chip with (M) logo (I believe this is Apple standard)
    ---Slot 3--- 256MB PC2700 Chip (generic brand, mysteriously says DDR400 not 333)
    ---Slot 3--- 256MB PC2700 Chip (generic brand, mysteriously says DDR400 not 333)
    I ran quick RAM tests and found no problems with the RAM. Then I checked out an Apple document that says ram should be installed like:
    ---Slot 1--- Empty/Upgrade
    ---Slot 2--- Original RAM
    ---Slot 3--- Original RAM
    ---Slot 4--- Empty/Upgrade
    Tried moving the memory to this configuration and had the same issues. Then I tried removing the generic chips and leaving the Apple original stuff. Same result. I figured that had narrowed down the problem to one of those two chips, but I tried it with only the generic chips installed and had the same problem.
    On a whim I ran hard drive and CPU tests to double check that the problem was in the memory. No problems in those tests. I've tried everything I can think of:
    I reset the PMU
    I zapped the PRAM
    I tried every RAM arrangement possible
    I reinstalled the OS with a fresh copy
    No luck folks. Any ideas?

    I am having virtually the exact same problem--I also purchased a used 1.6 G5 and have very frequent and seemingly random crashes. I thought it was RAM also, so completely removed the existing sticks and replaced them with the good RAM I have in my G4 (which still runs and purrs like a **** kitten, although needs a new fan so is a bit loud). Had the same result. Swapped out a new 250g HD and formatted it with ONLY OSX and the basic upgrades in Software Update, but no other apps that I had initially installed on the existing 80G HD. Still crashing. I have gotten a couple crazy kernel errors and the really creepy "System Failure: Corrupt Skip Lists" message. I'm starting to flip out because all the forums are suggesting it could be this and that, but nothing seems to help! Have you found anything out yet?

  • Kernel Panics - 2013 13" MacBook Pro with Retina Display

    Hi everyone,
    I've been experiencing some system freezes lately, and upon investigating the console logs, each freeze seems to correspond to a kernel panic, which is listed as such:
    1/20/14 9:25:19.000 PM kernel[0]: BootCache: too many history clusters (150, limit 151)
    I'm running the computer with all original components (stock RAM, etc.), and the only externally-connected peripheral is an Apple Thunderbolt Display, which is connected by both Thunderbolt and MagSafe port.
    I've done a bit of Googling to see if this was a widespread/known issue, but didn't find anything conclusive, expect for a few similar reports, but very little follow-up information or detail.
    I'm curious if anyone else has experienced this problem, or if there's someone out there with a bit of hardware expertise who could share some insight.
    Thanks!
    Andrew
    Here are some console log screenshots:

    Thanks, Kappy. Here is everythign from the /Library/Logs/DiagnosticReports directory from today:
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      cl_kernels
    <DAE25C85-C11D-4D53-9E1B-E58A9F6911E2>
    cl_kernels
      cl_kernels
    <F0688B00-DFFF-4D54-91E7-7C251D62CA10>
    cl_kernels
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      com.microsoft.mbukernel
    14.3.9 (14.3.9)
    <57864ED6-EAE3-64B1-FDF8-C6DFB4F8EF50>
    /Applications/Microsoft Office 2011/*/mbukernel.framework/Versions/14/mbukernel
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      com.microsoft.mbukernel
    14.3.9 (14.3.9)
    <57864ED6-EAE3-64B1-FDF8-C6DFB4F8EF50>
    /Applications/Microsoft Office 2011/*/mbukernel.framework/Versions/14/mbukernel
      com.microsoft.wlmkernel
    14.3.9 (14.3.9)
    <55FFE62A-10D2-7C27-DFE2-77C3B481D385>
    /Applications/Microsoft Office 2011/*/WLMKernel.framework/Versions/14/WLMKernel
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      com.microsoft.mbukernel
    14.3.9 (14.3.9)
    <57864ED6-EAE3-64B1-FDF8-C6DFB4F8EF50>
    /Applications/Microsoft Office 2011/*/mbukernel.framework/Versions/14/mbukernel
      com.microsoft.wlmkernel
    14.3.9 (14.3.9)
    <55FFE62A-10D2-7C27-DFE2-77C3B481D385>
    /Applications/Microsoft Office 2011/*/WLMKernel.framework/Versions/14/WLMKernel
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      cl_kernels
    <DAE25C85-C11D-4D53-9E1B-E58A9F6911E2>
    cl_kernels
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <D14913DB-47F1-3591-8DAF-D4B4EF5F8818>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib
      libsystem_kernel.dylib
    (2422.1.72)
    <C5641F6C-E271-380A-A656-AE4C04345602>
    /usr/lib/system/libsystem_kernel.dylib

  • AR301 causing kernel panics in 64-bit mode

    I have had to add kernel panics to my list of problems with A3, and this time, it seems to crash when I had opened a small project, doing face recognition.
    I will try to continue my work today in 32-bit mode and see it that fares any better.
    Running A301 on a MP 2,66x2 dual core with 4GB of RAM and SnowLeo 10.6.2.
    Kjell Are

    sensors won't help.
    Sensors are hardware and SP likely talks to them in a similar manner as the procs I'd guess. If you can follow that lead it may shed light. Got to start somewhere
    You know this one from the terminal, right?
    sysctl -a machdep.cpu
    machdep.cpu.thread_count: 2
    machdep.cpu.core_count: 2
    machdep.cpu.address_bits.virtual: 48
    machdep.cpu.address_bits.physical: 36
    machdep.cpu.tlb.data_large: 32
    machdep.cpu.tlb.inst_large: 8
    machdep.cpu.tlb.data_small: 256
    machdep.cpu.tlb.inst_small: 128
    machdep.cpu.cache.size: 4096
    machdep.cpu.cache.L2_associativity: 8
    machdep.cpu.cache.linesize: 64
    machdep.cpu.archperf.fixedwidth: 0
    machdep.cpu.archperf.fixednumber: 0
    machdep.cpu.arch_perf.events: 0
    machdep.cpu.archperf.eventsnumber: 7
    machdep.cpu.arch_perf.width: 40
    machdep.cpu.arch_perf.number: 2
    machdep.cpu.arch_perf.version: 2
    machdep.cpu.thermal.ACNT_MCNT: 1
    machdep.cpu.thermal.thresholds: 2
    machdep.cpu.thermal.dynamic_acceleration: 0
    machdep.cpu.thermal.sensor: 1
    machdep.cpu.mwait.sub_Cstates: 139808
    machdep.cpu.mwait.extensions: 3
    machdep.cpu.mwait.linesize_max: 64
    machdep.cpu.mwait.linesize_min: 64
    machdep.cpu.microcode_version: 199
    machdep.cpu.coresperpackage: 2
    machdep.cpu.logicalperpackage: 2
    machdep.cpu.extfeatures: XD EM64T
    machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM
    machdep.cpu.brand: 0
    machdep.cpu.signature: 1782
    machdep.cpu.extfeature_bits: 537919488 1
    machdep.cpu.feature_bits: -1075053569 58301
    machdep.cpu.stepping: 6
    machdep.cpu.extfamily: 0
    machdep.cpu.extmodel: 0
    machdep.cpu.model: 15
    machdep.cpu.family: 6
    machdep.cpu.brand_string: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz
    machdep.cpu.vendor: GenuineIntel

  • Corrupt Encrypted Sparseimage, PrivateFrameworks and Kernel Panics

    Hi Maclovers,
    After a kernel panic my encrypted sparseimage with valuable data won't mount:
    # hdiutil attach sec3.bak.sparseimage
    hdiutil: attach failed - Defektes Image // german for 'corrupt image'
    Attaching the following string:
    0000b90: 2c45 0000 0000 0000 0000 0000 0000 0000 ,E..............
    0000ba0: 0000 0001 6364 7361 656e 6372 ....cdsaencr
    gives:
    diskimages-helper(11183) malloc: * vm_allocate(size=3190173696) failed (error code=3)
    diskimages-helper(11183) malloc: * error: can't allocate region
    diskimages-helper(11183) malloc: * set a breakpoint in szone_error to debug
    hdiutil: attach failed - Speicher kann nicht zugewiesen werden // german for 'memory not allocable'
    Okay, no problem I thought, Mac OS X builds on Open Source Software, so I can decrypt the sparseimage by hand (with perl) and rescue the needed data with a hexeditor.
    But, the DiskImages Framework (/System/Library/PrivateFrameworks/DiskImages.framework/DiskImages) is not Open Source
    From poking around with gdb and strings I learned that hdiutil uses sha,sha1,sha256,sha512 and md5. But I was unable to figure out
    - how the password is expanded for the 128 bit aes key (plain md5/sha0,1,256,512 won't work)
    - in which mode aes runs (ecb/cbc/ofb)
    Do you know it and can you give me a hint?
    Btw: from gdb:
    openssl related
    0x9194711c aes128_cbccipher
    0x9196cd9a aes128_cfb128cipher
    0x9196cddf aes128_ecbcipher
    0x9196ce39 aes128_ofbcipher
    calling from here?
    0x97e6ba5e CEncryptedEncoding::encodePasswordHeader(Security::CssmData const&, Security::CssmData const&, CEncryptedEncoding::PasswordHeader&)
    0x97e6bd72 CEncryptedEncoding::generateKeyBlob(Security::CssmAutoData&)
    0x97e6bece CEncryptedEncoding::parseKeyBlob(Security::CssmData const&)
    more functions
    0x91946660 AESset_encryptkey
    0x91946a5b AESset_decryptkey
    0x9194715c AEScbcencrypt
    0x919473df AES_encrypt
    0x91947880 AES_decrypt
    0x9194dd91 AEScfb128encrypt
    0x9194de42 AEScfbr_encryptblock
    0x9194df86 AEScfb1encrypt
    0x9194e046 AEScfb8encrypt
    0x9194e095 AESctr128encrypt
    0x9194e20b AESecbencrypt
    0x9194e232 AES_options
    0x9194e242 AESofb128encrypt
    Here's some debug info:
    si hdiutil attach -debug sec3.bak.sparseimage calling DIHLDiskImageAttach with
    <CFDictionary 0x3161a0 [0xa08011c0]>{type = mutable, count = 7, capacity = 8, pairs = (
    2 : <CFString 0x42898 [0xa08011c0]>{contents = "debug"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    3 : <CFString 0x428d8 [0xa08011c0]>{contents = "drive-options"} = <CFDictionary 0x3160e0 [0xa08011c0]>{type = mutable, count = 0, capacity = 4, pairs = (
    5 : <CFString 0x42888 [0xa08011c0]>{contents = "verbose"} = <CFBoolean 0xa0801884 [0xa08011c0]>{value = false}
    6 : <CFString 0x42658 [0xa08011c0]>{contents = "agent"} = <CFString 0x42648 [0xa08011c0]>{contents = "hdiutil"}
    7 : <CFString 0x428b8 [0xa08011c0]>{contents = "main-url"} = <CFURL 0x316390 [0xa08011c0]>{type = 0, string = sec3.bak.sparseimage,
    base = <CFURL 0x3163f0 [0xa08011c0]>{type = 0, string = /Users/felix/Desktop/si/, base = (null)}}
    8 : <CFString 0x428c8 [0xa08011c0]>{contents = "image-options"} = <CFDictionary 0x316110 [0xa08011c0]>{type = mutable, count = 0, capacity = 4, pairs = (
    10 : <CFString 0x428a8 [0xa08011c0]>{contents = "quiet"} = <CFBoolean 0xa0801884 [0xa08011c0]>{value = false}
    2006-06-13 10:44:39.197 hdiutil[11290] using helper tool at "/System/Library/PrivateFrameworks/DiskImages.framework/Resources/diskimages-he lper".
    2006-06-13 10:44:39.232 hdiutil[11290] connectToFramework
    2006-06-13 10:44:39.233 hdiutil[11290] connectToFramework: about to ask proxy to perform operation
    status proc called: initialize
    2006-06-13 10:44:39.254 diskimages-helper[11291] _imageOptions: {"enable-keychain" = 1; }
    2006-06-13 10:44:39.254 diskimages-helper[11291] _driveOptions: {autodiskmount = 1; "unmount-timeout" = 0; }
    2006-06-13 10:44:39.254 diskimages-helper[11291] DIHelperAttach: initializing framework
    DILoadDriver: checking for disk image driver...DILoadDriver: DI_kextExists() returned 0x00000000 (0)...DIIsInitialized: returning NO2006-06-13 10:44:39.266 diskimages-helper[11291] DIHelperAttach: resolving disk image
    DIIsInitialized: returning YESDIIsInitialized: returning YESDIBackingStoreNewWithCFURL: entry with
    <CFURL 0x3208c0 [0xa08011c0]>{type = 15, string = file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage, base = (null)}
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIBackingStoreInstantiatorProbe: entry
    <CFURL 0x3208c0 [0xa08011c0]>{type = 15, string = file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage, base = (null)}
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
    CBSDBackingStore::newProbe score 100 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
    DIBackingStoreInstantiatorProbe: probing interface 1 CRAMBackingStore
    CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
    CRAMBackingStore::probe: score -1000 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
    DIBackingStoreInstantiatorProbe: probing interface 2 CCarbonBackingStore
    CCarbonBackingStore::newProbe: setting initial rval to +100
    CCarbonBackingStore::newProbe score 100 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
    DIBackingStoreInstantiatorProbe: probing interface 3 CDevBackingStore
    CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Users/felix/Desktop/si/sec3.bak.sparseimage).CDevBackingStore::newProbe score -1000 for
    DIBackingStoreInstantiatorProbe: probing interface 4 CCURLBackingStore
    CCURLBackingStore::probe: scheme is
    file
    CCURLBackingStore::probe: not recognized URL scheme.
    CCURLBackingStore::probe: score -1000 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
    DIBackingStoreInstantiatorProbe: probing interface 5 CVectoredBackingStore
    CVectoredBackingStore::newProbe not "vectored" scheme.
    CVectoredBackingStore::newProbe score -1000 for file://localhost/Users/felix/Desktop/si/sec3.bak.sparseimage
    DIBackingStoreNewWithCFURL: CBSDBackingStore
    DIBackingStoreNewWithCFURL: instantiator returned 0
    DIBackingStoreNewWithCFURL: returning 0x00000000
    DIResolveURLToBackingStore: processing level 1 encodings.
    DIFileEncodingNewWithBackingStore: entry for encoding level 1
    DIFileEncodingInstantiatorProbe: entry for level 1
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIFileEncodingInstantiatorProbe: probing level 1 interface 0 CMacBinaryEncoding
    CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
    CBSDBackingStore::closeDataFork: about to close 500000000: 4e9d dbc8 b429 00eb e882 36a3 d561 9fbd | N....)....6..a.. |
    00000010: ed78 e737 a8bd 55cc f2f3 ad7a 42cd 7379 | .x.7..U....zB.sy |
    00000020: 0499 4256 7ae3 df72 f032 664d c214 074c | ..BVz..r.2fM...L |
    00000030: 1b84 2b0a b849 18c0 c65a dfd9 0ae8 c6dd | ..+..I...Z...... |
    00000040: b6db 15ee 39ce db43 f3cf 7a33 8628 d8b3 | ....9..C..z3.(.. |
    00000050: fefa 725e 148d ecda e728 3889 bcb2 bb27 | ..r^.....(8....' |
    00000060: 3d78 2e88 652f 8e27 71eb a44a 98ca 3148 | =x..e/.'q..J..1H |
    00000070: 0780 a593 0e20 6f81 c2a7 f17d 1d87 5b48 | ..... o....}..[H |
    diskimages-helper: fileNameLength $0000009D
    diskimages-helper: resourceForkLength $DAE72838
    diskimages-helper: dataForkLength $5E148DEC
    diskimages-helper: commentLength $00008865
    diskimages-helper: MacBinary III signature ?'q? (0x8E2771EB)
    diskimages-helper: header CRC $00001D87
    diskimages-helper: minimum decoder version $0000007D
    diskimages-helper: encoder version $000000F1
    no MacBinary III signature - checking for MacBinary I or IIDIFileEncodingInstantiatorProbe: probing level 1 interface 1 CAppleSingleEncoding
    CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
    00000000: c8db 9d4e eb00 29b4 e882 36a3 d561 9fbd | ...N..)...6..a.. |
    00000010: ed78 e737 a8bd 55cc f3f2 ad7a 42cd 7379 | .x.7..U....zB.sy |
    00000020: 0499 4256 7ae3 .... .... .... .... .... | ..BVz........... |
    CBSDBackingStore::closeDataFork: about to close 5CAppleSingleEncoding::isAppleSingleFile loadAppleSingleHeader failed with error 22
    DIFileEncodingInstantiatorProbe: probing level 1 interface 2 CEncryptedEncoding
    CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
    CBSDBackingStore::closeDataFork: about to close 5DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
    DIFileEncodingNewWithBackingStore: returning 0x0000006A
    DIResolveURLToBackingStore: level 1 encoding match failed. 106.
    (continuing)
    DIResolveURLToBackingStore: processing level 2 encodings.
    DIFileEncodingNewWithBackingStore: entry for encoding level 2
    DIFileEncodingInstantiatorProbe: entry for level 2
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIFileEncodingInstantiatorProbe: probing level 2 interface 0 CUDIFEncoding
    CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
    CBSDBackingStore::closeDataFork: about to close 5CUDIFEncoding::newProbe: failing because backing store is not UDIF file
    DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
    DIFileEncodingNewWithBackingStore: returning 0x0000006A
    DIResolveURLToBackingStore: level 2 encoding match failed. 106.
    (continuing)
    DIResolveURLToBackingStore: processing level 3 encodings.
    DIFileEncodingNewWithBackingStore: entry for encoding level 3
    DIFileEncodingInstantiatorProbe: entry for level 3
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIFileEncodingInstantiatorProbe: probing level 3 interface 0 CSegmentedNDIFEncoding
    checkTypeCreator: /
    checkTypeCreator: returning , score 0
    CSegmentedNDIFEncoding::isSegmentedNDIFFile checkTypeCreator failed
    DIFileEncodingInstantiatorProbe: probing level 3 interface 1 CSegmentedUDIFEncoding
    CSegmentedUDIFEncoding::isSegmentedUDIFFile backing store is not of type CUDIFEncoding
    DIFileEncodingInstantiatorProbe: probing level 3 interface 2 CSegmentedUDIFRawEncoding
    DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
    DIFileEncodingNewWithBackingStore: returning 0x0000006A
    DIResolveURLToBackingStore: level 3 encoding match failed. 106.
    (continuing)
    DIIsInitialized: returning YESDIDiskImageNewWithBackingStore: entry with
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIDiskImageInstantiatorProbe: entry
    <CFDictionary 0x30c1b0 [0xa08011c0]>{type = mutable, count = 2, capacity = 4, pairs = (
    0 : <CFString 0x406c0 [0xa08011c0]>{contents = "enable-keychain"} = <CFBoolean 0xa080188c [0xa08011c0]>{value = true}
    1 : <CFString 0x407b0 [0xa08011c0]>{contents = "image-path"} = <CFString 0x30c2e0 [0xa08011c0]>{contents = "/Users/felix/Desktop/si/sec3.bak.sparseimage"}
    DIDiskImageInstantiatorProbe: probing interface 0 CDARTDiskImage
    DIDiskImageInstantiatorProbe: probing interface 1 CDiskCopy42DiskImage
    DIDiskImageInstantiatorProbe: probing interface 2 CNDIFDiskImage
    checkTypeCreator: /
    checkTypeCreator: returning , score 0
    CNDIFDiskImage::checkExtension: sparseimage
    CNDIFDiskImage::newProbe: checkExtension gives score -1000.
    DIDiskImageInstantiatorProbe: probing interface 3 CUDIFDiskImage
    CUDIFDiskImage::checkBackingStoreType: backing store is wrong type
    DIDiskImageInstantiatorProbe: probing interface 5 CRawDiskImage
    checkBackingStoreType returned score 0 type
    checkTypeCreator returned score 0 type
    CRawDiskImage::checkExtension: sparseimage
    checkExtension returned score -1000 type
    CRawDiskImage::newWithBackingStore: setBackingStore() failed. 106
    CRawDiskImage: checkBackingStoreLength score: -100
    DIDiskImageInstantiatorProbe: probing interface 6 CShadowedDiskImage
    DIDiskImageInstantiatorProbe: probing interface 7 CSparseDiskImage
    CSparseDiskImage::checkExtension: sparseimage
    DIDiskImageInstantiatorProbe: probing interface 8 CCFPlugInDiskImage
    DIDiskImageInstantiatorProbe: probing interface 9 CWrappedDiskImage
    DIBackingStore::inUse: this->_fUniqueID
    <CFArray 0x320590 [0xa08011c0]>{type = immutable, count = 1, values = (
    0 : <CFString 0x320dc0 [0xa08011c0]>{contents = "d234881026:i316148"}
    DI_kextCreateDiskImageIdentifierArray: exiting
    <CFArray 0x31fd00 [0xa08011c0]>{type = mutable-small, count = 1, values = (
    0 : <CFDictionary 0x321100 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, pairs = (
    3 : <CFString 0x321000 [0xa08011c0]>{contents = "writeable-components"} = <CFArray 0x320fe0 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, values = (
    0 : <CFString 0x321080 [0xa08011c0]>{contents = "d234881026:i1808676"}
    DIBackingStore::inUse: checking against image dictionary array
    <CFArray 0x3210f0 [0xa08011c0]>{type = immutable, count = 1, values = (
    0 : <CFDictionary 0x321100 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, pairs = (
    3 : <CFString 0x321000 [0xa08011c0]>{contents = "writeable-components"} = <CFArray 0x320fe0 [0xa08011c0]>{type = fixed-mutable, count = 1, capacity = 1, values = (
    0 : <CFString 0x321080 [0xa08011c0]>{contents = "d234881026:i1808676"}
    DIBackingStore::inUse: checking our list looking for who's naughty and nice
    DIBackingStore::inUse: checking image 0000
    CBSDBackingStore::openDataFork: about to open /Users/felix/Desktop/si/sec3.bak.sparseimage
    syncPhysicalAndLogicalForkLengths: returning 0 (cached logEOF: 1540853760, physEOF: 1540853760)
    CBSDBackingStore::closeDataFork: about to close 5CSparseFile::~CSparseFile: WARNING flushing header and index nodes failed. Invalid argument
    syncPhysicalAndLogicalForkLengths: entry (cached logEOF: 1540853760, physEOF: 1540853760)
    : returning 0 (new cached logEOF: 1540853760, physEOF: 1540853760)
    DIDiskImageNewWithBackingStore: returning 0x00000067
    DIResolveBackingStoreToDiskImage: unable to resolve to any disk image class. 103.
    DIResolveURLToDiskImage: resolving disk image format failed. 103.
    status proc called: attach
    error code: 103
    status proc called: cleanup
    2006-06-13 10:44:39.684 diskimages-helper[11291] DIHelperAttach performOperation: returning 103
    2006-06-13 10:44:39.684 diskimages-helper[11291] DIHelper perform_operation: returning {payload = {}; "result-code" = 103; }
    2006-06-13 10:44:39.684 hdiutil[11290] connectToFramework: proxy has finished operation
    2006-06-13 10:44:39.685 hdiutil[11290] results are: {payload = {}; "result-code" = 103; }
    2006-06-13 10:44:39.685 hdiutil[11290] _threadResultsError is 103
    2006-06-13 10:44:39.685 hdiutil[11290] connectToFramework: terminating proxy
    2006-06-13 10:44:39.686 diskimages-helper[11291] terminateHelper
    DIHLDiskImageAttach() returned 103
    <CFDictionary 0x3245a0 [0xa08011c0]>{type = immutable, count = 0, capacity = 0, pairs = (
    hdiutil: attach failed - Defektes Image
    si 2006-06-13 10:44:39.786 diskimages-helper[11291] -DIHelperAgentMaster terminateUIAgentConnection
    2006-06-13 10:44:39.786 diskimages-helper[11291] -exitIfPossible:0 (_drivesServed 0)
    2006-06-13 10:44:39.787 diskimages-helper[11291] -exitWatchThread: trying to get exit lock
    2006-06-13 10:44:39.787 diskimages-helper[11291] -exitWatchThread: got exit lock
    2006-06-13 10:44:39.787 diskimages-helper[11291] -exitWatchCompleted:0
    2006-06-13 10:44:40.788 diskimages-helper[11291] suicide:<NSCFTimer: 0x3217d0>
    cheers, felix
    MBP 15" Mac OS X (10.4.6)

    The key expansion does not work with a substring of the upper hash functions. Create a sparseimage with the password asdf and try the following script:
    #!/opt/local/bin/perl
    use Crypt::GCrypt;
    my $tmp;
    my $i;
    my $subkey;
    # asdf
    %pw = (
    ph => (pack "H*", "61736466000000000000000000000000"),
    pl => (pack "H*", "00000000000000000000000061736466"),
    md5 => (pack "H*", "912ec803b2ce49e4a541068d495ab570"),
    sha1 => (pack "H*", "3da541559918a808c2402bba5012f6c60b27661c"),
    sha => (pack "H*", "71f2cbe0db64c15e9e385525ad5ef854c494898f"),
    sha256 => (pack "H*", "f0e4c2f76c58916ec258f246851bea091d14d4247a2fc3e18694461b1816e13b"),
    sha512 => (pack "H*", "401b09eab3c013d4ca54922bb802bec8fd5318192b0a75f201d8b3727429080fb337591abd3e44 453b954555b7a0812e1081c39b740293f765eae731f5a65ed1"),
    open (INFILE, "< $ARGV[0]") or die "Could not open $filename for reading: $!";
    read(INFILE,$tmp,128);
    close INFILE;
    foreach my $key (keys %pw) {
    for($i=16;$i <= length $pw{$key};$i++) {
    $subkey = substr($pw{$key},$i-16,16);
    #print "------using $key with $pw{$key} and substr $subkey-------";
    $cipher = Crypt::GCrypt->new(
    type => 'cipher',
    algorithm => 'aes',
    mode => 'ecb'
    $cipher->start('decrypting');
    $cipher->setkey($subkey);
    print $cipher->decrypt($tmp);
    }

  • SA_MAGIC header corrupt on ZFS causing kernel panic in S11.1 SRU5.5

    I have a number of Sun Fire x4500s and x4540s running S11.1 SRU5.5. One of the x4540s has recently started kernel panicking within minutes of powering on and sharing its file systems over NFS (it provides user directories for a computing cluster). If I don't share via NFS, the kernel panics do not occur.
    When I run mdb on the kernel panic coredump I get:
    \> ::panicinfo
    cpu 1
    thread fffffffc80e52c20
    message
    assertion failed: BSWAP_32(hdr->sa_magic) == SA_MAGIC, file: ../../common/fs/zfs/sa.c, line: 2079
    \> ::stack
    vpanic()
    0xfffffffffbac1081()
    sa_get_field64+0x96(ffffc1c0aaf34a00, 18)
    zfs_space_delta_cb+0x46(2c, ffffc1c0aaf34a00, fffffffc80e52840, fffffffc80e52848)
    dmu_objset_userquota_get_ids+0xca(ffffc1c1085d9008, 0, ffffc1c080796640)
    dnode_sync+0xa7(ffffc1c1085d9008, ffffc1c080796640)
    dmu_objset_sync_dnodes+0x7f(ffffc1c0299a5b00, ffffc1c0299a5a80, ffffc1c080796640)
    dmu_objset_sync+0x1e2(ffffc1c0299a5940, ffffc1c07f0d17c8, ffffc1c030756680, ffffc1c080796640)
    dsl_dataset_sync+0x63(ffffc1c0418cd300, ffffc1c07f0d17c8, ffffc1c080796640)
    dsl_pool_sync+0xdb(ffffc1c0285493c0, 2c720a)
    spa_sync+0x395(ffffc1c01b1f6a80, 2c720a)
    txg_sync_thread+0x244(ffffc1c0285493c0)
    thread_start+8()In doing some google searching, I'm able to infer from similar lines of code in OpenSolaris (and various ZFS derivatives) that the point of this line of code is to ensure that a ZFS block has a particular header with the correct endianness. Lines of code just prior to this swap the endianness if its is incorrect (at least in these derivatives). For example:
    [ZFS corruption probably from bad RAM|https://github.com/zfsonlinux/spl/issues/157]
    [FreeBSD kernel panic|http://lists.freebsd.org/pipermail/freebsd-stable/2012-July/068882.html]
    [ZFSOnLinux Panic|https://github.com/zfsonlinux/zfs/issues/1303]
    So basically, this assert ought to work unless the header was written to disk incorrectly. I've recently done a resilver since a disk had failed and I'm currently in the middle of a scrub with estimated 90h to go. It did fix about 12kb of mistakes on the scrub even though it was right after the resilver.
    Nevertheless, I don't think this should be able to happen unless the redundant copies of this header were also corrupted.
    I wrote a little script that loops over process IDs and addresses in the core dump and prints this for each
    echo $addr | awk '{print $1,"::pfiles"}' | mdb $DMPNO
    The files that are open are all device files (eg./devices/pseudo/...) or things in /var, /etc, /lib, things like that. The user directories/files do not appear to be actively open in the core dump. That said, I cannot match the thread above to a process ID. So maybe there are open files that are not captured in the core dump
    Since the machine will panic when I make NFS available, I am currently doing two things to try to resolve the problem:
    (1) a zpool scrub
    (2) "zfs send"ing a snapshot of every filesystem straight to /dev/null
    The idea behind (2) is that eventually I'll read the bad block and force the kernel panic to happen. I'll infer from the log of the script which filesystem is bad and NFS share all the others.
    You should assume that I can spell mdb, but not much more than that and everything I've done thus far has been mimicking things I have found in google searching.
    Thanks for any advice the community has to help me fix the bad file/filesystem. I am happy to provide more details from mdb or whatever is needed.
    Tom
    Edited by: 998996 on Apr 9, 2013 7:13 AM
    Edited by: 998996 on Apr 9, 2013 7:13 AM
    Edited by: 998996 on Apr 9, 2013 7:14 AM
    Edited by: 998996 on Apr 9, 2013 7:18 AM
    Edited by: 998996 on Apr 9, 2013 8:48 AM

    The output of fmdump is below. On March 27th, 3 disks were automatically identified as having too many errors and were pulled from their zpools. I replaced them on April 2nd (I believe) and, while they were resilvering, kernel panics started happening on April 6th. After several panic / reboot cycles, I disabled NFS and have not experienced any panics sense. The resilver finished sometime on April 7th (I think) and I started a zpool scrub relatively soon thereafter.
    Mar 27 11:21:05.6894 2b5fca6d-8a55-6a16-d59a-86abf600ce1e DISK-8000-0X Diagnosed
    Mar 27 11:21:18.2224 335f323c-c723-e67f-c194-a346edde5f41 DISK-8000-0X Diagnosed
    Mar 27 11:21:43.8004 f515a18e-235d-c9e8-9b11-ff7284ed1b48 DISK-8000-0X Diagnosed
    Mar 31 12:27:08.8977 864387c6-9b50-6f90-d710-9e213a0ba327 SUNOS-8000-KL Diagnosed
    Apr 02 15:37:45.7040 2b5fca6d-8a55-6a16-d59a-86abf600ce1e FMD-8000-58 Updated
    Apr 02 15:37:45.8345 335f323c-c723-e67f-c194-a346edde5f41 FMD-8000-58 Updated
    Apr 02 15:37:45.9517 f515a18e-235d-c9e8-9b11-ff7284ed1b48 FMD-8000-58 Updated
    Apr 02 15:50:44.1012 2b5fca6d-8a55-6a16-d59a-86abf600ce1e FMD-8000-4M Repaired
    Apr 02 15:50:44.1429 2b5fca6d-8a55-6a16-d59a-86abf600ce1e FMD-8000-6U Resolved
    Apr 02 15:51:00.5162 f515a18e-235d-c9e8-9b11-ff7284ed1b48 FMD-8000-4M Repaired
    Apr 02 15:51:00.5614 f515a18e-235d-c9e8-9b11-ff7284ed1b48 FMD-8000-6U Resolved
    Apr 02 15:51:18.9518 335f323c-c723-e67f-c194-a346edde5f41 FMD-8000-4M Repaired
    Apr 02 15:51:18.9959 335f323c-c723-e67f-c194-a346edde5f41 FMD-8000-6U Resolved
    Apr 02 15:55:22.0946 1ccd6f62-7607-6f63-9069-9d947691df4b ZFS-8000-LR Diagnosed
    Apr 02 15:56:14.7847 f8d032c1-5d6e-e742-f01a-e2f38ccc6ce8 ZFS-8000-QJ Diagnosed
    Apr 02 15:59:05.6633 5564cf7e-3648-cd69-915f-9b6757509bae ZFS-8000-QJ Diagnosed
    Apr 02 15:59:05.8154 0214c0e7-59b6-47ca-c8c6-853d76713257 ZFS-8000-D3 Diagnosed
    Apr 02 16:01:14.5517 513db3ba-27a7-c8f2-f50e-8ef58c0fa71c ZFS-8000-QJ Diagnosed
    Apr 06 05:49:43.6917 eddb3a8f-9117-cfa8-8784-a1fceb242f7f SUNOS-8000-KL Diagnosed
    Apr 06 06:44:24.2562 6186711a-735a-67f7-9226-be419378c70e SUNOS-8000-KL Diagnosed
    Apr 06 07:20:45.2416 33b36e54-c2cd-ee0e-b370-821a00d342fe SUNOS-8000-KL Diagnosed
    Apr 06 08:05:29.7940 a7f6d49b-6b15-ef5a-ca58-911e2c6b1196 SUNOS-8000-KL Diagnosed
    Apr 06 08:28:06.7965 e4eea2e9-c800-e1c9-bd53-c45af9b616b0 SUNOS-8000-KL Diagnosed
    Apr 06 08:56:21.9017 a51779c9-549a-4334-f102-d26ff958c566 SUNOS-8000-KL Diagnosed
    Apr 06 09:26:33.7999 25e4e137-7962-e70f-ea91-f77dfdd8238b SUNOS-8000-KL Diagnosed
    Apr 06 09:47:56.5975 2d416320-f69e-e5c5-ea66-cafab1997546 SUNOS-8000-KL Diagnosed
    Apr 06 10:19:35.7141 ae4e7ef4-bbf5-e80a-8e30-8a99bafbc352 SUNOS-8000-KL Diagnosed
    Apr 06 11:07:14.7489 abc3c89c-d9f9-ee00-e546-99cbff435810 SUNOS-8000-KL Diagnosed
    Apr 06 11:51:31.1321 7aa0ab5e-d54c-4201-e56f-e8a502bb063e SUNOS-8000-KL Diagnosed
    Apr 06 12:17:42.4073 46d85a95-8f15-c0ea-e061-f241628d124a SUNOS-8000-KL Diagnosed
    Apr 06 12:48:15.4996 d16c0c54-33d5-c463-dae8-fc8cc82e517b SUNOS-8000-KL Diagnosed
    Apr 06 13:14:45.4799 021e8659-5359-edea-c7e9-8551c7de6d2c SUNOS-8000-KL Diagnosed
    Apr 06 13:51:56.5406 89620151-c97f-4256-8347-f412ee416282 SUNOS-8000-KL Diagnosed
    Apr 06 14:11:47.2594 b9923bc1-46d6-4fb6-ec7d-f3a1e0076419 SUNOS-8000-KL Diagnosed
    Apr 07 12:54:49.3759 513db3ba-27a7-c8f2-f50e-8ef58c0fa71c FMD-8000-4M Repaired
    Apr 07 12:54:49.4121 513db3ba-27a7-c8f2-f50e-8ef58c0fa71c FMD-8000-6U Resolved
    Apr 07 12:54:49.5092 0214c0e7-59b6-47ca-c8c6-853d76713257 FMD-8000-4M Repaired
    Apr 07 12:54:49.5368 0214c0e7-59b6-47ca-c8c6-853d76713257 FMD-8000-6U Resolved
    Apr 07 12:54:49.5864 5564cf7e-3648-cd69-915f-9b6757509bae FMD-8000-4M Repaired
    Apr 07 12:54:49.6064 5564cf7e-3648-cd69-915f-9b6757509bae FMD-8000-6U Resolved
    Apr 07 12:54:49.6367 f8d032c1-5d6e-e742-f01a-e2f38ccc6ce8 FMD-8000-4M Repaired
    Apr 07 12:54:49.6498 f8d032c1-5d6e-e742-f01a-e2f38ccc6ce8 FMD-8000-6U Resolved
    Apr 07 12:54:49.7409 1ccd6f62-7607-6f63-9069-9d947691df4b FMD-8000-4M Repaired
    Apr 07 12:54:49.7585 1ccd6f62-7607-6f63-9069-9d947691df4b FMD-8000-6U Resolved
    The output of fmadm faulty and fmdump -eV are quite long:
    https://pantherfile.uwm.edu/downes/public/fmdump_ev.txt
    https://pantherfile.uwm.edu/downes/public/fmadm_faulty.txt
    I note a number of events on April 9th in the output of fmdump -eV. Maybe these are the scrub fixing things?
    Tom

  • Kernel Panics, Drive Corruption, Directory Issues.

    Desktop M8840LL/A Dual 1.25GHz PowerPC G4 (FW800) MDD
    2GB Ram, 2 WD - 500GB IDE Drives Internal, 4 SATA Dr (2 WD - 500 GB SATA internal 1 WD 500GB SATA, One WD 640GB SATA external ), Sonnet Tempo SATA X4i PCI Card, ATI 9600Pro AGP, 1- 23in Apple Cinema Display, One 24in Samsung Display. 3 Firewire 250Gb WD external Drives.
    This setup was running great for 2 years until a four year old WD drive failed 3 weeks ago and corrupted its data etc. I had the data backed up so no panic.
    I decided to replaced it 3 weeks ago with a new 500GB WD IDE and reinstall 10.5 and migrate users for that drive.
    Ever since I have been getting daily if not hourly kernel panics and issues with ALL drives on my system.
    At one point the system loscked 4 drives and I could not access them at all.
    Discussion group helped fix that issue.
    I have managed to saved all my important data to a 500GB drive without a system on it and hopefully can deal with the issues at hand without worrying about the data.
    Booted from my System 1.5 install disk and had a dark grey/ Must restart your mac screen while I was booting from the DVD!
    Did an Apple Service diagnostics on the machine and all was great - no issues.
    So I did a clean install on a drive and all looked great!
    No other software installed except the system.
    Rebooted OK.
    I then did the apple software update and restarted.
    No startup!
    Rebooted with option key down - no drives??
    I have been working on this for three days and seem to be going backwards at best.
    I can boot sometimes and usually get a kernal panic eventually.
    It can happen right away or an hour later.
    Sometimes I get a message "your computer was shut down etc" sometimes I don't!?
    Sometimes I get a startup chime - sometimes I don't!!??
    What should I do next?
    Advise whatever info you might need and I will do my best to provide it.

    I stripped my Mac down to barebones incluing original 80GB Drive 512 RAM and Original Video card and started over.
    To make a long procedure shorter I found that all hardware was OK and after running ASD to confirm I reinstalled all my hardware/Add ins except for drives.
    I then started to check each drive individually with Applejack and then formatting and reinstalling virgin systems on each drive.
    Applejack and/or the system DVD would not fix and/or install on three of the Hard Drives (1 IDE 500GB and 2 500GB SATA)due to permission corruption. I could not do anything with these drives at all!
    When I had these individual drives in the computer I experienced kernel panics with every one!
    All the drives were under warranty and Western Digital replaced all of them. (I cannot begin to tell you how great Western Digital was in turnaround time and cross shipping and help in this matter.) Their warranty service is the best I have ever experienced bar none!
    I am now running non stop for nearly a week without any kernel panic or problem whatsoever. I have also noticed a significant speed up in my computer.
    I have rebooted many times and run non stop for days at a time.
    I maintain my computer with maintenance scripts once per week and do it faithfully and this type of permission issue can still occur!
    Without my backups there would have been a disaster for me.
    Many thanks to all the peolpe that emailed help to me from all sources.
    Sometimes out of the worst of situations good prevails.

  • Kernel panics, graphic file corruption with Firewire

    I've been having consistent problems with Firewire since I got my Mac Pro last year. I only recently narrowed it down to Firewire so I thought I'd write it up here for the record.
    I never actually solved the problem, just started using USB-2 instead and the issues went away.
    --I had been getting pretty consistent kernel panics while doing backups or large file transfers to an external FW drive. I tried a few different drives and cables and the panics were consistent.
    --I also noticed a strange problem where graphic files I'd backed up (TIFF, JPEG, etc.) would have these single-pixel horizontal streaks running through them. This was a little disconcerting because it wasn't picked up during verification, it was just there when I opened the backup file.
    I found lots of people with FW problems in these forums but none mentioned that strange file corruption I got.
    I'll try FW again after a future system software upgrade but I'm giving up on it for now.

    I've been having consistent problems with Firewire since I got my Mac Pro last year. I only recently narrowed it down to Firewire so I thought I'd write it up here for the record.
    I never actually solved the problem, just started using USB-2 instead and the issues went away.
    --I had been getting pretty consistent kernel panics while doing backups or large file transfers to an external FW drive. I tried a few different drives and cables and the panics were consistent.
    --I also noticed a strange problem where graphic files I'd backed up (TIFF, JPEG, etc.) would have these single-pixel horizontal streaks running through them. This was a little disconcerting because it wasn't picked up during verification, it was just there when I opened the backup file.
    I found lots of people with FW problems in these forums but none mentioned that strange file corruption I got.
    I'll try FW again after a future system software upgrade but I'm giving up on it for now.

  • Aperture Kernel Panics & Fusion Disk Corruptions

    We have a  new iMac with the Fusion drive bought not to long ago. It has 16gb memory. Since it's back to school, we are busier than this past summer
    We are editing about 200 - 400 images a day. While in Aperture we have had kernel panics and a major spinning ball freezes with a total reboot freeze that ended up with  corruption on the Fusion drive.
    We have ask some tech people, and all have said, when working with large raw images, which we do, the drive cannot keep up with editing, esp when using the brush tool. Also missing files sometimes, like magic their gone.
    Anyone else have this.
    PS we have swaped out the memory 3 times and still had issues. I don't think the drive can handle the work.

    While I am runing a DIY Fusion Drive on a Mac Pro, I am a heavy user of Aperture and have noticed no problems what so ever with my current setup.
    It might be helpful if you canpost a crash dump from one of your kernel panics.
    Allan

  • End All Kernel Panic Troubleshooting List

    I have been tasked to put together an end all list to troubleshooting Kernel Panics. Please take a look at this list to verify if I missed any steps you would try.
    I understand that there will be specific fixes to specific causes, and not all of these would be used in any one situation. Also not yet listed in specific or correct order that troubleshooting should be done.
    Some list instructions on how to do the needed troubleshooting, some do not. This would be user specific, dependent on computer knowledge so I did not get into that yet.
    - Was a change just made, added ram, HD, card of any kind, software installed? Remove/uninstall and reboot.
    - Verify cables, connections and their proper installation and ensure that they are working properly.
    - Restart your computer.
    - Make sure that sufficient RAM and hard disk space is available for proper functioning of Mac.
    - Remove all peripherals down to monitor, keyboard and mouse.
    - Run Software Update.
    - System Scan with Tech Tool Deluxe.
    - Clean Cashes.
    - An incompatible login item could cause this symptom.
    - Selecting the "Connect automatically when starting TCP/IP applications" option in Network preferences can sometimes cause this issue.
    - open-source tool 'Rember'.
    - Reset certain privileges.
    - Remove fonts folder (10.3.9 and earlier).
    - Uninstall Any KEXTs To check the KEXTs that are running on your system currently, type this command in Terminal (Applications >> Terminal) and hit enter:sudo kextstat.
    - If particular app, delete Plists.
    - Verify & Repair Permissions.
    - App specific: Delete and reinstall app.
    - Apple Hardware Test.
    - Run FSCK Start up holding command and 's' to boot in single user mode. Type the following exactly as this with the spaces fsck -fy and then press the return key reset-nvram then press return, set-defaults then press return, reset-all then press return.
    - Start computer by pressing power button then holding down the Shift key.
    - Hold down the X key and choose Apple menu > Restart. This may force the computer to start up using your Mac OS X system. If the computer starts up, release the X key. Choose Apple menu> System Preferences, and then click Startup Disk. Make sure that the disk containing Mac OS X is selected.
    - Restart and immediately hold down the Option key. When icons start to appear in the center of the screen, release the Option key. Select the disk that contains Mac OS X, and then click the forward arrow to continue starting up.
    - Boot from the Install DVD. Restart holding down the C, does it boot?
    - Reset PRAM. Start computer by pressing power button and hold down Command Option P and R buttons at same time and hold until you have heard the start chimes 3 times, then release all buttons and let it boot up.
    - Hardware Test. Use the DVD that came with computer and press the power button and immediately insert the DVD and once it goes in hold the D key down. When it boots up hit return and then select which Hardware test you want to run, probably a good idea to do the extended test even though it may take an hour to an hour and a half to run through.
    - Reinstall Mac OS.
    - Erase and Install Mac OS X.
    - Contact Apple Inc.
    Message was edited by: iamtigg
    Message was edited by: iamtigg

    Why not instead visit The XLab FAQs and read the FAQ on diagnosing kernel panics. Additionally Apple provides a number of articles about kernel panics:
    About "You need to restart your computer" (kernel panic) messages
    Kernel Panics on Startup
    Mac OS X- "Broken folder" icon, prohibitory sign, or kernel panic when computer starts
    Mac OS X- How to log a kernel panic
    Technical Note TN2063- Understanding and Debugging Kernel Panics
    Tutorial - Avoiding and eliminating Kernel panic
    What's a "kernel panic"? (Mac OS X)
    You are just reinventing the wheel which is not really a good use of the forum.

  • Kernel panic - hard drive or corrupt journal system?

    Hi,
    My powerbook G4 shut down today with a kernel panic and now won't boot up (giving a kernel panic error after reaching the gray screen). The computer has been working fine, though the battery has run down, with the exception of not shutting down properly (I would have to power off manually). I tried various things to fix this (repair permissions, check hard drive, checking logs, etc.), but all those checked out and I could never get it figured out. I have been leaving the computer running because of this and it has been working fine. It is a stock G4 with no peripherals, except for a 1 GB RAM upgrade. The RAM was installed two years ago and tested strenuously with memtest with no issues.
    I did have my hard drive near full, as I didn't realize that this could case severe issues. It's probably too full to do a clean Archive and Install. My fault.
    I have reset my PMU/PRAM, but the computer won't boot up in safe mode or single-user mode. I get the following message at the end of single-user mode:
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007: root:xnu-792.24.17~1/RELEASE_PPC
    panic: We are hanging here ...
    Unfortunately, I do not have my backup disks with me right now, as I recently moved (I will have them in a couple weeks).
    There's some data on the computer it would be nice to pull off, but not absolutely essential. So my question is: Does this sound like a hard drive problem or a journal system/file system problem or something else? I hear no strange noises from the drive (the fan is a little noisy, though). What can I do at this point while I wait for my discs to arrive from across country?
    If this is a file problem, I have heard these are difficult to fix or even deal with in terms of data recovery, since the disk won't mount even in firewire target mode. Should I invest in a firewire external drive in order to create a bootable second drive? Purchase DiskWarrior? Create a bootable Linux CD? Any help would be appreciated!

    darksurtur:
    If you have the original HDD with which the computer was bought you likely have a failed HDD and should have it replaced with a newer, faster and large capacity HDD. The average life of an internal HDD is 3 to 5 years, and although it may not suddenly stop functioning after that performance gradually decreases until the drive fails completely.
    A too full drive can cause serious directory corruption which can in turn lead to data corruption and possible loss, and eventually a crash. You should maintain a minimum of 15% to total disk capacity (5 GB minimum on HDDs of 40 GB or less) as contiguous free space to allow for swap files and directory expansion.
    You should always maintain a current backup of everything you do not wish to lose as even a new HDD can fail suddenly. Using an external firewire drive and making a bootable clone using a utility like SuperDuper or Carbon Copy Cloner is an excellent way to accomplish this. Dr. Smoke's FAQ Backup and Recovery has excellent tips on backup strategies.
    Please do post back if you have further questions or comments.
    cornelius

  • My kernel panic log doesn't have kext list

    Usually kernel panic logs should contain list of kexts with their addresses, but my log have only the backtrace, but not the section starts with:
    "Kernel Extensions in backtrace (with dependencies):".
    It was exists few hours ago, but now its gone. Does it related to the value of "boot-args=debug=0x144"?
    Thanks!

    I think I found out the answer -
    The backtrace log shows no kext in addresses, only pure kernel...
    This make the debug much harder...

Maybe you are looking for

  • How do I change the highlight color?

    When I'm working on my document in Pages, I often do a Search (command-F) to quickly find a word or phrase that appears somewhere else in the document. It works great, but it highlights the word/phrase in light gray, which I have trouble seeing. Is t

  • How do I save my copy of Lion?

    Once I download my Lion update, how do I save it for future re-install? M

  • Ipod won't work after trying to install Paid 2.0 update

    I bought the 2.0 update for my 16 gig ipod touch. After trying to install the update through itunes half way through the update it gave me the message "The ipod could not be restored. An Unknown error occured (6)." I tried to do a restore on the ipod

  • Aironet 350 Series

    We just took over a site that has the 350 Series Ap's in place. I need to get into the AP and change the username and password... or at least set it back to default without killing the whole config.

  • Battery life under Snow Leopard

    Looks like I can only get maximum half the battery life, as compared to what it was under Leopard 10.5.8. I have the latest MacBook Pro 2009, and under Leopard I would normally get about 6-8 hours of battery life, and could get through an entire work