Thanks for your replies, I suspected that the system freeze was not probably related to the log message but since it was the last message I had to try... To answers Kevin's question: it wasn't a kernel panic, the system just freezes, no mouse/keyboard responses and the screen remains the same. I'll try to figure out if it's related to some hw issue. The "normal support channels" weren't so useful last time but thanks for the suggestion. Again, thanks for decoding the log message for me and for pointing out that probably this can't be the cause of my problems. best regards/Rubén On Thu, Nov 4, 2010 at 5:13 PM, Kevin Van Vechten <kvv@apple.com> wrote:

Yes, neither a system-wide hang or by crash (do you mean kernel panic?) is likely to be related to this log message, and you should follow up with the normal support channels.

However, to decode the log message:

$ cd 10F569/libdispatch $ grep -rn assume * | grep 1730 src/source.c:1730: dispatch_assume_zero(kr);

(Note: the line numbers will vary some from the Mac OS Forge repository because not all of the cross-platform changes have been merged back into our release branch for 10F569)

This appears to be within _dispatch_kevent_machport_enable(dispatch_kevent_t dk) and error 0x11 is KERN_INVALID_RIGHT from kern_return.h. This implies that SystemUIServer has a bug where it's trying to create a dispatch source to monitor an invalid mach port.

Kevin

On Nov 4, 2010, at 8:41 AM, David Leimbach wrote:

When I've witnessed similar behavior, it's been due to bad RAM. If you can pull some and try running, see if that helps.

Otherwise you should probably contact Apple support.

On Wed, Nov 3, 2010 at 11:35 PM, Ruben Laguna <ruben.laguna@gmail.com

...

wrote:

My system (MacBook Pro) is crashing/freezing regularly 20 seconds after a wake up and the last message in the Console.app before the crash is a

SystemUIServer[184] BUG in libdispatch: 10F569 - 1730 - 0x11

I downloaded the git repo to find out what this means and if it is really related to my system freeze.

according to queue.c the format of this log is

_dispatch_log("BUG in libdispatch: %s - %lu - 0x%lx", _dispatch_build, (unsigned long)line, val);

So build 10F569, line 1730 (which file?), value 0x11.

Anyone can tell me exactly what this error log means , how to workaround it or point me to the right forum to ask?

-- /Rubén