[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/47069: posix_spawn/t_spawnattr locks up the system
The following reply was made to PR kern/47069; it has been noted by GNATS.
From: Julio Merino <julio%meroh.net@localhost>
To: Christos Zoulas <christos%zoulas.com@localhost>
Cc: gnats-bugs%netbsd.org@localhost, martin%netbsd.org@localhost,
Subject: Re: kern/47069: posix_spawn/t_spawnattr locks up the system
Date: Thu, 18 Oct 2012 18:29:30 -0400
On Wed, Oct 17, 2012 at 8:21 PM, Christos Zoulas
> On Oct 17, 8:16pm, julio%meroh.net@localhost (Julio Merino) wrote:
> -- Subject: Re: kern/47069: posix_spawn/t_spawnattr locks up the system
> | On Sun, Oct 14, 2012 at 4:30 PM, Christos Zoulas
> <christos%zoulas.com@localhost> wrote:
> | > Try defining FULL ok kern_mutex.c for powerpc.
> | Nope, nothing. I'm assuming that you meant to just "#define FULL" in
> | kern_mutex.c? I also tried enabling LOCKDEBUG and DIAGNOSTIC.
> | However, I noticed one more data point: when the system locks up, one
> | of the t_spawnattr processes is in RUN state and the other in STOP
> | state. Both show 0K of memory in the SIZE and RES columns of top.
> Fine, but the whole problem could be a mutex issue. Let's try this
> one first.
By "this one" you meant defining FULL, LOCKDEBUG or DIAGNOSTIC? I
already tried them all and none provided any further details :-/
Julio Merino / @jmmv
Main Index |
Thread Index |