Devkit-disks-probe-ata-smart causes HSM Violations on SSD

I've just experienced the same problem identified on this Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+sour … mments=all.
It seems to be a general Linux kernel problem, and there are reports of it on Arch. Is a solution on the way?
My SSD started playing up, first exhibiting bad sector errors, then suddenly becoming read only as I was using it and finally refusing to mount when I booted complaining about a possible zero length partition. It also manifested the same problems described in this bug report when I booted up. Fortunately its the drive where I have my home partition, so its recoverable (not sure about the data in it, but there's nothing I can't afford to lose, even if I'd prefer not to).
I'm running Toofishes' patched eee kernel on an Asus 900. I'm fairly up to date (a week out at most). Is there a fix already in pacman, or do I try and apply this patch to my Arch system somehow? If so, how exactly. I'm okay with modifying the file, though I think its in a different place, but I'm a bit worried about it being overwritten by future updates.
Also, any ideas for recovering the drive, or restoring it. Writing 0s all over it seems a little drastic, and I'd prefer not to lose my home drive if I can.

Similar Messages

  • [K8T neo 754] S-ATA Smart under XP64

    Hello,
    I have a MSI K8T NEO FISR2 socket 754 mobo with a maxtor dm10 s-ata drive on the VIA controller. The OS is Windows XP x64.
    When I try to read out the SMART values of my harddrive, i cannot see these with a couple of progs (speedfan, everest). I also cant see the temperature of the drive.
    I already installed the latest driver for my VIA s-ata controller.
    As I can remember under XP32 it was possible to read these values (not 100% sure).
    Does anyone know there is a possibility to read out the smart values and drive temp under x64?

    hmz But i can remember when i had just bought this disk, i plugged it in on my winxp32 install on my old p-ata disk and speedfan detected a new harddisk. That's why i'm a little confused that it could be a win xp x64 problem.
    Or can all other people with this mainboard also not read out the smart values on any OS?

  • HARD DISK PROBS / TIME MACHINE not behaving with TC ? READ THIS!!!!

    I had many probs with the hard disk and now have a happy healthy TC working great with time machine, so I though I'd share my experiences with others hoping it will save you my huge pain !
    i,
    I've spent hours and hours trying to get the harddisk to work properly. Set-up was easy-peasy and the Airport works great for the internet. However, when trying to use time-machine and the hard disk it was a nightmare !!! Each attempt at the back-up failed after about 4 gig with a 'unable to mount volume' error. If I re-tried, it failed. Following some of the tips on the forums, I deleted the back-up file created by time machine on the hard drive and the initial back-up started successfully but failed after about 4 gig again (I had 96 gig to back-up). There are various fixes flying around -
    *_ensure you have a name for your computer - should be short and no spaces or funny characters. Same goes for your name of the timecapsule. Some people are saying you should use an ethernet cable for your first back-up but that should not matter at all.*_ I took mine back to the apple store in the end - a mac genius downloaded all the latest patches (only came out 19th march) for the time-capsule firmware, time machine software and airport express. Still didn't work, so conclusion was the time-capsule was knackered !!! SO MY RECOMMENDATION IS TO GET APPLE TO REPLACE IT BUT MAKE SURE YOU TRY THE ABOVE FIRST.
    New time-capsule was attached to my imac, started up great first time. My initial back-up ran through perfectly first time through wireless - it took 15 hours but I did have 96 gig to back-up. time machine sees this no problem so it looks like everything is fine. _*I ALSO NOTICED THAT THE TC WAS MUCH MORE QUIET AND LESS HOT.*_
    Good luck !!

    Hi,
    Well, The external drive you have problem with is from a third party vendor :-)
    I just looked up your model and we need to start over.

    How do you connect it to your computer?
    Is it plugged in to the router via ethernet and you access it over WiFi.
    The drive needs to be setup as per supplied instructions.
    The manufacturer says it is Time Machine compatible but from my experience I know this is not switched on by default.
    The main reason why you cannot access it is you basically have to set it up for your use and most likely authenticate to it.
    At this stage I'm quite sure there is no much wrong with that drive. It just need setting up.
    Let me know if you have any instructions from Seagate which you can follow.

  • Can Disk Utility get SMART status from external drives?

    I recently updated my backup plan with a NewerTech quad-interface dock and a WD Caviar Green hd. I'm using the FW800 interface to connect to my iMac (10.6.7) Everything works perfectly, as expected. I noticed, though, that Disk Utility cannot report the SMART status on the new WD drive. DU simply says "Not Supported" under SMART Status.
    Is Disk Utility telling me that it doesn't read SMART status from external drives? Or is it telling me that the new drive doesn't support SMART (which I would find highly unusual)? And, if it's Disk Utility that can't read the status, are there any third-party apps that can report the SMART status on an external drive?
    Thanks,
    JimC

    Unfortunately I cannot speak to the NewerTech enclosure, but in principle it appears to be possible to have SMART information displayed even for external drives if the enclosure's bridge controller chip allows it.
    My experience:
    I've used two MacPower Pleiades FW800/400/USB/eSATA enclosures for several years and I've now supplemented them with two additional inXtron enclosures. They all work as expected daisy-chained to the iMac.
    The interesting thing is that the inXtron enclosures came with a CD with some software on it ("Smart AP") which is not available for download, notably a Dashboard Widget for displaying actual and maximum temperatures, total hours of operation, start/stop cycles, drive model and serial number.
    This widget is complete garbage, though – it is a nauseating nightmare of extreme over-design at the expense of even basic usability:
    http://www.inxtron.com/information-center/smart-ap-for-external-hard-drives
    To make matters even worse, it can only display the above information for the first external drive connected.
    BUT: This Widget internally calls a command line utility which does the actual parameter retrieval, and that one can be called from the terminal as well.
    So after installing the software from CD and effectively discarding the Widget, I checked out the command line utility in the Terminal and found that this utility actually reported data about ALL my enclosures, both the inXtron and the MacPower ones (there seems to be firmware compatibility across these):
    (The '$' is supposed to be Terminal's bash prompt – type in only the rest of the respective line.)
    $ /Applications/MacpowerAP/GetSMART 1
    29 50 13 8
    53 67 645 15829
    52 53 90 7105
    51 52 18 13
    Each line reports the following for one connected enclosure:
    [temp] [maxtemp] [cycles] [hours]
    The drives are reported first USB, then FireWire drives, each in the order of first connection / mounting.
    $ /Applications/MacpowerAP/GetSMART 2
    WD-WCA**************
    WDC WD30EZRX-00MMMB0
    5TE09***************
    ST31000333AS-00MMMB0
    5TE09***************
    ST31000333AS-00MMMB0
    WD-WMA**************
    WDC WD30EZRS-00J99B0
    Each drive gets two lines reported, first the drive's serial number ("***" blocking out my exact ones), then the drive model.
    $ /Applications/MacpowerAP/GetSMART 3
    29 50 13 8
    WD-WCA**************
    WDC WD30EZRX-00MMMB0
    53 67 645 15829
    5TE09***************
    ST31000333AS-00MMMB0
    52 53 90 7105
    5TE09***************
    ST31000333AS-00MMMB0
    51 52 18 13
    WD-WMA**************
    WDC WD30EZRS-00J99B0
    This combines both of the above.
    $ /Applications/MacpowerAP/GetSMART 5
    disk4
    disk1
    disk2
    disk3
    This reports the mounted disk names (referring not to the volume names but to the internal Unix names as in /dev/[drive]); Numbering is in connection / mounting order, the actual sequence is as always USB drives, then FireWire drives.
    $ /Applications/MacpowerAP/GetSMART 6
    USB
    1394
    1394
    1394
    This reports the connection interface for each drive in the same sequence as all other commands.
    $ /Applications/MacpowerAP/GetSMART 7
    MPT934DS1.20.0104.00
    MPT934DS1.20.0104.00
    This might report the firmware revision or something like that.
    These are the commands I know about, and they apply only to the "Smart AP" software supplied with current inXtron enclosures, but it may be possible that other brands use it as well.
    I have not been able to identify information about the self-test (early(?) failure warning), but it might be contained as well in the data reported above.
    As always, your mileage may vary and you should never do such experiments without FIRST making sure you've got backups of your data and that such backup is not connected during experimentation!
    Maybe this can help some people getting the information they need; And maybe there are similar capabilities with other enclosures. At the very least it demonstrates that with the proper firmware in the enclosures themselves and some software on the Mac it IS possible to get at least some of the SMART information from the drive in an external FireWire- or USB-connected enclosure.
    None of that is fed into the system's "official" SMART mechanism, though, so no luck using standard mechanisms or applications for it. It's strictly a command-line affair (deservedly disregarding the mishappen Widget).
    Good luck!

  • Disk image system copy causes problems

    Hi
      Working with a client who chose to copy a PRD SAP ECC 6.0 system to a new box (as DEV) via a disk image copy. They renamed enough of the new SAP system to get it running but they still have problems.
    The command CHGR3SHLOC fails when the PRD box tries to create the mount to DEV. Also the source system name show up in the name of the default & instance profiles even when the old profiles are deleted and regenerated.
    I was wondering if anyone had a list of things to be changed when using a disk image to create a new SAP system.
    Personally I always do a normal install followed by a DB copy to create a DEV system from a PRD system.
    Thanks
    Matt

    Hi Matt,
    I'm sorry, but I never used DSPR3SYS or similar ... you udefinetely do not need to redo the copy, but you need to fix the root cause. As I do not know your issue, I cannot help you ...
    I would change the data area in r3sid400, the profiles and the /usr/sap/trans/config/SID ... (except the rest of my document)
    In crazy cases delete of the IFS stuff in /usr/sap & /sapmnt should help as well and then use crtr3sys and crtr3inst ...
    For more details, I need to check online ...
    Regards
    Volker Gueldenpfennig, consolut international ag
    http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

  • Disk utility says SMART error but Tech Tools Pro says SMART passed

    Disk Utility on my Mac Pro (6GB ram, dual dual, 10.5.5) is saying my primary HD (a Seagate 1TB, one of three) has failed SMART. Tech Tools pro says it's fine and passes SMART (and all the other tests). I've got backups (Time Machine and tar files) and a new disk on the way. However I'd like to be able to know what exactly Disk Utility thinks the SAMRT error is - is there any way of finding our or is it opaque to the user?

    If the drive is possible defective, then you may be able to have it replaced at no cost because it's in warranty. Most drives carry at least a 3 year manufacturer's warranty. You would contact the manufacturer about a warranty replacement if your Apple warranty has expired. If you still have Apple's warranty in effect then contact AppleCare about the replacement.

  • Crash with hard disk errors (ATA exception)

    My Arch just crashed displaying in a TTY errors like this:
    [ 24.229347] ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
    [ 24.229397] ata2.00: irq_stat 0x40000008
    [ 24.229426] ata2.00: failed command: READ FPDMA QUEUED
    [ 24.229463] ata2.00: cmd 60/08:00:70:3e:c3/00:00:03:00:00/40 tag 0 ncq 4096 in
    res 51/40:08:70:3e:c3/00:00:03:00:00/40 Emask 0x409 (media error) <F>
    [ 24.229552] ata2.00: status: { DRDY ERR }
    [ 24.229579] ata2.00: error: { UNC }
    [ 24.234145] ata2.00: configured for UDMA/133
    [ 24.234168] sd 1:0:0:0: [sda] Unhandled sense code
    [ 24.234171] sd 1:0:0:0: [sda]
    [ 24.234173] Result: hostbyte=0x00 driverbyte=0x08
    [ 24.234176] sd 1:0:0:0: [sda]
    [ 24.234177] Sense Key : 0x3 [current] [descriptor]
    [ 24.234181] Descriptor sense data with sense descriptors (in hex):
    [ 24.234183] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 24.234192] 03 c3 3e 70
    [ 24.234196] sd 1:0:0:0: [sda]
    [ 24.234198] ASC=0x11 ASCQ=0x4
    [ 24.234200] sd 1:0:0:0: [sda] CDB:
    [ 24.234202] cdb[0]=0x28: 28 00 03 c3 3e 70 00 00 08 00
    [ 24.234210] end_request: I/O error, dev sda, sector 63127152
    [ 24.234261] Buffer I/O error on device dm-1, logical block 7864270
    [ 24.234321] ata2: EH complete
    I shutdown the laptop by pressing the power button. On the reboot, a lot of these errors displayed but the system booted successfully. Here is the dmsg : http://pastebin.com/FAEAXwwY
    It is a 8 months old MSI GT70 laptop which never suffered from mechanical shocks in any way in the past.
    Should I get worried about this and start making — full — backups?

    The problem seems fixed now, at least I hope so.
    If the live CD did not booted this isn't because of the hard drive but of my NVIDIA Optimus config, adding “acpi=off” as kernel parameter fixed that.
    In the live CD I was able to open the LUKS volume, activate the LVM VG and mount the LV without any errors or visible problems (such as lags).
    Then I launched a “e2fsck -c -c” on the root LV (after unmouting it, of course); it reported 9 errors (9/0/0). I answered “yes” to all questions of e2fsck.
    I had the idea to regenerate the initramfs with mkinitcpio as I remembered I have canceled the last mkinitcpio during the process, maybe it generated a corrupted ramfs?
    After rebooting, everything worked normally. But I'm afraid I only have a reprieve, I will still clone my disk while it is still readable.
    Last edited by Nock441 (2013-12-27 17:59:12)

  • Why does inserting a disk (dvd or cd) cause my MacBook Pro to reboot?

    My MacBook Pro has developed a serious problem. Every time I insert a disk the screen goes black and computer reboots itself. And if I don't get the disk ejected immediately it will reboot again. Doesn't matter if it's a commercially purchased disk or blank media the computer will reboot.
    I've searched the forums and haven't seen this topic pop up anywhere.
    This means that I can no longer put my system disks in the drive.
    MacBook Pro 2.2GH 15"
    Matshita U-857 drive
    I plan on having a talk with an Apple rep on Monday about a replacement as the computer is only two months old and should no be acting like this.

    Have you tried the standard mac glitch fixes: permissions repair, Zap the PRAM, and SWC reset?

  • Update pwdChangedTime via ldapmodify causes "Constraint violation"

    Hi,
    we're migrating an application from IBM products (WebSphere+Tivoli DS) to Sun produdcts (SJSAS 9.0+SJSDS 6.0). I need to be able to change an entry's pwdChangedTime using the ldapmodify command.
    Running the following command
    ldapmodify -D "cn=Directory Manager" -v -f /tmp/change_pwdChangedTime.txt
    with the folloing /tmp/change_pwdChangedTime.txt file
    dn: cn=abc,ou=people,o=aaa,c=bbb
    changetype: modify
    replace: pwdChangedTime
    pwdChangedTime: 20070806082500Z
    gives me the following output
    ldap_init( localhost, 389 )
    replace pwdChangedTime:
    20070806082500Z
    modifying entry cn=abc,ou=people,o=aaa,c=bbb
    ldap_modify: Constraint violation
    ldap_modify: additional info: Constraint violation in modifications
    In Tivoli Directory Server I was able to use the command above using the "-k" option to be able to change the value of operational attributes like pwdChangedTime. Is there anywthing similar in SJSDS 6?
    Is there any other way to update this attribute manually when required but still have the server updating it when the password is changed by the user?
    Message was edited by:
    mcari

    We are trying to constrain applications from meddling with operational attributes due to the possibility of surprising behavior of the DSA as a result of an unanticipated value.
    In a lab environment, I would think it would be acceptable to remove the "read-only" restriction. Edit <instance_root>/config/schema/00ds6pwp.ldif and remove the constraint.
    We can consider adding a programmatic mechanism (e.g., an LDAP extended operation) in a future release to manage these operational attributes for testing and other administrative purposes. Could you let us know what other attributes you modify and to what ends?

  • HSlider causes security violation.

    I am pulling image urls from Google using their AS API, and I decided to add an HSlider. Currently the HSlider is just sitting there, with no peroperties set in its tag, but when you click on the slider thumbnail you get this error:
    SecurityDomain 'IMAGE_URL_IS_HERE' tried to access incompatible context 'file:///C:/ChikaraDev/src/flexapps/Showcase/MediaBrowser/bin-debug/MediaBrowser.html'
    *** Security Sandbox Violation ***
    So I'm wondering how an HSlider that literally is not doing anything results in these errors just by clicking its thumbnail.

    Is that all you get or is there a full stacktrace.  Unless you get the RTE dialog you can ignore the output
    Alex Harui
    Flex SDK Developer
    Adobe Systems Inc.
    Blog: http://blogs.adobe.com/aharui

  • IMovie'08 uploaded to YouTube with Jingles caused copyright violation notice

    I just uploaded an IMovie '08 project to YouTube with my own video content from my camcorder, and audio solely from IMovie Jingles. I received a 3rd party content notification from YouTube stating that the audio content is owned by an entity called "Dance All Day." Somebody please tell me why, when I tried to avoid copyright entanglements by using only Apple's IMovie jingles, am I getting 3rd party use violation notice from YouTube? Who the heck is "Dance all Day" and why are they claiming ownership of Apple IMovie "jingles"? Who owns the rights to IMovie "jingles?"

    Horse Feathers wrote:
    Still wondering who is "Dance all Day"
    A Google search revealed this German site:
    http://translate.google.com.au/translate?hl=en&sl=de&tl=en&u=http%3A%2F%2Fwww.da nce-all-day.com%2F
    I've had similar issues with these so-called copyright violations, simply when using Apple provided jingles in iMovie. Others here have also reported this. In my case it was a different entity that was claiming ownership of the jingles. After a while, the notices stopped appearing. YouTube place ads on the videos when there is a perceived violation, but these can be removed temporarily by clicking on the x icon. From memory, there was also a note stating that no action was required by the user, but ads would appear.
    John

  • Starting from a Snow leopard disk prob

    I just upgraded to Lion, I have another  startup disk that is bootable into 10.6 when  I changed the startup disk from Lion to SLeopard  I got the chime and the dreaded black "you must restart msg" I tried o to hold thenPwr button down got the chime again and the same problem.
    Any help.
    Rd

    Date/Time:      2011-12-12 18:24:12 -0500
    OS Version:      10.7.2 (Build 11C74)
    Architecture:    x86_64
    Report Version:  9
    Command:         No Target
    Path:            No Target
    Version:         ??? (???)
    Parent:          kernel_task [0]
    PID:             0
    Event:           shutdown stall
    Duration:        0.94s
    Steps:           10 (100ms sampling interval)
    Pageins:         4
    Pageouts:        0
    Process:         aksusbd [142]
    Path:            /usr/libexec/aksusbd
    Architecture:    i386
    UID:             0
      Thread 0x3ad      
    User stack:
        10__select_nocancel + 10 (in libsystem_kernel.dylib) [0x95706b5e]
      Kernel stack:
        10 wakeup + 1024 (in mach_kernel)[0x575a00]
      Thread 0x3b2        DispatchQueue 1701273966
      User stack:
        10 _dispatch_mgr_thread + 53 (inlibdispatch.dylib) [0x9c93b6a7]
         10 kevent + 10 (in libsystem_kernel.dylib) [0x9570790a]
      Kernel stack:
        10 kqueue_scan + 480 (in mach_kernel)[0x5596e0]
      Thread 0x3b0      
    User stack:
        10thread_start + 34 (in libsystem_c.dylib) [0x9c9bb6de]
          10 semaphore_wait_trap + 10 (inlibsystem_kernel.dylib) [0x95704c5e]
    Kernel stack:
        10semaphore_wait_continue + 0 (in mach_kernel) [0x234a50]
      Thread 0x3b1      
    User stack:
        10 ??? (inaksusbd) [0x639f]
          10 CFRunLoopRun+ 129 (in CoreFoundation) [0x9b4dd611]
            10 CFRunLoopRunSpecific + 332 (inCoreFoundation) [0x9b4cc8ec]
             10 __CFRunLoopRun + 1428 (in CoreFoundation) [0x9b4cd214]
                10 __CFRunLoopServiceMachPort + 170(in CoreFoundation) [0x9b4c40ea]
                  10 mach_msg_trap + 10 (inlibsystem_kernel.dylib) [0x95704c22]
    Kernel stack:
        10ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
      Binary Images:
          0x1000 -    0x11fcb aksusbd ??? (???) /usr/libexec/aksusbd
      0x956ee000 - 0x9570cff7  libsystem_kernel.dylib ??? (???)<124A6CE3-3934-3994-9D0A-E85A0C0BF082>/usr/lib/system/libsystem_kernel.dyl ib
    0x9b492000 - 0x9b668fe3 com.apple.CoreFoundation 6.7.1 (635.15)<AC9F6462-6315-3D89-8075-D048DB4DBF7E> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
      0x9c93a000 - 0x9c948fff  libdispatch.dylib ??? (???)<B50C62AD-0B5B-34C3-A491-ECFD72ED505E>/usr/lib/system/libdispatch.dylib
    0x9c95b000 - 0x9ca26fff libsystem_c.dylib ??? (???) <1B0A12B3-DAFA-31E2-8F82-E98D620E4D72>/usr/lib/system/libsystem_c.dylib
    Process:         dbfseventsd [392]
    Path:           /Library/DropboxHelperTools/*/dbfseventsd
    Architecture:    i386
    UID:             0
      Thread 0xb88      
    User stack:
      Kernel stack:
        2 lo_unix_scall + 279 (in mach_kernel)[0x2e4367]
          2 unix_syscall + 539(in mach_kernel) [0x5f0f2b]
            2read_nocancel + 163 (in mach_kernel) [0x585823]
              2 write + 256 (in mach_kernel)[0x585090]
                2 get_pathbuff+ 4047 (in mach_kernel) [0x33784f]
                  2 tsleep + 116 (in mach_kernel)[0x575cf4]
                    2 wakeup +685 (in mach_kernel) [0x5758ad]
                      2 thread_block + 33 (inmach_kernel) [0x22f771]
                       2 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
                          2 thread_continue + 1729(in mach_kernel) [0x22f3a1]
                            2machine_switch_context + 582 (in mach_kernel) [0x2cba26]
      Binary Images:
          0x1000 -     0x8ff7 dbfseventsd ??? (???) <6E6421C9-0E72-73AF-1821-754B84B964AF>/Library/DropboxHelperTools/*/dbfseventsd
    Process:         dbfseventsd [394]
    Path:           /Library/DropboxHelperTools/*/dbfseventsd
    Architecture:    i386
    UID:             0
      Thread 0xb8a      
    User stack:
        2 ??? (indbfseventsd) [0x8575]
          2__select_nocancel + 10 (in libsystem_kernel.dylib) [0x95706b5e]
      Kernel stack:
        2 wakeup + 1024 (in mach_kernel)[0x575a00]
      Binary Images:
          0x1000 -     0x8ff7 dbfseventsd ??? (???) <6E6421C9-0E72-73AF-1821-754B84B964AF>/Library/DropboxHelperTools/*/dbfseventsd
    0x956ee000 - 0x9570cff7 libsystem_kernel.dylib ??? (???)<124A6CE3-3934-3994-9D0A-E85A0C0BF082>/usr/lib/system/libsystem_kernel.dyl ib
    Process:         diskarbitrationd [13]
    Path:            /usr/sbin/diskarbitrationd
    Architecture:    x86_64
    UID:             0
      Thread 0x14c        DispatchQueue 1
      User stack:
        10 ??? (in diskarbitrationd)[0x10194439c]
          10 ??? (indiskarbitrationd) [0x10194ae15]
           10 CFRunLoopRun + 95 (in CoreFoundation) [0x7fff89e8c7ff]
              10 CFRunLoopRunSpecific + 230 (inCoreFoundation) [0x7fff89e7cae6]
               10 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff89e7d2d4]
                  10 __CFRunLoopServiceMachPort +188 (in CoreFoundation) [0x7fff89e74b6c]
                    10 mach_msg_trap + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7867a]
    Kernel stack:
        10ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
      Thread 0x151        DispatchQueue 2
      User stack:
        10 _dispatch_mgr_thread + 54 (inlibdispatch.dylib) [0x7fff8e91414e]
         10 kevent + 10 (in libsystem_kernel.dylib) [0x7fff8eb7a7e6]
      Kernel stack:
        10 kqueue_scan + 480 (in mach_kernel)[0x5596e0]
      Thread 0x6e2d     
    User stack:
        10start_wqthread + 13 (in libsystem_c.dylib) [0x7fff88bd3b85]
          10 __workq_kernreturn + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7a192]
    Kernel stack:
        10workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
      Thread 0x6e74     
    User stack:
        10start_wqthread + 13 (in libsystem_c.dylib) [0x7fff88bd3b85]
          10 __workq_kernreturn + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7a192]
    Kernel stack:
        10workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
      Binary Images:
             0x101943000 -        0x10195eff7  diskarbitrationd ??? (???)<F033F3D5-FF18-37D9-B9BF-59E6D4E30C10> /usr/sbin/diskarbitrationd
          0x7fff88b82000 -     0x7fff88c5ffef  libsystem_c.dylib ??? (???)<FF69F06E-0904-3C08-A5EF-536FAFFFDC22> /usr/lib/system/libsystem_c.dylib
          0x7fff89e44000 -     0x7fff8a018fff  com.apple.CoreFoundation 6.7.1 (635.15)<FE4A86C2-3599-3CF8-AD1A-822F1FEA820F>/System/Library/Frameworks/CoreFo undation.framework/Versions/A/CoreFoundation
          0x7fff8e912000 -     0x7fff8e920fff  libdispatch.dylib ??? (???)<712AAEAC-AD90-37F7-B71F-293FF8AE8723>/usr/lib/system/libdispatch.dylib
         0x7fff8eb63000 -    0x7fff8eb83fff libsystem_kernel.dylib ??? (???)<C56819BB-3779-3726-B610-4CF7B3ABB6F9> /usr/lib/system/libsystem_kernel.dylib
    Process:         DiskWarriorDaemon [263]
    Path:           /Applications/Utilities/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon
    Architecture:    i386
    UID:             501
      Thread 0x96a      
    User stack:
        10 ??? (inDiskWarriorDaemon) [0x1f61]
          10??? (in DiskWarriorDaemon) [0x203a]
           10 ??? (in DiskWarriorDaemon)[0x27a7]
              10 ??? (inDiskWarriorDaemon) [0xd85d]
               10 CFRunLoopRunInMode + 120 (in CoreFoundation) [0x9b4cc798]
                  10 CFRunLoopRunSpecific + 332 (inCoreFoundation) [0x9b4cc8ec]
                   10 __CFRunLoopRun + 1428 (inCoreFoundation) [0x9b4cd214]
                      10 __CFRunLoopServiceMachPort+ 170 (in CoreFoundation) [0x9b4c40ea]
                        10 mach_msg_trap + 10 (inlibsystem_kernel.dylib) [0x95704c22]
    Kernel stack:
        10 ipc_mqueue_receive_continue+ 0 (in mach_kernel) [0x215060]
    Thread 0x98a        DispatchQueue1701273966
      User stack:
        10 _dispatch_mgr_thread + 53 (inlibdispatch.dylib) [0x9c93b6a7]
         10 kevent + 10 (in libsystem_kernel.dylib) [0x9570790a]
      Kernel stack:
        10 kqueue_scan + 480 (in mach_kernel)[0x5596e0]
      Binary Images:
          0x1000 -    0x14fd7 DiskWarriorDaemon ??? (???)/Applications/Utilities/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon
      0x956ee000 - 0x9570cff7  libsystem_kernel.dylib ??? (???)<124A6CE3-3934-3994-9D0A-E85A0C0BF082>/usr/lib/system/libsystem_kernel.dyl ib
    0x9b492000 - 0x9b668fe3 com.apple.CoreFoundation 6.7.1 (635.15)<AC9F6462-6315-3D89-8075-D048DB4DBF7E>/System/Library/Frameworks/CoreFo undation.framework/Versions/A/CoreFoundation
      0x9c93a000 - 0x9c948fff  libdispatch.dylib ??? (???)<B50C62AD-0B5B-34C3-A491-ECFD72ED505E>/usr/lib/system/libdispatch.dylib
    Process:         launchd [1]
    Path:            /sbin/launchd
    Architecture:    unknown
    UID:             0
      Thread0x10a        DispatchQueue 1
      User stack:
        10 ??? [0x1099b625c]
          10 ??? [0x1099bbcaa]
            10 ??? [0x1099be33b]
              10 ??? [0x7fff8eb7867a]
      Kernel stack:
        10 ipc_mqueue_receive_continue + 0 (inmach_kernel) [0x215060]
      Thread0x136      
      User stack:
        10 ??? [0x7fff88bd3b75]
          10 ??? [0x7fff88bd08bf]
            10 ??? [0x7fff8eb79df2]
      Kernel stack:
        10 wakeup + 1024 (in mach_kernel)[0x575a00]
      Thread 0x137      
    User stack:
        10 ???[0x7fff88bd3b75]
          10 ???[0x7fff88bd08bf]
            10 ???[0x1099bbd6a]
              10 ???[0x7fff88b86c2c]
                10 ???[0x7fff8eb79e42]
      Kernel stack:
        10 semaphore_wait_continue + 0 (inmach_kernel) [0x234a50]
      BinaryImages:
    Process:        Router Manager [400]
    Path:           /Library/Application Support/Belkin/*/Router Manager
    Architecture:    i386
    UID:             501
      Thread 0xbd0      
    User stack:
        10 start + 41(in Router Manager) [0x2029]
          10_start + 209 (in Router Manager) [0x20fb]
            10 main + 877 (in Router Manager)[0x2b2b]
              10PluginPipe::~PluginPipe() + 35 (in Router Manager) [0x11c47]
                10 PluginPipe::stop() + 46 (inRouter Manager) [0x10fe2]
                 10 boost::thread::join() + 189 (in Router Manager) [0x42f1d]
                    10 pthread_cond_wait + 48 (inlibsystem_c.dylib) [0x9c96382a]
                      10 __psynch_cvwait + 10 (inlibsystem_kernel.dylib) [0x9570683e]
    Kernel stack:
        10lo_unix_scall + 279 (in mach_kernel) [0x2e4367]
          10 unix_syscall + 539 (in mach_kernel)[0x5f0f2b]
            10 psynch_cvwait +1967 (in mach_kernel) [0x5c38bf]
             10 ksyn_block_thread_locked + 77 (in mach_kernel) [0x5bed6d]
                10 thread_block + 33 (inmach_kernel) [0x22f771]
                 10 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
                    10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
                     10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
      Thread 0xbf7        DispatchQueue 1701273966
      User stack:
        10 _dispatch_mgr_thread + 53 (inlibdispatch.dylib) [0x9c93b6a7]
         10 kevent + 10 (in libsystem_kernel.dylib) [0x9570790a]
      Kernel stack:
        10 kqueue_scan + 480 (in mach_kernel)[0x5596e0]
      Thread 0xc1c      
    User stack:
        10 thread_start+ 34 (in libsystem_c.dylib) [0x9c9bb6de]
          10 _pthread_start + 335 (inlibsystem_c.dylib) [0x9c9b7ed9]
           10 __select + 10 (in libsystem_kernel.dylib) [0x95706b42]
      Kernel stack:
        10 wakeup + 1024 (in mach_kernel)[0x575a00]
      Thread 0xc40      
    User stack:
        10thread_start + 34 (in libsystem_c.dylib) [0x9c9bb6de]
          10 _pthread_start + 335 (inlibsystem_c.dylib) [0x9c9b7ed9]
           10 thread_proxy + 141 (in Router Manager) [0x426cd]
              10 boost::_bi::bind_t<void,boost::_mfi::mf0<void, PluginPipe>,boost::_bi::list1<boost::_bi::value<PluginPipe*> >>::operator()() + 43 (in Router Manager) [0x173b5]
                10 PluginPipe::run() + 20 (inRouter Manager) [0x11058]
                 10 XmlClient::run() + 489 (in Router Manager) [0x41e1]
                    10 boolboost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex>> (boost::unique_lock<boost::mutex>&, boost::xtime const&) + 48(in Router Manager) [0x9d42]
                      10 boolboost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex>> (boost::unique_lock<boost::mutex>&, boost::posix_time::ptimeconst&) + 91 (in Router Manager) [0x9c87]
                        10 pthread_cond_timedwait +47 (in libsystem_c.dylib) [0x9c9637f5]
                          10 __psynch_cvwait + 10 (inlibsystem_kernel.dylib) [0x9570683e]
    Kernel stack:
        10lo_unix_scall + 279 (in mach_kernel) [0x2e4367]
          10 unix_syscall + 539 (in mach_kernel)[0x5f0f2b]
            10 psynch_cvwait +1967 (in mach_kernel) [0x5c38bf]
              10 ksyn_block_thread_locked + 77 (inmach_kernel) [0x5bed6d]
               10 thread_block + 33 (in mach_kernel) [0x22f771]
                  10 thread_block_reason + 331 (inmach_kernel) [0x22f62b]
                   10 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
                      10 machine_switch_context +582 (in mach_kernel) [0x2cba26]
    Thread 0xc41      
      User stack:
        10 thread_start + 34 (in libsystem_c.dylib)[0x9c9bb6de]
          10 _pthread_start+ 335 (in libsystem_c.dylib) [0x9c9b7ed9]
            10 thread_proxy + 141 (in RouterManager) [0x426cd]
              10boost::_bi::bind_t<void, boost::_mfi::mf0<void, PluginPipe>,boost::_bi::list1<boost::_bi::value<PluginPipe*> >>::operator()() + 43 (in Router Manager) [0x173b5]
                10 PluginPipe::PowerNotificatoinCallbackRunLoop()+ 134 (in Router Manager) [0x111e2]
                  10 CFRunLoopRun + 129 (inCoreFoundation) [0x9b4dd611]
                   10 CFRunLoopRunSpecific + 332 (in CoreFoundation) [0x9b4cc8ec]
                      10 __CFRunLoopRun + 1428 (inCoreFoundation) [0x9b4cd214]
                        10__CFRunLoopServiceMachPort + 170 (in CoreFoundation) [0x9b4c40ea]
                          10 mach_msg_trap + 10 (inlibsystem_kernel.dylib) [0x95704c22]
    Kernel stack:
        10ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
      Thread 0x6eaa     
    User stack:
        10start_wqthread + 30 (in libsystem_c.dylib) [0x9c9bb6fe]
          10 __workq_kernreturn + 10 (inlibsystem_kernel.dylib) [0x9570702e]
    Kernel stack:
        10workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
      Thread 0x6f04     
    User stack:
      Kernelstack:
        10 workqueue_exit + 1232(in mach_kernel) [0x5c5ea0]
    Binary Images:
          0x1000-   0x126fff  com.Affinegy.Router_Manager Router Manager4.0.0 ¬© 2009 Affinegy, Inc. (4.0.0)<9F5F3D7F-0354-4DC7-0400-D5059481A68C> /Library/ApplicationSupport/Belkin/*/Router Manager
    0x956ee000 - 0x9570cff7 libsystem_kernel.dylib ??? (???)<124A6CE3-3934-3994-9D0A-E85A0C0BF082>/usr/lib/system/libsystem_kernel.dyl ib
    0x9b492000 - 0x9b668fe3 com.apple.CoreFoundation 6.7.1 (635.15)<AC9F6462-6315-3D89-8075-D048DB4DBF7E>/System/Library/Frameworks/CoreFo undation.framework/Versions/A/CoreFoundation
      0x9c93a000 - 0x9c948fff  libdispatch.dylib ??? (???)<B50C62AD-0B5B-34C3-A491-ECFD72ED505E>/usr/lib/system/libdispatch.dylib
    0x9c95b000 - 0x9ca26fff libsystem_c.dylib ??? (???) <1B0A12B3-DAFA-31E2-8F82-E98D620E4D72>/usr/lib/system/libsystem_c.dylib
    Process:         securityd [27]
    Path:            /usr/sbin/securityd
    Architecture:    x86_64
    UID:             0
      Thread 0x15f        DispatchQueue 1
      User stack:
        10 start + 52 (in securityd)[0x100b428f4]
          10 main + 2179(in securityd) [0x100b58df4]
           10 Security::MachPlusPlus::MachServer::run(unsigned long, int) + 103 (insecurityd) [0x100b95b1b]
              10Security::MachPlusPlus::MachServer::runServerThread(bool) + 676 (in securityd)[0x100b2e0e2]
                10mach_msg_overwrite_trap + 10 (in libsystem_kernel.dylib) [0x7fff8eb78686]
      Kernel stack:
        10 ipc_mqueue_receive_continue + 0 (inmach_kernel) [0x215060]
      Thread0x212        DispatchQueue 2
      User stack:
        10 _dispatch_mgr_thread + 54 (inlibdispatch.dylib) [0x7fff8e91414e]
         10 kevent + 10 (in libsystem_kernel.dylib) [0x7fff8eb7a7e6]
      Kernel stack:
        10 kqueue_scan + 480 (in mach_kernel)[0x5596e0]
      Thread 0x19f      
    User stack:
        10thread_start + 13 (in libsystem_c.dylib) [0x7fff88bd3b75]
          10 _pthread_start + 335 (inlibsystem_c.dylib) [0x7fff88bd08bf]
           10 Security::Thread::runner(void*) + 104 (in securityd)[0x100b2dbda]
              10AuditMonitor::action() + 97 (in securityd) [0x100b79153]
                10 au_sdev_read_aia + 79 (inlibbsm.0.dylib) [0x7fff85d5d091]
                  10 fgetc + 50 (inlibsystem_c.dylib) [0x7fff88bb8dee]
                    10 __srget + 20 (inlibsystem_c.dylib) [0x7fff88c185e8]
                      10 __srefill1 + 30 (inlibsystem_c.dylib) [0x7fff88bcd166]
                        10 __read_nocancel + 10 (inlibsystem_kernel.dylib) [0x7fff8eb79d52]
    Kernel stack:
        10lo64_unix_scall + 23 (in mach_kernel) [0x2e4977]
          10 unix_syscall64 + 554 (in mach_kernel)[0x5f15fa]
            10 read_nocancel +163 (in mach_kernel) [0x585823]
             10 write + 256 (in mach_kernel) [0x585090]
                10 utf8_encodelen + 4080 (inmach_kernel) [0x3201b0]
                 10 VNOP_READ + 82 (in mach_kernel) [0x32a782]
                    10 spec_read + 110 (inmach_kernel) [0x33cd7e]
                     10 audit_session_setaia + 2388 (in mach_kernel) [0x5426d4]
                        10 _audit_cv_wait_sig + 50 (inmach_kernel) [0x5354c2]
                          10 msleep + 165 (inmach_kernel) [0x575e25]
                            10 wakeup + 287 (inmach_kernel) [0x57571f]
                              10 lck_mtx_sleep + 79(in mach_kernel) [0x227bcf]
                                10 thread_block +33 (in mach_kernel) [0x22f771]
                                  10thread_block_reason + 331 (in mach_kernel) [0x22f62b]
                                    10thread_continue + 1729 (in mach_kernel) [0x22f3a1]
                                      10machine_switch_context + 582 (in mach_kernel) [0x2cba26]
      Thread 0x6a63     
    User stack:
        10thread_start + 13 (in libsystem_c.dylib) [0x7fff88bd3b75]
          10 _pthread_start + 335 (inlibsystem_c.dylib) [0x7fff88bd08bf]
           10 Security::Thread::runner(void*) + 104 (in securityd)[0x100b2dbda]
              10Security::MachPlusPlus::MachServer::LoadThread::action() + 48 (in securityd)[0x100b2dc7c]
                10Security::MachPlusPlus::MachServer::runServerThread(bool) + 676 (in securityd)[0x100b2e0e2]
                  10mach_msg_overwrite_trap + 10 (in libsystem_kernel.dylib) [0x7fff8eb78686]
      Kernel stack:
        10 ipc_mqueue_receive_continue + 0 (inmach_kernel) [0x215060]
      Thread0x6bd4     
      User stack:
        10 thread_start + 13 (in libsystem_c.dylib)[0x7fff88bd3b75]
          10_pthread_start + 335 (in libsystem_c.dylib) [0x7fff88bd08bf]
            10 Security::Thread::runner(void*) +104 (in securityd) [0x100b2dbda]
             10 Security::MachPlusPlus::MachServer::LoadThread::action() + 48 (insecurityd) [0x100b2dc7c]
               10 Security::MachPlusPlus::MachServer::runServerThread(bool) + 676 (insecurityd) [0x100b2e0e2]
                 10 mach_msg_overwrite_trap + 10 (in libsystem_kernel.dylib) [0x7fff8eb78686]
      Kernel stack:
        10 ipc_mqueue_receive_continue + 0 (inmach_kernel) [0x215060]
      Thread0x6f01     
      User stack:
        10 start_wqthread + 13 (inlibsystem_c.dylib) [0x7fff88bd3b85]
         10 __workq_kernreturn + 10 (in libsystem_kernel.dylib)[0x7fff8eb7a192]
      Kernel stack:
        10 workqueue_exit + 1808 (in mach_kernel)[0x5c60e0]
      Thread 0x6f08     
    User stack:
      Kernelstack:
        10 workqueue_exit + 1232(in mach_kernel) [0x5c5ea0]
    Binary Images:
            0x100b1f000 -        0x100c09fff  securityd ??? (???)<B750B226-98DB-39E9-A3E5-14B8D36882D7> /usr/sbin/securityd
          0x7fff85d50000 -     0x7fff85d62ff7  libbsm.0.dylib ??? (???)<349BB16F-75FA-363F-8D98-7A9C3FA90A0D> /usr/lib/libbsm.0.dylib
          0x7fff88b82000 -     0x7fff88c5ffef  libsystem_c.dylib ??? (???)<FF69F06E-0904-3C08-A5EF-536FAFFFDC22>/usr/lib/system/libsystem_c.dylib
         0x7fff8e912000 -    0x7fff8e920fff  libdispatch.dylib??? (???) <712AAEAC-AD90-37F7-B71F-293FF8AE8723> /usr/lib/system/libdispatch.dylib
          0x7fff8eb63000 -     0x7fff8eb83fff  libsystem_kernel.dylib ??? (???)<C56819BB-3779-3726-B610-4CF7B3ABB6F9> /usr/lib/system/libsystem_kernel.dylib
    Process:         spindump [1942]
    Path:            /usr/sbin/spindump
    Architecture:    x86_64
    UID:             0
      Thread 0x6ef4     
    User stack:
        10 ??? (inspindump) [0x10215b814]
          10 ???(in spindump) [0x10215c4b2]
           10 dispatch_main + 43 (in libdispatch.dylib) [0x7fff8e914c20]
              10 pthread_exit + 30 (inlibsystem_c.dylib) [0x7fff88bd227d]
                10 _pthread_exit + 142 (inlibsystem_c.dylib) [0x7fff88bd1f7c]
                  10 _pthread_tsd_cleanup + 230 (inlibsystem_c.dylib) [0x7fff88c16942]
                    10 _dispatch_queue_cleanup2 +88 (in libdispatch.dylib) [0x7fff8e91686d]
                      10 sleep$NOCANCEL + 61 (inlibsystem_c.dylib) [0x7fff88c23ae5]
                        10__semwait_signal_nocancel + 10 (in libsystem_kernel.dylib)[0x7fff8eb79e56]
      Kernel stack:
        10 semaphore_wait_continue + 0 (inmach_kernel) [0x234a50]
      Thread0x6f15       DispatchQueue 2
      User stack:
        10 _dispatch_mgr_thread + 54 (inlibdispatch.dylib) [0x7fff8e91414e]
         10 kevent + 10 (in libsystem_kernel.dylib) [0x7fff8eb7a7e6]
      Kernel stack:
        9 lo64_unix_scall + 23 (in mach_kernel)[0x2e4977]
          9 unix_syscall64 +554 (in mach_kernel) [0x5f15fa]
           9 kevent + 114 (in mach_kernel) [0x55b112]
              9 kevent_description + 1875 (inmach_kernel) [0x55af63]
                9kqueue_scan + 228 (in mach_kernel) [0x5595e4]
                  9 thread_block_parameter + 32 (inmach_kernel) [0x22f740]
                   9 thread_block_reason + 306 (in mach_kernel) [0x22f612]
                      9 thread_cancel_timer + 640(in mach_kernel) [0x22e110]
                        9 processor_idle + 181 (inmach_kernel) [0x22d335]
                          9 machine_idle + 206 (inmach_kernel) [0x2cfbce]
        1kqueue_scan + 480 (in mach_kernel) [0x5596e0]
      Thread 0x6f16       DispatchQueue 6
      User stack:
        10 _dispatch_sig_thread + 45 (inlibdispatch.dylib) [0x7fff8e916954]
         10 __sigsuspend_nocancel + 10 (in libsystem_kernel.dylib)[0x7fff8eb7a022]
      Kernel stack:
        10 wakeup + 1024 (in mach_kernel)[0x575a00]
      Thread<multiple> DispatchQueue 18
    User stack:
        10start_wqthread + 13 (in libsystem_c.dylib) [0x7fff88bd3b85]
          10 _pthread_wqthread + 316 (inlibsystem_c.dylib) [0x7fff88bd23da]
           10 _dispatch_worker_thread2 + 198 (in libdispatch.dylib)[0x7fff8e914760]
              10_dispatch_queue_invoke + 54 (in libdispatch.dylib) [0x7fff8e914f66]
                10 _dispatch_queue_drain + 210 (inlibdispatch.dylib) [0x7fff8e9150d4]
                  10 _dispatch_queue_invoke + 71(in libdispatch.dylib) [0x7fff8e914f77]
                    10 _dispatch_source_invoke +635 (in libdispatch.dylib) [0x7fff8e9182b6]
                      10 __syscall + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7a09a]
    Kernel stack:
        10lo64_unix_scall + 23 (in mach_kernel) [0x2e4977]
          10 unix_syscall64 + 554 (in mach_kernel)[0x5f15fa]
            10 stack_snapshot+ 104 (in mach_kernel) [0x545698]
             10 stack_snapshot2 + 160 (in mach_kernel) [0x545580]
      Thread 0x6f28     
    User stack:
        10start_wqthread + 13 (in libsystem_c.dylib) [0x7fff88bd3b85]
          10 __workq_kernreturn + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7a192]
    Kernel stack:
        10workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
      Thread 0x6f29     
    User stack:
        10start_wqthread + 13 (in libsystem_c.dylib) [0x7fff88bd3b85]
          10 __workq_kernreturn + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7a192]
    Kernel stack:
        10workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
      Thread 0x6f14       DispatchQueue 13
      User stack:
        8 start_wqthread + 13 (inlibsystem_c.dylib) [0x7fff88bd3b85]
         8 _pthread_wqthread + 316 (in libsystem_c.dylib) [0x7fff88bd23da]
            8 _dispatch_worker_thread2 + 198 (inlibdispatch.dylib) [0x7fff8e914760]
              8 _dispatch_queue_invoke + 54 (inlibdispatch.dylib) [0x7fff8e914f66]
                8 _dispatch_queue_drain + 264 (inlibdispatch.dylib) [0x7fff8e91510a]
                  8_dispatch_call_block_and_release + 18 (in libdispatch.dylib)[0x7fff8e9138ba]
                    8??? (in spindump) [0x1021615a8]
                      8 ??? (in spindump)[0x102160723]
                        8??? (in spindump) [0x102161961]
                          8_dispatch_barrier_sync_f_invoke + 33 (in libdispatch.dylib)[0x7fff8e915aad]
                           8 ??? (in spindump) [0x102161b0d]
                              8CSSymbolicatorCreateWithPidFlagsAndNotification + 84 (in CoreSymbolication)[0x7fff8ec67945]
                               8 CSCppMachTask::symbol_owners(bool, unsigned int) + 90 (inCoreSymbolication) [0x7fff8ec3aa8e]
                                  8CSCppDyld::symbol_owner(CSCppMachTaskContainer const&, unsigned long long, bool,unsigned int) + 62 (in CoreSymbolication) [0x7fff8ec3abd2]
                                    8CSCppTaskMemory::CSCppTaskMemory(CSCppMachTaskContainer const&, bool) + 101(in CoreSymbolication) [0x7fff8ec3adf9]
                                      8 task_suspend+ 71 (in libsystem_kernel.dylib) [0x7fff8eb72c3e]
                                        8mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8eb7867a]
      Kernel stack:
        8 lo64_mach_scall + 23 (in mach_kernel)[0x2e4997]
          8 thread_set_child +407 (in mach_kernel) [0x2b7307]
           8 mach_msg_overwrite_trap + 219 (in mach_kernel) [0x21b1cb]
              8 ipc_kmsg_send + 83 (in mach_kernel)[0x213fd3]
                8ipc_kobject_server + 310 (in mach_kernel) [0x222d06]
                  8 task_server_routine + 3156 (inmach_kernel) [0x25d374]
                   8 task_suspend + 204 (in mach_kernel) [0x237bdc]
                      8 thread_wait + 349 (inmach_kernel) [0x2303ad]
                       8 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
                          8 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
                            8machine_switch_context + 582 (in mach_kernel) [0x2cba26]
      Thread 0x6f2b     
    User stack:
        2 thread_start+ 13 (in libsystem_c.dylib) [0x7fff88bd3b75]
          2_pthread_start + 335 (in libsystem_c.dylib) [0x7fff88bd08bf]
            2 cleaner_thread_main(void*) + 36 (inCoreSymbolication) [0x7fff8ec56f63]
              2 __semwait_signal + 10 (inlibsystem_kernel.dylib) [0x7fff8eb79e42]
    Kernel stack:
        2 semaphore_wait_continue+ 0 (in mach_kernel) [0x234a50]
    Thread 0x6f14     
      User stack:
        1 start_wqthread + 13 (inlibsystem_c.dylib) [0x7fff88bd3b85]
         1 __workq_kernreturn + 10 (in libsystem_kernel.dylib)[0x7fff8eb7a192]
      Kernel stack:
        1 lo64_unix_scall + 23 (in mach_kernel)[0x2e4977]
          1 unix_syscall64 +554 (in mach_kernel) [0x5f15fa]
           1 workq_kernreturn + 676 (in mach_kernel) [0x5c7304]
              1 workqueue_exit + 5758 (inmach_kernel) [0x5c704e]
                1thread_block + 33 (in mach_kernel) [0x22f771]
                  1 thread_block_reason + 306 (inmach_kernel) [0x22f612]
                   1 thread_cancel_timer + 640 (in mach_kernel) [0x22e110]
                      1 processor_idle + 181 (inmach_kernel) [0x22d335]
                       1 machine_idle + 206 (inmach_kernel) [0x2cfbce]
      Thread0x6f27     
      User stack:
        1 start_wqthread + 13 (inlibsystem_c.dylib) [0x7fff88bd3b85]
         1 __workq_kernreturn + 10 (in libsystem_kernel.dylib)[0x7fff8eb7a192]
      Kernel stack:
        1 workqueue_exit + 1808 (in mach_kernel)[0x5c60e0]
      Binary Images:
             0x10215a000 -        0x102170ff7  spindump ??? (???)<B568C435-488D-3705-8058-83F62AD2258A> /usr/sbin/spindump
          0x7fff88b82000 -     0x7fff88c5ffef  libsystem_c.dylib ??? (???)<FF69F06E-0904-3C08-A5EF-536FAFFFDC22>/usr/lib/system/libsystem_c.dylib
         0x7fff8e912000 -    0x7fff8e920fff  libdispatch.dylib??? (???) <712AAEAC-AD90-37F7-B71F-293FF8AE8723> /usr/lib/system/libdispatch.dylib
          0x7fff8eb63000 -     0x7fff8eb83fff  libsystem_kernel.dylib ??? (???)<C56819BB-3779-3726-B610-4CF7B3ABB6F9>/usr/lib/system/libsystem_kernel.dyl ib
         0x7fff8ec39000 -    0x7fff8eca7fff com.apple.CoreSymbolication 2.1 (66)<7CF9EF4A-262A-3009-8D42-A76F5614E372> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSy mbolication
    Process:         umount [1936]
    Path:            /sbin/umount
    Architecture:    x86_64
    UID:             0
      Thread 0x6ed2       DispatchQueue 1
      User stack:
        10 ??? (in umount) [0x106ce77f8]
          10 ??? (in umount) [0x106ce7bc2]
            10 unmount + 10 (inlibsystem_kernel.dylib) [0x7fff8eb7af66]
    Kernel stack:
        10lo64_unix_scall + 23 (in mach_kernel) [0x2e4977]
          10 unix_syscall64 + 554 (in mach_kernel)[0x5f15fa]
            10 unmount + 251(in mach_kernel) [0x31ba2b]
             10 safedounmount + 159 (in mach_kernel) [0x31b8af]
                10 dounmount + 356 (in mach_kernel)[0x31b534]
                  9 vflush +819 (in mach_kernel) [0x30c633]
                    9 vnode_rele_internal + 895 (inmach_kernel) [0x30adaf]
                     5 vnode_rele_ext + 391 (in mach_kernel) [0x30b127]
                        5 ubc_msync + 227 (inmach_kernel) [0x591fc3]
                          4memory_object_lock_request + 220 (in mach_kernel) [0x26afac]
                            2memory_object_lock_page + 4723 (in mach_kernel) [0x26aba3]
                              1 vm_page_lookup +229 (in mach_kernel) [0x297695]
                              1 vm_page_lookup +206 (in mach_kernel) [0x29767e]
                                1 hw_lock_to + 28 (in mach_kernel)[0x2bb9ec]
                            1memory_object_lock_page + 2878 (in mach_kernel) [0x26a46e]
                            1memory_object_lock_page + 4760 (in mach_kernel) [0x26abc8]
                          1 memory_object_lock_request+ 64 (in mach_kernel) [0x26af10]
                            1 lck_rw_lock_exclusive+ 6 (in mach_kernel) [0x2bbcc6]
                      4 vnode_rele_ext + 504 (inmach_kernel) [0x30b198]
                       4 ubc_page_op + 418 (in mach_kernel) [0x591db2]
                          4 memory_object_destroy +40 (in mach_kernel) [0x2698d8]
                            4 vm_object_page_grab +4912 (in mach_kernel) [0x289830]
                  1 vflush + 881 (in mach_kernel)[0x30c671]
                    1 vfs_iterate+ 505 (in mach_kernel) [0x307fc9]
                      1 vnode_list_lock + 19 (inmach_kernel) [0x300c23]
                       1 usimple_lock + 29 (in mach_kernel) [0x2c457d]
      Binary Images:
             0x106ce7000 -        0x106ce8fff  umount ??? (???)<0ED0E540-9302-3EC7-9B6B-B2233A6F074A> /sbin/umount
          0x7fff8eb63000 -     0x7fff8eb83fff  libsystem_kernel.dylib ??? (???)<C56819BB-3779-3726-B610-4CF7B3ABB6F9> /usr/lib/system/libsystem_kernel.dylib
    Process:         kernel_task [0]
    Path:            kernel_task
    Architecture:    i386
    UID:             0
    Version:         Darwin Kernel Version 11.2.0: TueAug  9 20:56:15 PDT 2011;root:xnu-1699.24.8~1/RELEASE_I386
    Thread 0x1        
      Kernel stack:
        10 vm_pageout_continue + 0 (in mach_kernel)[0x295f20]
      Thread 0x2        
    Kernel stack:
        10idle_thread + 0 (in mach_kernel) [0x22cc30]
      Thread 0x3        
    Kernel stack:
        9assert_wait_deadline + 384 (in mach_kernel) [0x22fd60]
        1 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
          1assert_wait_deadline + 1045 (in mach_kernel) [0x22fff5]
            1 thread_block_reason + 306 (inmach_kernel) [0x22f612]
              1thread_cancel_timer + 640 (in mach_kernel) [0x22e110]
                1 processor_idle + 181 (inmach_kernel) [0x22d335]
                 1 machine_idle + 206 (in mach_kernel) [0x2cfbce]
      Thread 0x4        
    Kernel stack:
        10thread_daemon_init + 288 (in mach_kernel) [0x23bc30]
      Thread 0x5        
    Kernel stack:
        10thread_create + 32 (in mach_kernel) [0x23b6e0]
      Thread 0x6        
    Kernel stack:
        10thread_call_func + 480 (in mach_kernel) [0x23e1f0]
      Thread 0x7        
    Kernel stack:
        10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
          10 mapping_replenish + 394 (inmach_kernel) [0x2b684a]
            10thread_block + 33 (in mach_kernel) [0x22f771]
              10 thread_block_reason + 331 (inmach_kernel) [0x22f62b]
               10 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
                  10 machine_switch_context + 582(in mach_kernel) [0x2cba26]
    Thread 0x8        
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0xa        
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0xc        
      Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x1a       
    Kernel stack:
        10thread_call_func + 752 (in mach_kernel) [0x23e300]
      Thread 0x1b       
    Kernel stack:
        10 wakeup +1024 (in mach_kernel) [0x575a00]
    Thread 0x1d       
      Kernel stack:
        10 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
          10AppleIntelCPUPowerManagement::~AppleIntelCPUPowerManagement() + 23470 (inAppleIntelCPUPowerManagement) [0x1efbe80]
            10 IOLockSleep + 39 (in mach_kernel)[0x63f2a7]
              10 lck_mtx_sleep+ 79 (in mach_kernel) [0x227bcf]
               10 thread_block + 33 (in mach_kernel) [0x22f771]
                  10 thread_block_reason + 331 (inmach_kernel) [0x22f62b]
                   10 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
                      10 machine_switch_context +582 (in mach_kernel) [0x2cba26]
    Thread 0x20       
      Kernel stack:
        10 idle_thread + 0 (in mach_kernel)[0x22cc30]
      Thread 0x23       
    Kernel stack:
        9idle_thread + 0 (in mach_kernel) [0x22cc30]
        1 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
          1 idle_thread + 30(in mach_kernel) [0x22cc4e]
            1processor_idle + 181 (in mach_kernel) [0x22d335]
              1 machine_idle + 206 (in mach_kernel)[0x2cfbce]
      Thread 0x26       
    Kernel stack:
        5idle_thread + 0 (in mach_kernel) [0x22cc30]
        5 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
          5 idle_thread + 30(in mach_kernel) [0x22cc4e]
            5processor_idle + 181 (in mach_kernel) [0x22d335]
              5 machine_idle + 206 (in mach_kernel)[0x2cfbce]
      Thread 0x2b       
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x65       
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x6d       
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x6e       
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x6f       
    Kernel stack:
        10 IOWorkLoop::threadMain()+ 0 (in mach_kernel) [0x6607d8]
    Thread 0x71       
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0x82       
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0x85       
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0x86       
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0x89       
      Kernel stack:
        9 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
        1call_continuation + 28 (in mach_kernel) [0x2c6d0c]
          1 IOWorkLoop::threadMain() + 97 (inmach_kernel) [0x660839]
            1thread_block_parameter + 32 (in mach_kernel) [0x22f740]
              1 thread_block_reason + 306 (inmach_kernel) [0x22f612]
                1thread_cancel_timer + 640 (in mach_kernel) [0x22e110]
                  1 processor_idle + 181 (inmach_kernel) [0x22d335]
                   1 machine_idle + 206 (in mach_kernel) [0x2cfbce]
      Thread0x8b       
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0x8c       
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0x9f       
      Kernel stack:
        10 m_prepend_2 + 23184 (in mach_kernel)[0x59d400]
      Thread 0xa0       
    Kernel stack:
        10audit_worker_init + 80 (in mach_kernel) [0x544380]
      Thread 0xa1       
    Kernel stack:
        10get_aiotask + 144 (in mach_kernel) [0x549010]
      Thread 0xa2       
    Kernel stack:
        10get_aiotask + 144 (in mach_kernel) [0x549010]
      Thread 0xa3       
    Kernel stack:
        10get_aiotask + 144 (in mach_kernel) [0x549010]
      Thread 0xa4       
    Kernel stack:
        10get_aiotask + 144 (in mach_kernel) [0x549010]
      Thread 0xa5       
    Kernel stack:
        10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
          10 dlil_if_ref + 3518 (in mach_kernel)[0x3551de]
            10 msleep + 165(in mach_kernel) [0x575e25]
             10 wakeup + 287 (in mach_kernel) [0x57571f]
                10 lck_mtx_sleep + 79 (inmach_kernel) [0x227bcf]
                 10 thread_block + 33 (in mach_kernel) [0x22f771]
                    10 thread_block_reason + 331(in mach_kernel) [0x22f62b]
                      10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
                       10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
      Thread 0xa6       
    Kernel stack:
        10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
          10 dlil_init + 1292 (in mach_kernel)[0x355d9c]
            10 msleep + 165(in mach_kernel) [0x575e25]
             10 wakeup + 287 (in mach_kernel) [0x57571f]
                10 lck_mtx_sleep + 79 (inmach_kernel) [0x227bcf]
                 10 thread_block + 33 (in mach_kernel) [0x22f771]
                    10 thread_block_reason + 331(in mach_kernel) [0x22f62b]
                      10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
                       10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
      Thread 0xa7       
    Kernel stack:
        10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
          10 utun_register_control + 56899 (inmach_kernel) [0x384b73]
            10tsleep + 116 (in mach_kernel) [0x575cf4]
              10 wakeup + 685 (in mach_kernel)[0x5758ad]
                10thread_block + 33 (in mach_kernel) [0x22f771]
                  10 thread_block_reason + 331 (inmach_kernel) [0x22f62b]
                   10 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
                      10 machine_switch_context +582 (in mach_kernel) [0x2cba26]
    Thread 0xaa       
      Kernel stack:
        10 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
          10 bpf_validate +25673 (in mach_kernel) [0x34cd59]
           10 msleep + 165 (in mach_kernel) [0x575e25]
              10 wakeup + 287 (in mach_kernel)[0x57571f]
                10 lck_mtx_sleep+ 79 (in mach_kernel) [0x227bcf]
                  10 thread_block + 33 (inmach_kernel) [0x22f771]
                   10 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
                      10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
                        10 machine_switch_context + 582 (inmach_kernel) [0x2cba26]
      Thread0xab       
      Kernel stack:
        10 sockwall_gc_thread + 0 (in ALF)[0x219c58f]
      Thread 0xad       
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0xaf       
    Kernel stack:
        9IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
        1 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
          1IOWorkLoop::threadMain() + 97 (in mach_kernel) [0x660839]
            1 thread_block_parameter + 32 (inmach_kernel) [0x22f740]
              1thread_block_reason + 306 (in mach_kernel) [0x22f612]
                1 thread_cancel_timer + 640 (inmach_kernel) [0x22e110]
                 1 processor_idle + 181 (in mach_kernel) [0x22d335]
                    1 machine_idle + 206 (inmach_kernel) [0x2cfbce]
      Thread0xb0       
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0xbc       
      Kernel stack:
        10 thread_call_func + 752 (in mach_kernel)[0x23e300]
      Thread 0xd4       
    Kernel stack:
        10thread_call_func + 752 (in mach_kernel) [0x23e300]
      Thread 0xe0       
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0xe3       
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0xe6       
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x109      
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x10b      
    Kernel stack:
        10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
          10 catch_exception_raise + 550 (inmach_kernel) [0x5cf866]
            10mach_msg_receive + 165 (in mach_kernel) [0x21b415]
              10 ipc_mqueue_receive + 105 (in mach_kernel)[0x214fd9]
                10thread_block + 33 (in mach_kernel) [0x22f771]
                  10 thread_block_reason + 331 (inmach_kernel) [0x22f62b]
                   10 thread_continue + 1729 (in mach_kernel) [0x22f3a1]
                      10 machine_switch_context +582 (in mach_kernel) [0x2cba26]
    Thread 0x10c      
      Kernel stack:
        10 vm_pageout_internal_start + 128 (inmach_kernel) [0x2937b0]
      Thread0x10d      
      Kernel stack:
        10 vm_pageout_internal_start + 1440 (inmach_kernel) [0x293cd0]
      Thread0x10e      
      Kernel stack:
        10 vm_object_page_grab + 5088 (inmach_kernel) [0x2898e0]
      Thread0x13e      
      Kernel stack:
        10 call_continuation + 28 (in mach_kernel)[0x2c6d0c]
          10sock_inject_data_in + 622 (in mach_kernel) [0x5bae7e]
            10 msleep + 165 (in mach_kernel)[0x575e25]
              10 wakeup + 287(in mach_kernel) [0x57571f]
               10 lck_mtx_sleep + 79 (in mach_kernel) [0x227bcf]
                  10 thread_block + 33 (inmach_kernel) [0x22f771]
                   10 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
                      10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
                       10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
      Thread 0x1bd      
    Kernel stack:
        10 call_continuation+ 28 (in mach_kernel) [0x2c6d0c]
         10 dlil_if_ref + 3518 (in mach_kernel) [0x3551de]
            10 msleep + 165 (in mach_kernel)[0x575e25]
              10 wakeup + 287(in mach_kernel) [0x57571f]
               10 lck_mtx_sleep + 79 (in mach_kernel) [0x227bcf]
                  10 thread_block + 33 (inmach_kernel) [0x22f771]
                   10 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
                      10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
                       10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
      Thread 0x1bf      
    Kernel stack:
        10call_continuation + 28 (in mach_kernel) [0x2c6d0c]
          10 dlil_if_ref + 3518 (in mach_kernel)[0x3551de]
            10 msleep + 165(in mach_kernel) [0x575e25]
              10 wakeup + 287 (in mach_kernel)[0x57571f]
                10lck_mtx_sleep + 79 (in mach_kernel) [0x227bcf]
                  10 thread_block + 33 (inmach_kernel) [0x22f771]
                   10 thread_block_reason + 331 (in mach_kernel) [0x22f62b]
                      10 thread_continue + 1729 (inmach_kernel) [0x22f3a1]
                       10 machine_switch_context + 582 (in mach_kernel) [0x2cba26]
      Thread 0x29c      
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x2a3      
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x2a6      
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x2ad      
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x2ae      
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x2cd      
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x2d1      
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x2d3      
    Kernel stack:
        10IOWorkLoop::threadMain() + 0 (in mach_kernel) [0x6607d8]
      Thread 0x2d6      
    Kernel stack:
        10 IOWorkLoop::threadMain()+ 0 (in mach_kernel) [0x6607d8]
    Thread 0x2d8      
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0x2ee      
      Kernel stack:
        10 vm_pageout_internal_start + 128 (inmach_kernel) [0x2937b0]
      Thread0x32e      
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0x360      
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0x369      
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      Thread0x36c      
      Kernel stack:
        9 thread_call_func + 752 (in mach_kernel)[0x23e300]
        1 call_continuation +28 (in mach_kernel) [0x2c6d0c]
         1 thread_call_func + 990 (in mach_kernel) [0x23e3ee]
            1IOSCSIMultimediaCommandsDevice::sPollForMedia(void*, void*) + 34 (inIOSCSIMultimediaCommandsDevice) [0x15be89a]
              1IOSCSIMultimediaCommandsDevice::PollForMedia() + 180 (inIOSCSIMultimediaCommandsDevice) [0x15c10cc]
                1IOSCSIPrimaryCommandsDevice::SendCommand(OSObject*, unsigned long) + 327 (inIOSCSIArchitectureModelFamily) [0xb485cb]
                  1IOSCSIPrimaryCommandsDevice::ExecuteCommand(OSObject*) + 38 (inIOSCSIArchitectureModelFamily) [0xb4755c]
                    1IOSCSIPeripheralDeviceNub::ExecuteCommand(OSObject*) + 33 (inIOSCSIArchitectureModelFamily) [0xb46157]
                      1IOSCSIProtocolServices::ExecuteCommand(OSObject*) + 220 (inIOSCSIArchitectureModelFamily) [0xb4aa2c]
                        1IOCommandGate::runAction(int (*)(OSObject*, void*, void*, void*, void*), void*,void*, void*, void*) + 296 (in mach_kernel) [0x66266e]
                          1_ZL11WaitForTaskP8OSObjectP13IOCommandGateS0_ + 81 (inIOSCSIArchitectureModelFamily) [0xb49e68]
                            1IOEventSource::sleepGate(void*, unsigned long) + 82 (in mach_kernel)[0x6614e4]
                             1 IOWorkLoop::sleepGate(void*, unsigned long) + 80 (in mach_kernel)[0x660652]
                               1 IORecursiveLockSleep + 61 (in mach_kernel) [0x63f25d]
                                  1 lck_mtx_sleep +79 (in mach_kernel) [0x227bcf]
                                    1 thread_block+ 33 (in mach_kernel) [0x22f771]
                                      1thread_block_reason + 306 (in mach_kernel) [0x22f612]
                                        1thread_cancel_timer + 640 (in mach_kernel) [0x22e110]
                                          1processor_idle + 181 (in mach_kernel) [0x22d335]
                                            1 machine_idle+ 206 (in mach_kernel) [0x2cfbce]
    Thread 0x35be     
      Kernel stack:
        10 IOWorkLoop::threadMain() + 0 (inmach_kernel) [0x6607d8]
      BinaryImages:
        0x200000 -   0x768837 mach_kernel ??? (???) <C2810CF8-D672-3301-8D3F-ED56974A80E1> /mach_kernel
        0xb46000 -  0xb60fdb com.apple.iokit.IOSCSIArchitectureModelFamily 3.0.1 (3.0.1)<97490326-3E01-403D-A080-666932C4412A> /System/Library/Extensions/IOSCSIArchitectureModelFamily.kext/Contents/MacOS/IO SCSIArchitectureModelFamily
       0x15ba000 - 0x15ce8d7 com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.0.1 (3.0.1)<0359232F-AAA5-4588-BA79-B483F412F5A7>/System/Library/Extensions/IOSCSIA rchitectureModelFamily.kext/Contents/PlugIns/IOSCSIMultimediaCommandsDevice.kext /Contents/MacOS/IOSCSIMultimediaCommandsDevice
       0x1ef6000 - 0x1f15f9b com.apple.driver.AppleIntelCPUPowerManagement 167.0.0 (167.0.0)<EB830617-53D6-4098-A9C0-11AC8EF213D5> /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/App leIntelCPUPowerManagement
       0x2198000 - 0x219e0df com.apple.nke.applicationfirewall 3.2.30 (3.2.30)<6C2D82F8-137B-4117-BCDE-EBFAEA9F7BCB> /System/Library/Extensions/ALF.kext/Contents/MacOS/ALF
      Kextstat:
    Index Refs Address    Size      Wired      Name (Version)<Linked Against>
        1   71 0x945000  0x5d48     0x5d48     com.apple.kpi.bsd (11.2.0)
        2   6 0x932000   0x35c      0x35c     com.apple.kpi.dsep (11.2.0)
       3   93 0x9e7000   0x1ab7c   0x1ab7c    com.apple.kpi.iokit (11.2.0)
        4  97 0x93c000   0x8e60     0x8e60    com.apple.kpi.libkern (11.2.0)
       5   84 0x933000   0x7f0     0x7f0      com.apple.kpi.mach (11.2.0)
        6  29 0x934000   0x4274     0x4274    com.apple.kpi.private (11.2.0)
       7   43 0x939000   0x2924    0x2924     com.apple.kpi.unsupported(11.2.0)
        8    0 0x94f000  0x25f38    0x25f38    com.apple.kernel.6.0 (7.9.9)
        9   0 0xa02000   0x25f38    0x25f38   com.apple.kernel.bsd (7.9.9)
      10    0 0x9c1000   0x25f38

  • "DISK FULL" Touch Smart Pavilion notebook PC -- Model F3F15UA#AB​A

    I have not used a pc with so little storage before and I have no idea what to do next. I am getting messages that Java and Flash Player are not accessible or not on my computer, but When I try to fix it, I am blocked from continuing due to lack of disk space.
    I eliminated some programs, but did not solve the problem.  Also, when online, my Flash Player and Javascripts are not recognized.  Any help will be much appreciated.  I am feeling a little dinosaurish.

    Hi @flower46 
    Welcome to the HP Forums!
    It is a grand  place to find answer and suggestions!
    For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
    Sometimes things get accidentally  stored on the Recovery drive which is very limited and is not to be used for storage.
    I grasp you are getting a low disk space error.  You have deleted some programs but it did not make any difference.
    I think this document may assist you. Error: Low Disk Space. You are running out of disk space on Recovery (Windows 8)
    This will also help you to determine the amount of free space on Drive C.
    Here is a link to the HP Pavilion TouchSmart 10-e010nr Notebook PC Product Specifications.  It shows that it came with a 320GB hard drive which is a fair amount of storage.
    I hope this helped and Happy Holidays!
    Sparkles1
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

  • WAE 574 disk prob

    Logged into and got below, Can I do a hot reseat of the drive or do I have to shut down (docs say too) before reseating? Any other thoughts would be appreciated. No directory /local/local1! Logging in with home = "/". System Initialization Finished. Disk based software not installed. Some applications may not run correctly! #sh disks details Storage array not supported. Physical disk information:   disk00: Not present or not responding   disk01: Not present or not responding Mounted file systems: MOUNT POINT      TYPE      DEVICE                SIZE    INUSE      FREE USE% No RAID devices present. #sh disks tech Storage array not supported. === disk00 === disk00: Not present or not responding === disk01 === disk01: Not present or not responding Thanks in advance! Rich

    Hi Rich,
    Disks on this system should be hot swappable so I think you can go ahead and try a reseat without any intervention.
    This is mentionned under the following link: http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v431/configuration/guide/maint.html#wp1139597
    It seems that both disks were lost so even if they both come back after reseating, you might need to re-install the WAAS software as the raid array would have been lost.
    Regards,
    Nicolas

  • Disk prob

    ok so my disk utilitys said this
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Invalid leaf record count
    (It should be 796836 instead of 796837)
    796837
    ,"Checking multi-linked files.",0)
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking volume bitmap.
    Volume Bit Map needs minor repair
    Checking volume information.
    Invalid volume free block count
    (It should be 1153142 instead of 1150964)
    The volume the G-5 needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    and then a pop up poped up and ssaid that it had quite cuz of some thing whats up???
    i-mac g5   Mac OS X (10.4.8)  

    Hi dast357;
    If you have the protection plan, they should. That is why you paid for it.
    Do make sure you have current backups because there is a good chance they will replace the drive for you.
    Allan

Maybe you are looking for

  • CIN: Alteration of base value for CST in TAXINN

    Hi, In our business process there is a requirement that CST should not be calculated only on Basic Price + Excise Duties (BEDEcessSEcess) rather base value for CST should be Basic Price + Excise Duties (BEDEcessSEcess) + 2 Additional Surcharges as me

  • How can two users of one computer keep their bookmarks separate on Mozilla?

    My computer has User A and User B. User A has dozens of bookmarks all neatly organized in categories. User B would like to have his bookmarks on this computer, too, but doesn't want them to get mixed up with User A's bookmarks. What can we do with Us

  • V1.4.0 on W95

    I tried to install Java SDK V1.4.0 (with Forte) on a 486/W95 machine by offline execution of the self extracting installation file. All appeared to work, there were no error messages and it informed me that the installation was successful. The instal

  • Dual monitor suddenly stops working - flickering & vibrating

    Using a mid 2010 15" macbook pro with a LG Flatron W2261VP monitor and dual displaying these two worked perfectly for the past year with a HDMI cable into the thunderport. However suddenly it stopped displaying correctly, the MBP would detect the dis

  • Ooma Service Blocked?

    I have the Verizon 4G LTE Router and cannot get my Ooma to make outgoing calls (incoming calls work fine). The Ooma diagnostics report ports 123 and 53 are blocked. I've tried the following, to no avail: Forwarding ports 53 and 123 to the Ooma device