64-bit and 32-bit driver packages
What are the accepted norms for creating packages for drivers? Is there an accepted template that installs 32-bit or 64-bit drivers from the same package or is it better to create two different packages?
I don't know about the accepted norm, but I am inclined to think that most drivers are small enough that you should install both 32-bit and 64-bit drivers from the same package. The only thing the extra driver does is take up tens of kilobytes of disk space. There are some small-footprint O/S's for which this would be a big deal, but Solaris is not one of them.
You can look at /var/sadm/install/contents to see what Sun does. Most of the drivers are in separate packages for 32 and 64-bits. The 64-bit packages have 'x' appended onto the end of the name. This makes sense since there are so many drivers -- those tens of KB start to add up.
Richard
Similar Messages
-
SCCM 2012 OSD; Not finding driver package during deployment
I've been having some trouble setting up my OSD deployment using SCCM 2012 and hope someone can point me in the right direction. Specifically I am having trouble with device driver deployment while deploying my reference image.
I am running SCCM Config Manager 2012 SP1 CU2. This is running on a Server 2012 VM with SQL 2012. I am building an OSD deployment and have successfully captured my reference image. I am not sure if it matters, but I manually built a reference
PC and using capture media (USB stick), I successfully captured my reference image. I have imported my drivers for the target PC into Config Manager and into a driver package. The driver package has been deployed to the distribution point
(DP). I checked the status of the driver package within the console and verified it has been deployed to the DP. I created a new task sequence (TS) to deploy the captured wim. Within the TS, I added an "Apply
Driver Package" step and pointed it to the aforementioned driver package. I added a WMI query to the step as follows
select * from Win32_ComputerSystem where Model like "HP Probook 6570b%."
Incidentally, I did a wmi query on the target PC to verify the model. I deployed the TS to the unknown computers collection and PXE booted the target PC. I ran through the OSD wizard and while OSD is verifying the deployment prerequisites,
the deployment fails with the error, "The task sequence cannot be run because a package referenced by the task sequence could not be found." I checked the smsts.log log and found the following:
Failed to find CCM_SoftwareDistribution object for AdvertID="CT120043", PackageID="CT100044", ProgramID="*"
After some research I found this error means Config Manager cannot find the driver package (PackageID="CT100044")
for deployment. After more research I have done the following:
Deleted the Driver Package and recreated it and updated the TS step to point to this package.
Deleted and recreated the TS along with the driver package.
Recreated the driver package and distributed content, only importing the NIC drivers as a way to make a simple test.
When distributing content I verified it was successfully completed each time as per the console.
Each time I recreated the driver package and the OSD failed, smsts.log is showing the appropriate package ID in the error. If I disable the Apply Driver Package step and configure a Apply Device Drivers step to install the best matched compatible drivers
and limit the driver matching to the specific driver package, the OSD completes but the drivers do not install. It is as if Config Manager is not seeing the imported drivers at all.
I have run out of options to try and hope someone can help point me in the next direction to take. After reading numerous forums and guides, I am sure I am doing the OSD steps correctly but I am apparently missing something.
Thanks in advance,
Mike G.Thanks for responding.
Yes after I posted the question I right-clicked on the driver package, and selected to update distribution points. I checked now (about 12 hours later) and the package is showing it has not finished updating. I checked the content status and
it is "waiting for content." I looked at distmgr.log and I found an error "Failed to start DP health monitoring task for package 'CT100044'. Error code: -1". This error would occur every 30 min after each time the DP retried to process
the package. After some research I found a post stating a file called "Microsoft" or "Program" on located on the root of the site server could cause this and renaming or deleting the file would resolve this. I renamed the file and after the next time
it retried, the error cleared, however the package status is still waiting for content. I tried doing a validation on the package but so far there has been no change. -
I have a windows 7 premium laptop, 64 bit driver, have tried to install itunes but recieve an error when trying to open. Error states "Apple Application Support is required to run itunes. uninstall and reinstall again, error 2 (windows error 2). have tried this 4-5 times with no success. help!
For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down page in case one of them applies.
Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
The section Install missing components has advice on breaking down the iTunes installer into the individual .msi files which might prove useful if AAS won't install normally.
tt2 -
I am running Lightroom 6 in conjunction with 64 bit Photoshop CS6. I need to install Camera Raw 9 plus other relevan updates for the Adobe Design and Web Premium CS6 package. Running Adobe Application manager finds the relevant updates but won't download / install them. Clicking the update button results in an error message "Application Manager has stopped working". This is a windows system running 64 bit Windows 7
update manually:
pre cc updates: http://www.adobe.com/downloads/updates/
cc updates: http://prodesigntools.com/adobe-cc-updates-direct-links-windows.html
cc 2014 updates: win (http://prodesigntools.com/adobe-cc-2014-updates-links-windows.html) / mac (http://prodesigntools.com/adobe-cc-2014-updates-links-mac.html) -
P2015 can't download windows 7 64 bit driver without contract and can't contact HP
After a repair, i am currently reloading my computer with windows 7 64 bit. The disc that came with my printer doesn't have a 64 bit driver. No problem. I went to the HP website. Imagine my surprice, when I went to download a driver and was told without an existing contract for a printer I've owned for 5 years, I can no longer download a driver or get support. Further, without payment, I have no way to contact a human someone to resolve this issue?
I bought an HP printer bc of the support and superior quality of the printers. Now, not only do I have no support, I have a 50 lb paper weight I can't use. If this is the way HP is now doing business, I AM NEVER BUYING ANOTHER HP PRINTER. I have recommended HP printers 100s of times for business and personal use. Now, all those people I've raved to about HP printers and those who have bought them, have the same paper weight I do. I spent 50 minutes on the HP website, found the serial #, jumped through all the hoops and this is the best you can do? I AM NOT HAPPY!Hello STwirre,
Welcome to the HP Forums!
I am sorry, but to get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial product. You can do this at http://h30499.www3.hp.com/hpeb/ .
I hope this helps.
I worked on behalf of HP -
MSI K8N SLI Mobo (with 24 bit SB Live!) and XP64, no driv
There are no drivers to be found anywhere for the onboard 24 bit SB Li've! chip on the MSI K8N SLI platinum motherboard. It's quite confusing really, seeing how it's a board designed for 64 bit processing yet there are no drivers for the Li've! chip. I'm assuming the drivers are in Beta development, is there a tentati've release date, even if it's November, it's better than not knowing anything. I love my 64 bit system but it really stinks having no sound.
Jan GonsalvesAs I stated in the original post, I am looking for 64 bit drivers for the Sound Blaster 24 bit Li've! chip that is onboard the MSI K8N SLI Platinum Motherboard. The "preview" drivers, as noted in the release notes:
(http://preview.creativelabs.com/Lists/Announcements/DispForm.aspx?ID=6&Source=http%3A%2F%2Fpreview%2Ec reativelabs%2Ecom%2Fdefault%2Easpx)
2. SYSTEM REQUIREMENTS
One of the following supported audio cards:
Creative SoundBlaster Li've! (except Li've! 24-bit)
Creative SoundBlaster Audigy (except Audigy LS)
Creative SoundBlaster Audigy 2 (except Audigy 2 NX)
These do NOT support Li've! 24 bit. In fact, on the Discussion board at the preview website, a moderator wrote this:
(http://preview.creativelabs.com/Lists/General%20Discussion/DispForm.aspx?ID=344&Source=http%3A%2F%2Fpreview%2 Ecreativelabs%2Ecom%2FLists%2FGeneral%2520Discussi on%2FAllItems%2Easpx)
"It is not a site for asking for the Li've 24-bit/Audigy LS/NX drivers (32-bit or 64-bit). If you want those drivers, post at the official Creative forum or contact technical/customer support. That will get noticed. No one reads this site except for the people involved in the 64-bit driver preview for hardware listed in the release notes."
So, according to that email is says this list is responsible for producing 64 Bit drivers for the SB Li've! 24 bit chip. I would like to know which group is responsible for the drivers and when these drivers are TBA. Like I said, rough estimates are fine, I just want to know SOMEONE is working on it.
Jan -
Can't install a 32 bit driver on my new 64 bit server
I have a windows 2008 R2 server runing the print server. I have a HP Laserjet 4345 MFP Printer and can't install the 32 bit driver. I have installed the 64 bit but when I try to add the 32 bit driver is states that it is not the correct driver? I have downloaded the PCl 5 Driver (HP_LJ_M4345MFP_PCL5_32bit) But it states it the wrong driver. Please Help
Thanks,
Dave
David Babbel
System AdminHi broadwater,
Could you please re-download the package from this link and then install
http://www.adobe.com/go/tryphotoshop_elements/
Regards,
Sandeep -
FRUSTRATED - windows 7 64 bit driver HP 6500 709e all in one won't install on 2 computers
Hi,
My son and I both got new laptops for Christmas. I have had nothing but problems installing our wireless printer with its full features. My son's computer is a Dell, mine is a Toshiba. From what I could find both needed the same driver but both have had MAJOR issues getting the install to complete and installing the device. Somehow I was able to get it installed on my Toshiba but the "fix" I used didn't work on the Dell. PLEASE HELP! Thanks
Carol
Sorry I realized I did add much information. The printer is the 6500 all in one deskjet 709e. I have tried installing the 64 bit, windows 7...i also downloaded the update. Eventually it worked for my Toshiba laptop but still can't get it to install on my son's dell.
After numerous tries,
I downloaded the driver for windows 7, 64 bit driver and then downloaded the update. The driver/software wouldn't install the device until I did the update (for my Toshiba) but this is not working for the Dell. Also I did download the troubleshooter and it was useless!Welcome to the HP Forums Zoney,
I read your post which indicates that you are getting a "MICROSOFT VISUAL C ++RUNTIME LIBRARY" error, when trying to install the printer software. I can help you with this.
Download and install this Patch> Microsoft Visual C++ Runtime Error.
Uninstall the printer software.
Before installing the printer software again, setup the Admin rights on the computer.
Run Command Prompt as Administrator. Go to the start menu, type “CMD” in the search bar. Now, you should see a shortcut for CMD above. Right click on it, and click “run as administrator”. If it asks you for administrative permission, please allow permission. In your Command Prompt window (as administrator), type the following and hit Enter: net user administrator /active:yes
You should see a message saying "the command completed successfully". After troubleshooting is done, you can disable this account by typing the following command into Command Prompt (as administrator): net user administrator /active:no.
Restart the computer, and utilize the new account that is available, which should be named "Administrator".
Here are some more steps you can try if you are still getting the Runtime error.
But it is looking more like a Operating System issue.
Download and install the Microsoft Visual C++ 2010, 2008 and 2005 Redistributable Packages.
You will find the download links to these packages below:
2005 - http://www.microsoft.com/en-ca/download/details.aspx?id=26347
2008 - http://www.microsoft.com/en-ca/download/details.aspx?id=5582
2010 - http://www.microsoft.com/en-us/download/details.aspx?id=14632
Try the installation again please.
Let me know how you make out.
Have a nice day!
Thank You.
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 right to say “Thanks” for helping!
Gemini02
I work on behalf of HP -
Win 7 64-bit driver needed for HP LaserJet 1022
Cannot find a driver for HP LaserJet 1022 (non-networked, directly connected) printer. The one from the HP website doesn't work. This is a fully up to date Win7 64-bit installation.
Thank you very much for any help you can give!!
This question was solved.
View Solution.Here is a I have created a document (see attached) that has 3 different install methods. These install methods have been tested several times on several different system and all have worked successfully, both in printing test pages and in printing from Word, in the 32 and 64 bit environments.
Several people have reported that install method 3 has worked successfully for them.
If you have downloaded drivers previous drivers and you want to clean them off your system, you will need to delete everything that has LJ1020 or LJ 1022 associated with it. This means removing everything from the driver store and from all HP folders. You will need to look in your Print Server Properties (at the top of your device manager, make sure you have at least one driver with a green check mark on it and it isn't the LJ1022 so you can see the Print Server Properties) and delete the driver and package from here. As well as delete the LJ1022 folders from your C://Program files and your recycle bin. Then make sure your reboot your computer BEFORE you try and reinstall anything. You may have to do this a couple of time before everything is off your system.
I am an HP employee.
Say Thanks by clicking the Kudos Star in the post that helped you.
Please mark the post that solves your problem as Accepted Solution
Attachments:
3 install methods for the LJ1022.pdf 642 KB -
HP Laserjet 1012 Windows 7 64-bit Driver
I cannot find a Windows 7 64-bit driver for my Laserjet 1012. Has anyone else had any luck?
Win 7 X64 works with my Trusty HP Laserjet 1012.
From Start/Devices and Printers.
Choose add a printer.
Had to use Windows update at the bottom of the install printer driver window because the HP Laserjet 1015 was not on the list of HP printers. But after the update there it was "HP Laserjet 1015".
I did the intstall and it is working on my Win7 x64 machine and Office 2010. By the way, I chose Generic IEEE 1284.4 as the printer port (See comment below)
If you look on the HP website, they show the most recent drivers only for Vista x64 but the drivers are for the HP Laserjet 1010, 1012, 1015. So 1015 drivers will work but I did the install through Windows add printer as stated earlier in this thread and seems Win7 offers support for this legacy printer.
Comment:
Oddly the HP HP Laserjet 1012 also shows in unspecified devices on the Devices and printers page and did so before I installed the printer...I could not delete it but right clicking and Running Troubleshout gave me the choice to fix it saying "The driver for Generic IEEE 1284.4 printing support is not installed. Install the latest driver for the device." I believe chosing Apply this fix would have made it work. I am hoping on reboot it dissapears from unspecified. I will repost later -
Windows 8.1 64-bit driver for Coprocessor on Mid 2009 Macbook Pro 5,4
I have successfully installed Windows 8.1 Pro 64-bit onto my Mid 2009 Macbook Pro 5,4. The installer from BootCamp 5.0.533.5033 would not run, but I installed one-by-one the files under Apple and then ran the 64-bit nVidia installlers. I have everything present and accounted for except for the 'Coprocessor.'
I have looked through the forums and everything seems to indicated that if you install the nVidia drivers it will install the driver for this but it doesn't. Any thoughts/suggestions/solutions?For anyone who will find this post in the future, the Device Manager indicates that the 'Device Instance Path' is
pci co-processor pci\ven_10de&dev_0aa3&subsys_cb7910de&rev_b1\3&21436425&0&1d
Searching for that online, it appears that this is the nVidia MCP79 Co processor System.
This driver did not install with version 306.37 that came with the BootCamp drivers. I downloaded the current version from nVidia of 334.89 and that didn't work either. I searched online and found a driver for an Alienware 17x that uses the same co processor and ran the installer which extracted the files for the nVidia chipset v. 15.57 for 64-bit Windows 7 and Vista to c:\dell\drivers\R273039 and pointed the Device Manager to this folder and it was able to successfully install the driver software for the Management Controller (drivers are listed under the SMU folder for the "PCI\VEN_10DE&DEV_0AA3" device).
NVIDIA nForce System Management Controller
I then proceeded to use Double Driver to backup the drivers in use by the system so that if I install Windows 8 on future systems I can use this rather than the round-about way of getting the driver installed on the system. -
32 bit driver for windows 7 64 bit
I have a laserjet 1022 on my new Windows 7 64 bit,, works good.. I want to share the printer with XP 32 bit systems.. The 32 bit pcs connect up (somewhat) but dont print and get messages of death when trying to do a test page to the shared printer.. I read that I need to install the 32 bit drives on Windows 7 64 pc,, I found where to add the drivers in win 7,, but I need an .inf file of the 32 bit drivers.. The hp drivers i download so far just want to install.. Whats the process for getting the hp 32 bit drivers into the 64 bit system???
Thanks for sharing your tip RatioCynic! That's what this forum is all about!
Happy printing!
Thanks!
Tara
**Although I am an HP employee, I am speaking for myself and not for HP. -
Windows 8.1 64-bit driver for infrared usb adapter
I'm looking for the correct 64-bit driver on my Windows 8.1 OS for my infrared usb adapter that I'm trying to hotsync
with my Palm m500. I already have the Palm Desktop software for the 8.1. I just need the correct driver for thr adapter.
Any help with this will be greatly appreciated. ,Thank you.Hello, and Welcome to the HP Support Community!
I would suggest you try looking at the manufacturer's website for the dongle.
We have no idea what device you are asking about!
WyreNut
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked! -
Windows 7 - 64 Bit Driver Needed For Sound Blaster Live! 5.1 Model SB0100
I am having trouble finding a working driver for Windows 7 - 64 Bit for a Sound Blaster Li've! 5. Audo Card Model# SB000
I downloaded driver file SBL_PC64DRVBETA_LB_2_03_0005.exe which I think is a 64 Bit Sound Blaster Li've! update, but Windows 7 does not allow it to be installed because it is not a digitally signed driver. It also seems Creative is no longer supporting these old cards with new driver updates.
I love the card though. I have bought more recent sound cards and the sound of this card is still much better than the more recent sound cards I have bought. So I would like to keep using it if possible.
Are there any driver solutions?I recently answered about the same question:
If you?use Vista or Windows7, then there is no official driver. You can only use alternati've drivers like Vista Support Pack by Daniel_K or the one from KXProject (better). But if you have more than 2 gigs of memory installed or an x64 OS, then both drivers will be half-working (as far as I remember, Daniel's driver won't work with more than 2 Gb of memory installed in any OS, and with KX-driver there will only be a problem with MIDI playback with more than 2 Gb AND x64 Win7). -
How to identify a false 64-bit driver?
Since upgrading to Lion on my iMac (2.93 GHz, i7 with 16 GB) I often—usually, in fact—have kernel panics upon restarts. Inquiring about this on another Mac site brought a response suggesting that when upgrading to 10.7 a 32-bit driver slipped through, probably falsely indicating that it is 64-bit; restarting in 32 bit eliminates the kernel panics, suggesting that this is the case.
My question here: is there any way to identify what this false 64-bit driver is so that I can remove it?
Much thanks for any help.Thanks for the quick response.
I just induced a kernel panic (i.e., not holding down 3-2 during startup) and here is the report from /Library/Logs/DiagnosticReports:
Date/Time: 2011-12-22 18:07:43 +0100
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: 10.00s
Steps: 101 (100ms sampling interval)
Pageins: 7
Pageouts: 0
Process: DDServiced [106]
Path: /Library/Application Support/Data Robotics/*/DDServiced
Architecture: i386
UID: 0
Thread 0x35e
User stack:
101 start + 41 (in DDServiced) [0x7e7d]
101 _start + 209 (in DDServiced) [0x7f4f]
87 main + 1897 (in DDServiced) [0x8c17]
87 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273 (in Foundation) [0x9be7e607]
87 CFRunLoopRunInMode + 120 (in CoreFoundation) [0x934ba798]
87 CFRunLoopRunSpecific + 332 (in CoreFoundation) [0x934ba8ec]
87 __CFRunLoopRun + 1428 (in CoreFoundation) [0x934bb214]
87 __CFRunLoopServiceMachPort + 170 (in CoreFoundation) [0x934b20ea]
87 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x93891c22]
14 main + 1913 (in DDServiced) [0x8c27]
14 usleep + 60 (in libsystem_c.dylib) [0x92a6ecba]
14 mach_wait_until + 10 (in libsystem_kernel.dylib) [0x93891d36]
Kernel stack:
87 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
14 mach_wait_until_trap + 80 (in mach_kernel) [0x21df60]
Thread 0x63a DispatchQueue 1701273966
User stack:
101 _dispatch_mgr_thread + 53 (in libdispatch.dylib) [0x925756a7]
101 kevent + 10 (in libsystem_kernel.dylib) [0x9389490a]
Kernel stack:
101 kqueue_scan + 480 (in mach_kernel) [0x5596e0]
Thread 0x640
User stack:
101 thread_start + 34 (in libsystem_c.dylib) [0x92ac66de]
101 _pthread_start + 335 (in libsystem_c.dylib) [0x92ac2ed9]
101 __select + 10 (in libsystem_kernel.dylib) [0x93893b42]
Kernel stack:
101 wakeup + 1024 (in mach_kernel) [0x575a00]
Thread 0xbf90a
User stack:
44 start_wqthread + 30 (in libsystem_c.dylib) [0x92ac66fe]
44 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x9389402e]
Kernel stack:
44 workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
Thread 0xbf8f5
User stack:
43 start_wqthread + 30 (in libsystem_c.dylib) [0x92ac66fe]
43 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x9389402e]
Kernel stack:
43 workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
Binary Images:
0x1000 - 0x21afe7 DDServiced ??? (???) <D75D013D-0EF1-2DAA-666E-10BC0FEE323A> /Library/Application Support/Data Robotics/*/DDServiced
0x92574000 - 0x92582fff libdispatch.dylib ??? (???) <B50C62AD-0B5B-34C3-A491-ECFD72ED505E> /usr/lib/system/libdispatch.dylib
0x92a66000 - 0x92b31fff libsystem_c.dylib ??? (???) <1B0A12B3-DAFA-31E2-8F82-E98D620E4D72> /usr/lib/system/libsystem_c.dylib
0x93480000 - 0x93656fe3 com.apple.CoreFoundation 6.7.1 (635.15) <AC9F6462-6315-3D89-8075-D048DB4DBF7E> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9387b000 - 0x93899ff7 libsystem_kernel.dylib ??? (???) <124A6CE3-3934-3994-9D0A-E85A0C0BF082> /usr/lib/system/libsystem_kernel.dylib
0x9be72000 - 0x9c17cff3 com.apple.Foundation 6.7.1 (833.20) <B5092554-485A-3A7D-904B-B04B1EE5C50C> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
Process: java [108]
Path: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java
Architecture: x86_64
UID: 0
Thread 0x360 DispatchQueue 1
User stack:
31 ??? (in java) [0x109dc6a98]
31 ??? (in java) [0x109dc929a]
31 ??? (in java) [0x109dc9843]
31 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff83524ae6]
31 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff835252d4]
31 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8351cb6c]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x60b DispatchQueue 2
User stack:
31 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff8128414e]
31 kevent + 10 (in libsystem_kernel.dylib) [0x7fff8c0ef7e6]
Kernel stack:
31 kqueue_scan + 480 (in mach_kernel) [0x5596e0]
Thread 0x415
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in java) [0x109dc8240]
31 ??? (in java) [0x109dc7cf3]
31 ??? (in libclient64.dylib) [0x109f33a1d]
31 ??? (in libclient64.dylib) [0x109f33b75]
31 ??? (in libclient64.dylib) [0x109f1053e]
31 ??? (in libclient64.dylib) [0x109f1077a]
31 ??? [0x10a818438]
31 ??? [0x10a81d85a]
31 ??? [0x10a81d85a]
31 ??? [0x10a828d6e]
31 JVM_MonitorWait + 59 (in libjvmlinkage.dylib) [0x10a563b0b]
31 JVM_MonitorWait + 154 (in libclient64.dylib) [0x109f1ccbc]
31 ??? (in libclient64.dylib) [0x109f1d050]
31 ??? (in libclient64.dylib) [0x109f1dbc3]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x418
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109e79ca3]
31 ??? (in libclient64.dylib) [0x109e79de9]
31 mach_msg_server + 641 (in libsystem_kernel.dylib) [0x7fff8c0ed31c]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x41a
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109e915c8]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x41b
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109e915c8]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x41c
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109e915c8]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x41d
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109e915c8]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x41e
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109e915c8]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x41f
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109e915c8]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x420
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109e915c8]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x421
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109e915c8]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x422
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x10a2dce35]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x423
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x10a2dce35]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x424
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109e979e9]
31 ??? (in libclient64.dylib) [0x109f6d7cf]
31 ??? (in libclient64.dylib) [0x109f6d8e5]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e97b6e]
31 ??? (in libclient64.dylib) [0x109e78fb5]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x5fb
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f0f307]
30 ??? (in libclient64.dylib) [0x109f0f5b7]
30 ??? (in libclient64.dylib) [0x109e787c3]
30 ??? (in libclient64.dylib) [0x109e7891d]
30 ??? (in libclient64.dylib) [0x109e97b6e]
30 ??? (in libclient64.dylib) [0x109e78fb5]
30 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
1 ??? (in libclient64.dylib) [0x109f0f703]
1 ??? (in libclient64.dylib) [0x10a007ebd]
1 ??? (in libclient64.dylib) [0x10a007fa9]
1 ??? (in libclient64.dylib) [0x10a05ee92]
1 ??? (in libclient64.dylib) [0x10a05ef20]
1 ??? (in libclient64.dylib) [0x10a049b69]
1 ??? (in libclient64.dylib) [0x10a05f44c]
1 ??? (in libclient64.dylib) [0x10a05f632]
1 ??? (in libclient64.dylib) [0x10a05fba8]
1 ??? (in libclient64.dylib) [0x10a0601ce]
1 ??? (in libclient64.dylib) [0x10a0634de]
1 ??? (in libclient64.dylib) [0x10a063592]
1 ??? (in libclient64.dylib) [0x10a0636fe]
1 ??? (in libclient64.dylib) [0x109ef2b10]
Kernel stack:
30 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
1 lo_allintrs + 302 (in mach_kernel) [0x2e3fde]
1 interrupt + 200 (in mach_kernel) [0x2cdb98]
1 lapic_interrupt + 95 (in mach_kernel) [0x2d33ef]
1 cpu_signal_handler + 148 (in mach_kernel) [0x2d5254]
1 sync_iss_to_iks + 86 (in mach_kernel) [0x2cd046]
Thread 0x609
User stack:
31 ??? [0x10a9ff074]
31 ??? [0x10a8f16c8]
31 JVM_MonitorWait + 59 (in libjvmlinkage.dylib) [0x10a563b0b]
31 JVM_MonitorWait + 154 (in libclient64.dylib) [0x109f1ccbc]
31 ??? (in libclient64.dylib) [0x109f1d050]
31 ??? (in libclient64.dylib) [0x109f1dbc3]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x60a
User stack:
31 ??? [0x10a98bd28]
31 ??? [0x10a8f16c8]
31 JVM_MonitorWait + 59 (in libjvmlinkage.dylib) [0x10a563b0b]
31 JVM_MonitorWait + 154 (in libclient64.dylib) [0x109f1ccbc]
31 ??? (in libclient64.dylib) [0x109f1d050]
31 ??? (in libclient64.dylib) [0x109f1dbc3]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x617
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f1c355]
31 ??? (in libclient64.dylib) [0x109f1c540]
31 ??? (in libclient64.dylib) [0x109f2cfcd]
31 ??? (in libclient64.dylib) [0x109e7872a]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x618
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f1c355]
31 ??? (in libclient64.dylib) [0x109f1c540]
31 ??? (in libclient64.dylib) [0x109f2d4e5]
31 semaphore_wait_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed6b6]
Kernel stack:
31 semaphore_wait_continue + 0 (in mach_kernel) [0x234a50]
Thread 0x619
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f1c355]
31 ??? (in libclient64.dylib) [0x109f1c540]
31 ??? (in libclient64.dylib) [0x109f2e67f]
31 ??? (in libclient64.dylib) [0x109f3407d]
31 ??? (in libclient64.dylib) [0x109e7872a]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x61a
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f1c355]
31 ??? (in libclient64.dylib) [0x109f1c540]
30 ??? (in libclient64.dylib) [0x109f2e67f]
30 ??? (in libclient64.dylib) [0x109f3407d]
30 ??? (in libclient64.dylib) [0x109e7872a]
30 ??? (in libclient64.dylib) [0x109e7891d]
30 ??? (in libclient64.dylib) [0x109e78d42]
30 ??? (in libclient64.dylib) [0x109e78de3]
30 ??? (in libclient64.dylib) [0x109e78f23]
30 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
1 ??? (in libclient64.dylib) [0x109f2e5cc]
1 ??? (in libclient64.dylib) [0x109f3b5b4]
1 ??? (in libclient64.dylib) [0x109f3c6ab]
1 ??? (in libclient64.dylib) [0x109f80e04]
1 ??? (in libclient64.dylib) [0x109f9ff26]
1 ??? (in libclient64.dylib) [0x109fb2d26]
1 ??? (in libclient64.dylib) [0x109f48223]
1 ??? (in libclient64.dylib) [0x109fcdf2d]
1 ??? (in libclient64.dylib) [0x109ee1598]
1 ??? (in libclient64.dylib) [0x10a01aa64]
1 ??? (in libclient64.dylib) [0x10a01acdd]
1 ??? (in libclient64.dylib) [0x109e77b0f]
1 ??? (in libclient64.dylib) [0x109e77bcd]
1 ??? (in libclient64.dylib) [0x109e78d42]
1 ??? (in libclient64.dylib) [0x109e78de3]
1 ??? (in libclient64.dylib) [0x109e78f23]
1 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x61b
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f1c355]
31 ??? (in libclient64.dylib) [0x109f1c540]
31 ??? (in libclient64.dylib) [0x109f30080]
31 ??? (in libclient64.dylib) [0x109e787c3]
31 ??? (in libclient64.dylib) [0x109e7891d]
31 ??? (in libclient64.dylib) [0x109e78d42]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x61c
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f321b2]
31 ??? (in libclient64.dylib) [0x109e97b6e]
31 ??? (in libclient64.dylib) [0x109e78fb5]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
29 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
2 lo64_mach_scall + 23 (in mach_kernel) [0x2e4997]
2 thread_set_child + 407 (in mach_kernel) [0x2b7307]
2 mach_msg_overwrite_trap + 517 (in mach_kernel) [0x21b2f5]
2 ipc_mqueue_receive + 93 (in mach_kernel) [0x214fcd]
2 thread_block + 33 (in mach_kernel) [0x22f771]
2 thread_block_reason + 306 (in mach_kernel) [0x22f612]
2 thread_cancel_timer + 640 (in mach_kernel) [0x22e110]
2 processor_idle + 181 (in mach_kernel) [0x22d335]
2 machine_idle + 206 (in mach_kernel) [0x2cfbce]
Thread 0x76e
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f1c355]
31 ??? (in libclient64.dylib) [0x109f1c540]
31 ??? (in libclient64.dylib) [0x109f1c69e]
31 ??? (in libclient64.dylib) [0x109f1c6fe]
31 ??? (in libclient64.dylib) [0x109f1c808]
31 ??? (in libclient64.dylib) [0x109f1077a]
31 ??? [0x10a818438]
31 ??? [0x10a81dd34]
31 ??? [0x10a81d85a]
31 ??? [0x10a8f1351]
31 JVM_Sleep + 62 (in libjvmlinkage.dylib) [0x10a56465e]
31 JVM_Sleep + 191 (in libclient64.dylib) [0x10a029466]
31 ??? (in libclient64.dylib) [0x10a01a8d8]
31 ??? (in libclient64.dylib) [0x109e78fb5]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x7a3
User stack:
30 ??? [0x10abd46a4]
30 ??? [0x10a81d85a]
30 ??? [0x10a81d85a]
30 ??? [0x10a8f16c8]
30 JVM_MonitorWait + 59 (in libjvmlinkage.dylib) [0x10a563b0b]
30 JVM_MonitorWait + 154 (in libclient64.dylib) [0x109f1ccbc]
30 ??? (in libclient64.dylib) [0x109f1d050]
30 ??? (in libclient64.dylib) [0x109f1dbcd]
30 ??? (in libclient64.dylib) [0x109e97b6e]
30 ??? (in libclient64.dylib) [0x109e78fb5]
30 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
1 ??? [0x113ea1ac8]
1 ??? [0x10abd46a4]
1 ??? [0x10a81d85a]
1 ??? [0x10a81d85a]
1 ??? [0x10a8f16c8]
1 JVM_MonitorWait + 59 (in libjvmlinkage.dylib) [0x10a563b0b]
1 JVM_MonitorWait + 154 (in libclient64.dylib) [0x109f1ccbc]
1 ??? (in libclient64.dylib) [0x109f1d050]
1 ??? (in libclient64.dylib) [0x109f1dbcd]
1 ??? (in libclient64.dylib) [0x109e97b6e]
1 ??? (in libclient64.dylib) [0x109e78fb5]
1 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0xbf91a
User stack:
31 start_wqthread + 13 (in libsystem_c.dylib) [0x7fff822e2b85]
31 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x7fff8c0ef192]
Kernel stack:
31 workqueue_exit + 1808 (in mach_kernel) [0x5c60e0]
Thread 0xbf91b
User stack:
Kernel stack:
31 workqueue_exit + 1232 (in mach_kernel) [0x5c5ea0]
Thread 0xbf91c
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f1c355]
31 ??? (in libclient64.dylib) [0x109f1c540]
31 ??? (in libclient64.dylib) [0x109f1c69e]
31 ??? (in libclient64.dylib) [0x109f1c6fe]
31 ??? (in libclient64.dylib) [0x109f1c808]
31 ??? (in libclient64.dylib) [0x109f1077a]
31 ??? [0x10a818438]
31 ??? [0x10a81dd34]
31 ??? [0x10a81dd34]
31 ??? [0x10a81d85a]
31 ??? [0x10a81d85a]
31 ??? [0x10a81d85a]
31 ??? [0x10a81dd34]
31 ??? [0x10a81d85a]
31 ??? [0x10a81d85a]
31 ??? [0x10a81d85a]
31 ??? [0x10a81d85a]
31 ??? [0x10a8f16c8]
31 JVM_MonitorWait + 59 (in libjvmlinkage.dylib) [0x10a563b0b]
31 JVM_MonitorWait + 154 (in libclient64.dylib) [0x109f1ccbc]
31 ??? (in libclient64.dylib) [0x109f1d050]
31 ??? (in libclient64.dylib) [0x109f1dbc3]
31 ??? (in libclient64.dylib) [0x109e78de3]
31 ??? (in libclient64.dylib) [0x109e78f23]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0xbf920
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f1c355]
31 ??? (in libclient64.dylib) [0x109f1c540]
31 ??? (in libclient64.dylib) [0x109f1c69e]
31 ??? (in libclient64.dylib) [0x109f1c6fe]
31 ??? (in libclient64.dylib) [0x109f1c808]
31 ??? (in libclient64.dylib) [0x109f1077a]
31 ??? [0x10a818438]
31 ??? [0x10a81d85a]
20 ??? [0x10a8f1351]
20 JVM_Sleep + 62 (in libjvmlinkage.dylib) [0x10a56465e]
20 JVM_Sleep + 191 (in libclient64.dylib) [0x10a029466]
20 ??? (in libclient64.dylib) [0x10a01a8d8]
20 ??? (in libclient64.dylib) [0x109e78fb5]
20 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d85a]
11 ??? [0x10a8f1351]
11 JVM_Sleep + 62 (in libjvmlinkage.dylib) [0x10a56465e]
11 JVM_Sleep + 191 (in libclient64.dylib) [0x10a029466]
11 ??? (in libclient64.dylib) [0x10a01a8d8]
11 ??? (in libclient64.dylib) [0x109e78fb5]
11 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0xbf956
User stack:
31 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
31 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
31 ??? (in libclient64.dylib) [0x109e78884]
31 ??? (in libclient64.dylib) [0x109f1c355]
31 ??? (in libclient64.dylib) [0x109f1c540]
31 ??? (in libclient64.dylib) [0x109f1c69e]
31 ??? (in libclient64.dylib) [0x109f1c6fe]
31 ??? (in libclient64.dylib) [0x109f1c808]
31 ??? (in libclient64.dylib) [0x109f1077a]
31 ??? [0x10a818438]
31 ??? [0x10a81dd34]
31 ??? [0x10a81d85a]
31 ??? [0x10a8f1351]
31 JVM_Sleep + 62 (in libjvmlinkage.dylib) [0x10a56465e]
31 JVM_Sleep + 191 (in libclient64.dylib) [0x10a029466]
31 ??? (in libclient64.dylib) [0x10a01a8d8]
31 ??? (in libclient64.dylib) [0x109e78fb5]
31 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
31 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x8a9
User stack:
16 ??? [0x10a9aa3a0]
16 ??? [0x10a8f1351]
16 JVM_Sleep + 62 (in libjvmlinkage.dylib) [0x10a56465e]
16 JVM_Sleep + 191 (in libclient64.dylib) [0x10a029466]
16 ??? (in libclient64.dylib) [0x10a01a8d8]
16 ??? (in libclient64.dylib) [0x109e78fb5]
16 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
1 ??? [0x10ab08538]
1 ??? [0x10a81d85a]
1 ??? [0x10a81d85a]
1 ??? [0x10a81d85a]
1 ??? [0x10a81de8d]
1 ??? [0x10a81d9b3]
1 ??? [0x10a81d9b3]
1 ??? [0x10a81d85a]
1 ??? [0x10a81d85a]
1 ??? [0x10a828d6e]
1 ??? (in libjava.jnilib) [0x10a6cd6bb]
1 ??? (in libclient64.dylib) [0x109f2598e]
1 ??? (in libclient64.dylib) [0x109ee1598]
1 ??? (in libclient64.dylib) [0x10a01aa64]
1 ??? (in libclient64.dylib) [0x10a01acdd]
1 ??? (in libclient64.dylib) [0x109e77b0f]
1 ??? (in libclient64.dylib) [0x109e77bcd]
1 ??? (in libclient64.dylib) [0x109e78d42]
1 ??? (in libclient64.dylib) [0x109e78de3]
1 ??? (in libclient64.dylib) [0x109e78f23]
1 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
1 ??? [0x10aac33c8]
1 ??? [0x10aa86ba2]
1 ??? (in libjava.jnilib) [0x10a6cd32e]
1 JVM_Read + 55 (in libjvmlinkage.dylib) [0x10a567067]
1 read + 10 (in libsystem_kernel.dylib) [0x7fff8c0efaf2]
Kernel stack:
16 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
1 lo64_mach_scall + 23 (in mach_kernel) [0x2e4997]
1 thread_set_child + 407 (in mach_kernel) [0x2b7307]
1 mach_msg_overwrite_trap + 517 (in mach_kernel) [0x21b2f5]
1 ipc_mqueue_receive + 93 (in mach_kernel) [0x214fcd]
1 thread_block + 33 (in mach_kernel) [0x22f771]
1 thread_block_reason + 306 (in mach_kernel) [0x22f612]
1 thread_cancel_timer + 640 (in mach_kernel) [0x22e110]
1 processor_idle + 181 (in mach_kernel) [0x22d335]
1 machine_idle + 206 (in mach_kernel) [0x2cfbce]
1 lo64_unix_scall + 23 (in mach_kernel) [0x2e4977]
1 unix_syscall64 + 554 (in mach_kernel) [0x5f15fa]
1 read_nocancel + 163 (in mach_kernel) [0x585823]
1 write + 256 (in mach_kernel) [0x585090]
1 utf8_encodelen + 4080 (in mach_kernel) [0x3201b0]
1 VNOP_READ + 82 (in mach_kernel) [0x32a782]
1 hfs_vnop_read + 638 (in mach_kernel) [0x50883e]
1 cluster_read + 61 (in mach_kernel) [0x2fd34d]
1 cluster_read_ext + 330 (in mach_kernel) [0x2fbfca]
1 advisory_read + 4447 (in mach_kernel) [0x2fb9ef]
1 ubc_upl_commit_range + 127 (in mach_kernel) [0x59199f]
1 upl_commit_range + 74 (in mach_kernel) [0x28f5aa]
1 lo_allintrs + 302 (in mach_kernel) [0x2e3fde]
1 interrupt + 200 (in mach_kernel) [0x2cdb98]
1 lapic_interrupt + 95 (in mach_kernel) [0x2d33ef]
1 cpu_signal_handler + 148 (in mach_kernel) [0x2d5254]
1 sync_iss_to_iks + 86 (in mach_kernel) [0x2cd046]
Thread 0x773
User stack:
11 ??? [0x10a98bd28]
11 ??? [0x10a8f16c8]
11 JVM_MonitorWait + 59 (in libjvmlinkage.dylib) [0x10a563b0b]
11 JVM_MonitorWait + 154 (in libclient64.dylib) [0x109f1ccbc]
11 ??? (in libclient64.dylib) [0x109f1d050]
11 ??? (in libclient64.dylib) [0x109f1dbc3]
11 ??? (in libclient64.dylib) [0x109e78de3]
11 ??? (in libclient64.dylib) [0x109e78f23]
11 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
11 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x7a2
User stack:
11 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
11 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
11 ??? (in libclient64.dylib) [0x109e78884]
11 ??? (in libclient64.dylib) [0x109f1c355]
11 ??? (in libclient64.dylib) [0x109f1c540]
11 ??? (in libclient64.dylib) [0x109f1c69e]
11 ??? (in libclient64.dylib) [0x109f1c6fe]
11 ??? (in libclient64.dylib) [0x109f1c808]
11 ??? (in libclient64.dylib) [0x109f1077a]
11 ??? [0x10a818438]
11 ??? [0x10a81dd34]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d9b3]
11 ??? [0x10a81dd34]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d85a]
11 ??? [0x10a828d6e]
11 ??? (in libclient64.dylib) [0x10a095068]
11 ??? (in libclient64.dylib) [0x10a0952ad]
11 ??? (in libclient64.dylib) [0x109e78f23]
11 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
11 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x7b0
User stack:
11 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
11 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
11 ??? (in libclient64.dylib) [0x109e78884]
11 ??? (in libclient64.dylib) [0x109f1c355]
11 ??? (in libclient64.dylib) [0x109f1c540]
11 ??? (in libclient64.dylib) [0x109f1c69e]
11 ??? (in libclient64.dylib) [0x109f1c6fe]
11 ??? (in libclient64.dylib) [0x109f1c808]
11 ??? (in libclient64.dylib) [0x109f1077a]
11 ??? [0x10a818438]
11 ??? [0x10a81dd34]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d85a]
11 ??? [0x10a8f16c8]
11 JVM_MonitorWait + 59 (in libjvmlinkage.dylib) [0x10a563b0b]
11 JVM_MonitorWait + 154 (in libclient64.dylib) [0x109f1ccbc]
11 ??? (in libclient64.dylib) [0x109f1d050]
11 ??? (in libclient64.dylib) [0x109f1dbcd]
11 ??? (in libclient64.dylib) [0x109e97b6e]
11 ??? (in libclient64.dylib) [0x109e78fb5]
11 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
11 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x82b
User stack:
11 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
11 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
11 ??? (in libclient64.dylib) [0x109e78884]
11 ??? (in libclient64.dylib) [0x109f1c355]
11 ??? (in libclient64.dylib) [0x109f1c540]
11 ??? (in libclient64.dylib) [0x109f1c69e]
11 ??? (in libclient64.dylib) [0x109f1c6fe]
11 ??? (in libclient64.dylib) [0x109f1c808]
11 ??? (in libclient64.dylib) [0x109f1077a]
11 ??? [0x10a818438]
11 ??? [0x10a81d9b3]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d85a]
11 ??? [0x10a8f16c8]
11 JVM_MonitorWait + 59 (in libjvmlinkage.dylib) [0x10a563b0b]
11 JVM_MonitorWait + 154 (in libclient64.dylib) [0x109f1ccbc]
11 ??? (in libclient64.dylib) [0x109f1d050]
11 ??? (in libclient64.dylib) [0x109f1dbc3]
11 ??? (in libclient64.dylib) [0x109e78de3]
11 ??? (in libclient64.dylib) [0x109e78f23]
11 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
11 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0x215060]
Thread 0x82c
User stack:
11 thread_start + 13 (in libsystem_c.dylib) [0x7fff822e2b75]
11 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff822df8bf]
11 ??? (in libclient64.dylib) [0x109e78884]
11 ??? (in libclient64.dylib) [0x109f1c355]
11 ??? (in libclient64.dylib) [0x109f1c540]
11 ??? (in libclient64.dylib) [0x109f1c69e]
11 ??? (in libclient64.dylib) [0x109f1c6fe]
11 ??? (in libclient64.dylib) [0x109f1c808]
11 ??? (in libclient64.dylib) [0x109f1077a]
11 ??? [0x10a818438]
11 ??? [0x10a81dd34]
11 ??? [0x10a81d9b3]
11 ??? [0x10a81dd34]
11 ??? [0x10a81d85a]
11 ??? [0x10a81d85a]
11 ??? [0x10a828d6e]
11 ??? (in libclient64.dylib) [0x10a095068]
11 ??? (in libclient64.dylib) [0x10a0952ad]
11 ??? (in libclient64.dylib) [0x109e78f23]
11 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8c0ed67a]
Kernel stack:
Maybe you are looking for
-
I am actually posting this for my mom... She switched from PC to Macbook late last year. Ever since then, when she opens Mail, which is setup for her AOL account, several messages keep resending themselves until she Quits Mail (does not have to force
-
MacBook Pro GAMERS: 2.4 vs 2.6 OR 7200rpm drive OR?
I am getting a 15" MacBook Pro soon. I might wait for Macworld to see what improvements Apple makes in the line, but I want to see if some of the Apple-installed upgrades are really worth it, so I can possibly avoid unnecessarily spending some $. I w
-
Delete 'choose folder' message
Random is selected in Screen Savers, part of System Preferences. Instead of randomly choosing the folders that I have pictures/slides in to show, I get a message saying 'the folder chosen is empty, choose options', at least once a day. I don't know w
-
Buenos días, Sigo batallando con el Labview, acabo de adquirir mi licencia, es la básica, y estoy tratando de leer tensión eléctrica alterna: 20 Hz -10 kHz Entre 30 mV y 700 mV. Necesito obtener 10 lecturas de la tensión en RMS, como si fuera un mult
-
Deleting Uploaded Pix from computer
Hi Guys, Ive been searching and searching but cant seem to find an answer to this. Bascially Ive uploaded tons of pictures and videos from my desktop computer before it crashed to my iphone 5 and everything that was on that comptuer is gone including