On Sun, May 01, 2005 at 06:14:04PM +0000, tron@netbsd.org wrote:
> Synopsis: Xserver triggers threading problem
> 
> Responsible-Changed-From-To: xsrc-manager->port-sparc64-maintainer
> Responsible-Changed-By: tron@netbsd.org
> Responsible-Changed-When: Sun, 01 May 2005 18:14:03 +0000
> Responsible-Changed-Why:
> 1.) XFree86's signal handling code does *not* cause this. It will not
>     unblock SIGIO from a the SIGIO signal handler.

I just read the code again, it sure looks like it does to me.
the call stack in the initial PR comments looks like it could really happen.


> 2.) The X11 server is stuck in "libpthread" also it is not linked against
>     that library which is *really* suspicious.

this I have no explanation for.



> 3.) Even if XFree86 is completely broken it should not lock up the kernel.

true.


so this is really 3 bugs:

(1) Xserver manipulates signal state in a signal handler (common).
(2) Xserver is somehow calling libpthread functions (common? sparc64? unclear).
(3) pthreads are still kinda broken on sparc64 (sparc64).


-Chuck



> I'm moving this bug to category port-sparc64 because that's the platform
> it has been observered on. And that platform has unfortunately a history
> of bugs in the SA code.
> 
> 
> State-Changed-From-To: feedback->open
> State-Changed-By: tron@netbsd.org
> State-Changed-When: Sun, 01 May 2005 18:14:03 +0000
> State-Changed-Why:
> Martin Husemann provided information about the X server.
> 
>