System lockups on rMBP

Question

Level 1

19 points

System lockups on rMBP

I'm having trouble with my rMBP as I encountered system getting hanged often and I had no choice but to forcibly reboot it after waiting for 20-30 mins. Earlier it was freezing once in a week or so. Then I read about booting the machine in Safe Mode once. Which I did and for a while it looked that this problem had disappeared. I could use my rMBP for a month without restarting and I never encountered any freeze. However, today after 31 days, I did encounter the freeze once more 😟 Every time when it happened, I checked the Console and I get mdworker or Spotlight indexing thing shown in the Console immediately before the system is frozen. I'm pasting it below. Can anyone suggest what further I could do to avoid this problem or if people are also having the same problem.

6/4/13 11:32:14.432 AM	mdworker[63298]	Unable to talk to lsboxd
6/4/13 11:32:14.495 AM	sandboxd[63299]	([63298]) mdworker(63298) deny mach-lookup com.apple.ls.boxd
6/4/13 11:32:14.000 AM	kernel[0]	Sandbox: sandboxd(63299) deny mach-lookup com.apple.coresymbolicationd

MacBook Pro with Retina display, OS X Mountain Lion, 2.6 GHz, 8 GB RAM

Posted on Jun 4, 2013 6:51 AM

Reply

Answer 1

Linc Davis

Level 10

209,541 points

Jun 4, 2013 10:00 AM in response to Tissot11

Those log messages are routine.

If you have more than one user account, these instructions must be carried out as an administrator.

Launch the Console application.

Step 1

Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

View ▹ Show Log List

from the menu bar.

Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time after you had the problem. Select the messages logged before the boot, while the system was unresponsive or was failing to shut down. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V). Please include the BOOT_TIME message at the end of the log extract.

If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.

When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

Please do not indiscriminately dump thousands of lines from the log into this discussion.

Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

Step 2

Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

Reply

Answer 2

Tissot11 Author

Level 1

19 points

Jun 5, 2013 2:02 AM in response to Linc Davis

Thanks Linc for your reply. I'm pasting below information and I hope that I don't overdo it! Part of the full report corresponding to sandboxd[63298] I'm pasting it afterwards the messages from the Console. In the System Diagnostic Report, there are no crash and panic logs. But there is a log about the Dashboard.app from yesterday though at a different time then when this lockup actually occurred. I'm not pasting it now as I noticed that it had only information about different running threads and binary images and it is quite long. If you suggest then I can paste this as well? Please let me know.

-------------------------------------------------------------------------------- ------------------------------------------------------------------------------

6/4/13 11:30:49.813 AM mDNSResponder[51]: SSLHandshake failed: -9806

6/4/13 11:30:49.813 AM mDNSResponder[51]: tcpCallback: stream connection for LLQ _autotunnel6.1050971659.members.btmm.icloud.com. (PTR) failed 5 times, retrying in 81162 ms

6/4/13 11:32:14.432 AM mdworker[63298]: Unable to talk to lsboxd

6/4/13 11:32:14.495 AM sandboxd[63299]: ([63298]) mdworker(63298) deny mach-lookup com.apple.ls.boxd

6/4/13 11:32:14.000 AM kernel[0]: Sandbox: sandboxd(63299) deny mach-lookup com.apple.coresymbolicationd

6/4/13 11:54:55.000 AM bootlog[0]: BOOT_TIME 1370339695 0

-------------------------------------------------------------------------------- -------------------------------------------------------------------------------

Full report corresponding to sandboxd[63298], I have removed the some portions about different running threads and the binary images section hoping that it isn't required.

-------------------------------------------------------------------------------- -------------------------------------------------------------------------------

mdworker(63298) deny mach-lookup com.apple.ls.boxd

Process: mdworker [63298]

Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker

Load Address: 0x10e091000

Identifier: mdworker

Version: ??? (???)

Code Type: x86_64 (Native)

Parent Process: launchd [144]

Date/Time: 2013-06-04 11:32:14.445 +0200

OS Version: Mac OS X 10.8.3 (12D78)

Report Version: 8

Thread 0:

0 libsystem_kernel.dylib 0x00007fff8fcc6686 mach_msg_trap + 10

1 CoreFoundation 0x00007fff954d1233 __CFRunLoopServiceMachPort + 195

2 CoreFoundation 0x00007fff954d6916 __CFRunLoopRun + 1078

3 CoreFoundation 0x00007fff954d60e2 CFRunLoopRunSpecific + 290

4 CoreFoundation 0x00007fff954e4dd1 CFRunLoopRun + 97

5 mdworker 0x000000010e099ba9

6 libdyld.dylib 0x00007fff9059d7e1 start + 0

Thread 1:

0 libsystem_kernel.dylib 0x00007fff8fcc8d16 kevent + 10

1 libdispatch.dylib 0x00007fff929bf9ee _dispatch_mgr_thread + 54

Thread 2:

0 libsystem_kernel.dylib 0x00007fff8fcc6686 mach_msg_trap + 10

1 liblaunch.dylib 0x00007fff890687c4

2 liblaunch.dylib 0x00007fff890674d9 bootstrap_look_up3 + 69

3 libxpc.dylib 0x00007fff94e0fc21 _xpc_connection_bootstrap_look_up_slow + 371

4 libxpc.dylib 0x00007fff94e0ec82 _xpc_connection_init + 1062

5 libdispatch.dylib 0x00007fff929bd0b6 _dispatch_client_callout + 8

6 libdispatch.dylib 0x00007fff929be47f _dispatch_queue_drain + 235

7 libdispatch.dylib 0x00007fff929be2f1 _dispatch_queue_invoke + 52

8 libdispatch.dylib 0x00007fff929be448 _dispatch_queue_drain + 180

9 libdispatch.dylib 0x00007fff929be2f1 _dispatch_queue_invoke + 52

10 libdispatch.dylib 0x00007fff929be1c3 _dispatch_worker_thread2 + 249

11 libsystem_c.dylib 0x00007fff94694d0b _pthread_wqthread + 404

12 libsystem_c.dylib 0x00007fff9467f1d1 start_wqthread + 13

Reply

Answer 3

Linc Davis

Level 10

209,541 points

Jun 5, 2013 8:35 AM in response to Tissot11

Please read this whole message before doing anything.

This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.

These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing.

Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.

Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands.

Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.

Launch the Terminal application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.

When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.

Step 1

Triple-click the line of text below to select it:

kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -f -a TextEdit

Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). A TextEdit window will open with the output of the command. Post the contents of that window, if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.

Step 2

Repeat with this line:

{ sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; sudo defaults read com.apple.loginwindow LoginHook; } | open -f -a TextEdit

This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.

Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.

Step 3

launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}' | open -f -a TextEdit

Step 4

ls -1A /e*/mach* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts 2> /dev/null | open -f -a TextEdit

Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.

Step 5

osascript -e 'tell application "System Events" to get name of every login item' | open -f -a TextEdit

Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output.

You can then quit Terminal.

Reply

Answer 4

Tissot11 Author

Level 1

19 points

Jun 6, 2013 1:59 AM in response to Linc Davis

Thanks Linc again for your very descriptive reply! I'm a long term user of Mac and quite familer with the terminal etc. in OS X, so you can cut short the description, whenever you feel like doing so, to save your time! And I heartily appreciate that you're looking into this issue! I'm pasting the output for each command below. Please let me know what to do further. I'm also keen to learn these tips and tricks from you!!

Step 1

-------------------------------------------------------------------------------- ---------

com.protech.NoSleep (1.3.3)

com.nvidia.CUDA (1.1.0)

com.github.osxfuse.filesystems.osxfusefs (2.5.5)

com.tuxera.filesystems.tufsfs.fusefs_txantfs (2013.3.14)

-------------------------------------------------------------------------------- --------

Step 2

---------------------------------------------------------------

com.agilebits.onepassword-osx-thumbs

---------------------------------------------------------------

Step 3

-----------------------------------------------------------------------

com.agilebits.onepassword-osx-helper

com.protech.NoSleep

com.nvidia.CUDASoftwareUpdate

com.spotify.webhelper

com.google.keystone.user.agent

---------------------------------------------------------------------

Step 4

------------------------------------------------

/Library/Components:

.

..

/Library/Extensions:

.

..

/Library/Frameworks:

.

..

AEProfiling.framework

AERegistration.framework

AudioMixEngine.framework

CUDA.framework

NyxAudioAnalysis.framework

OSXFUSE.framework

PluginManager.framework

iTunesLibrary.framework

/Library/Input Methods:

.

..

/Library/Internet Plug-Ins:

.

..

JavaAppletPlugin.plugin

Quartz Composer.webplugin

QuickTime Plugin.plugin

nsIQTScriptablePlugin.xpt

/Library/Keyboard Layouts:

.

..

/Library/LaunchAgents:

.

..

com.nvidia.CUDASoftwareUpdate.plist

com.protech.NoSleep.plist

/Library/LaunchDaemons:

.

..

/Library/PreferencePanes:

.

..

CUDA Preferences.prefPane

NoSleep.prefPane

OSXFUSE.prefPane

TeXDistPrefPane.prefPane

Tuxera NTFS.prefPane

/Library/PrivilegedHelperTools:

.

..

/Library/QuickLook:

.

..

iBooksAuthor.qlgenerator

iWork.qlgenerator

/Library/QuickTime:

.

..

AppleIntermediateCodec.component

AppleMPEG2Codec.component

/Library/ScriptingAdditions:

.

..

TotalTerminal.osax

/Library/Spotlight:

.

..

Microsoft Office.mdimporter

iBooksAuthor.mdimporter

iWork.mdimporter

/Library/StartupItems:

.

..

/etc/mach_init.d:

.

..

/etc/mach_init_per_login_session.d:

.

..

/etc/mach_init_per_user.d:

.

..

Library/Address Book Plug-Ins:

.

..

SkypeABDialer.bundle

SkypeABSMS.bundle

Library/Fonts:

.

..

DroidSansMono.ttf

Library/Frameworks:

.

..

EWSMac.framework

Library/Input Methods:

.

..

.localized

Library/Internet Plug-Ins:

.

..

Library/Keyboard Layouts:

.

..

Library/LaunchAgents:

.

..

com.apple.AddressBook.ScheduledSync.PHXCardDAVSource.CCD9BE58-45E2-45AF-ACBF-EEF B5E1E217E.plist

com.google.keystone.agent.plist

com.spotify.webhelper.plist

Library/PreferencePanes:

.

..

Library/Services:

.

..

Scale and Convert Images.workflow

-------------------------------------------------------------------------

Step 5

---------------------------------------------

iTunesHelper, gfxCardStatus, NoSleep, Remind Me Later, TotalTerminal, Dropbox

-------------------------------------------------------------------------------- ---------------------------------------

Reply

Answer 5

Linc Davis

Level 10

209,541 points

Jun 6, 2013 7:47 AM in response to Tissot11

The problem is caused by one or more of the third-party kernel modifications you've installed:

NoSleep

CUDA

OSXFuse

Tuxera NTFS

Finding the culprit(s) is a process of elimination. I would start with the first one.

Reply

Answer 6

Tissot11 Author

Level 1

19 points

Jun 6, 2013 8:42 AM in response to Linc Davis

Actually this problem was there even before I started using NoSleep (few months before). At that time I only had OSXFuse and Tuxera NTFS installed. Tuxera got updated in March, so it might have solved some issues. With OSXFuse I still have some small problems, so it could be a possible culprit! Though I need sshfs and it needs OSXFuse! However, as I mentioned before after booting into Safe Mode one and half month ago, it now took 31 days for this problem to show up, before I could see this problem occuring once in a week though 10.8.3 and 10.8.4 might have also fixed certain issues with OS X. It's harder to wait for that long to eliminate suspects with hit and trial method. Is there anything else that can be done?

Reply

Answer 7

Linc Davis

Level 10

209,541 points

Jun 6, 2013 8:56 AM in response to Tissot11

If the problem is caused by third-party software, one of the items mentioned above is causing it. You could try reinstalling the OS, but that rarely does any good. Beyond that, you'd have to consider a hardware fault.

Reply