Mac Pro Mouse lagging issues.

Question

Level 1

4 points

Mac Pro Mouse lagging issues.

Hi there.

i'm a proud owner of late 2013 MacPro that serves as a nice pro media server in live events useing Qlab as a platform to playing and handle video cues.

the mac pro is up to date with latest osx version (10.11.12) and all suggested updates already installed.

for some reason.

the external mouse and keyboard (any of which i try use, and i tried almost a dozen, including a mighty mouse and the wired original one that came with the mac),

any ways, the mouse and keyboard get stuck every 4-6 seconds for about 3 seconds with no way to do anything.

I heard somewhere it got something to do with the display settings but even if only one monitor is connected and in any resolution, mouse and keyboard get stuckd every 4-6 seconds.

even if no app is running.

i ran a hardware check, all ok.

i updated to el capitan's latest version - stuck every 4-6 seconds.

sometimes, with no particular reason, after tens and dozens of restarts, problem disappears.

another restart and we're stuck again.

the only way mouse and keyboard works as expected is on recovery mode and only until back to normal mode.

i changed literally each and every piece of external equipment connected and uninstalled every piece of third party software.

can't seem to find a reasonable reason for the input devices to halt in such consistent method.

any ideas? cause i'm running out of...

Thanks!

Mac Pro (Late 2013), null

Posted on Jan 28, 2016 9:24 AM

Reply

Answer 1

Jan 28, 2016 10:03 AM in response to Hakol.Sound

Mouse lag occurs most often when your processor cycles are all used up, or the (brain-damaged) driver for a particular piece of Hardware is using up so much CPU that there is no "background" time in which to update the mouse. Activity Monitor CPU display can be used to gain insight.

It can also occur if you have added any so-called Virus Checkers, which are universally useless on a Mac and interfere with the Mac's stability and its built-in malware deterrents.

Reply

Answer 2

Linc Davis

Level 10

209,541 points

Jan 28, 2016 1:21 PM in response to Hakol.Sound

When you notice the lag, note the exact time: hour, minute, second.

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any one 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 and start typing the name.

The title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar at the top of the screen.

Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.

Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.

Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

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

When you post the log extract, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

Reply

Answer 3

Hakol.Sound Author

Level 1

4 points

Feb 9, 2016 4:24 AM in response to Linc Davis

09/02/2016 2:23:11.237 PM com.apple.xpc.launchd[1]: (com.apple.watchdogd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

09/02/2016 2:23:11.356 PM secd[565]: SOSAccountThisDeviceCanSyncWithCircle sync with device failure: (null)

09/02/2016 2:23:21.274 PM watchdogd[1309]: [watchdog_daemon] @( wd_watchdog_open) - IOIteratorNext failed (kr=0)

09/02/2016 2:23:21.274 PM watchdogd[1309]: [watchdog_daemon] @( wd_daemon_init) - could not open connection with the kernel watchdog

09/02/2016 2:23:21.274 PM watchdogd[1309]: [watchdog_daemon] @( main) - cannot initialize the watchdog service

09/02/2016 2:23:21.275 PM com.apple.xpc.launchd[1]: (com.apple.watchdogd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

09/02/2016 2:23:31.311 PM watchdogd[1310]: [watchdog_daemon] @( wd_watchdog_open) - IOIteratorNext failed (kr=0)

09/02/2016 2:23:31.312 PM watchdogd[1310]: [watchdog_daemon] @( wd_daemon_init) - could not open connection with the kernel watchdog

09/02/2016 2:23:31.312 PM watchdogd[1310]: [watchdog_daemon] @( main) - cannot initialize the watchdog service

09/02/2016 2:23:31.313 PM com.apple.xpc.launchd[1]: (com.apple.watchdogd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

09/02/2016 2:23:41.350 PM watchdogd[1312]: [watchdog_daemon] @( wd_watchdog_open) - IOIteratorNext failed (kr=0)

09/02/2016 2:23:41.351 PM watchdogd[1312]: [watchdog_daemon] @( wd_daemon_init) - could not open connection with the kernel watchdog

09/02/2016 2:23:41.351 PM watchdogd[1312]: [watchdog_daemon] @( main) - cannot initialize the watchdog service

09/02/2016 2:23:41.352 PM com.apple.xpc.launchd[1]: (com.apple.watchdogd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

09/02/2016 2:23:51.390 PM watchdogd[1313]: [watchdog_daemon] @( wd_watchdog_open) - IOIteratorNext failed (kr=0)

09/02/2016 2:23:51.390 PM watchdogd[1313]: [watchdog_daemon] @( wd_daemon_init) - could not open connection with the kernel watchdog

09/02/2016 2:23:51.391 PM watchdogd[1313]: [watchdog_daemon] @( main) - cannot initialize the watchdog service

09/02/2016 2:23:51.392 PM com.apple.xpc.launchd[1]: (com.apple.watchdogd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

09/02/2016 2:24:01.430 PM watchdogd[1314]: [watchdog_daemon] @( wd_watchdog_open) - IOIteratorNext failed (kr=0)

09/02/2016 2:24:01.430 PM watchdogd[1314]: [watchdog_daemon] @( wd_daemon_init) - could not open connection with the kernel watchdog

09/02/2016 2:24:01.430 PM watchdogd[1314]: [watchdog_daemon] @( main) - cannot initialize the watchdog service

09/02/2016 2:24:01.431 PM com.apple.xpc.launchd[1]: (com.apple.watchdogd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

09/02/2016 2:24:11.466 PM watchdogd[1316]: [watchdog_daemon] @( wd_watchdog_open) - IOIteratorNext failed (kr=0)

09/02/2016 2:24:11.466 PM watchdogd[1316]: [watchdog_daemon] @( wd_daemon_init) - could not open connection with the kernel watchdog

09/02/2016 2:24:11.466 PM watchdogd[1316]: [watchdog_daemon] @( main) - cannot initialize the watchdog service

09/02/2016 2:24:11.467 PM com.apple.xpc.launchd[1]: (com.apple.watchdogd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Reply