Ruben Laguna | 4 Nov 07:35 2010
Picon

BUG in libdispatch: 10F569 - 1730 - 0x11

Hi, 


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?

Thanks /Rubén


--
/Rubén
_______________________________________________
libdispatch-dev mailing list
libdispatch-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev
David Leimbach | 4 Nov 16:41 2010
Picon

Re: BUG in libdispatch: 10F569 - 1730 - 0x11

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. 

Dave

On Wed, Nov 3, 2010 at 11:35 PM, Ruben Laguna <ruben.laguna-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
Hi, 

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?

Thanks /Rubén


--
/Rubén

_______________________________________________
libdispatch-dev mailing list
libdispatch-dev <at> lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev


_______________________________________________
libdispatch-dev mailing list
libdispatch-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev
Toby Peterson | 4 Nov 17:11 2010
Picon

Re: BUG in libdispatch: 10F569 - 1730 - 0x11

This error occurs when creating a dispatch source with a mach portset (rather than a port). Probably due to a
bug in one of the menu extras. However, it's extremely unlikely that it's the cause of the issues you're
seeing; at worst it would just cause one of your menu extras to misbehave.

- Toby

On Nov 3, 2010, at 11:35 PM, Ruben Laguna wrote:

> Hi, 
> 
> 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?
> 
> Thanks /Rubén
> 
> 
> -- 
> /Rubén
> _______________________________________________
> libdispatch-dev mailing list
> libdispatch-dev@...
> http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev
Kevin Van Vechten | 4 Nov 17:13 2010
Picon

Re: BUG in libdispatch: 10F569 - 1730 - 0x11

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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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?
_______________________________________________
libdispatch-dev mailing list
libdispatch-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev
Joakim Johansson | 4 Nov 17:24 2010

Patch submissions for Solaris compatibility

I submitted a few patches back in July for Solaris portability (enough to get libdispatch through most of
the test suite when built with gcc together with libkqueue/libpthread_workqueue) - was there any
(stylistic or other) issues with those that I should address for them being considered, or ...?

Cheers,

Joakim
Ruben Laguna | 4 Nov 17:45 2010
Picon

Re: BUG in libdispatch: 10F569 - 1730 - 0x11

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-2kanFRK1NckAvxtiuMwx3w@public.gmane.org> 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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
_______________________________________________
libdispatch-dev mailing list
libdispatch-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev
Mark Heily | 10 Nov 02:51 2010

[PATCH] various portability issues

I have attached a collection of patches that allows libdispatch to build on
Linux and Solaris. Many thanks to Joakim Johansson for providing the Solaris
patches and testing everything.

The commands I used to build on Linux are:

  CC="clang" LD="llvm-ld-2.8" CFLAGS="-I/usr/local" \
  LDFLAGS="-L/usr/local" LIBS="-lbsd" ./configure && make

The commands Joakim used to build on Solaris are:

  ./configure CFLAGS="-m64 -I/usr/local/include" \
  LDFLAGS="-L/usr/local/lib” gmake

Please review these and consider them for inclusion in the trunk.

Regards,

 - Mark
Attachment (attribute_unused.patch): text/x-patch, 491 bytes
Attachment (getexecname.patch): text/x-patch, 1513 bytes
Attachment (libpthread_workqueue.patch): text/x-patch, 1056 bytes
Attachment (private-extern.patch): text/x-patch, 1243 bytes
Attachment (time.patch): text/x-patch, 902 bytes
Attachment (unused_value.patch): text/x-patch, 513 bytes
_______________________________________________
libdispatch-dev mailing list
libdispatch-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev

Gmane