[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/24829 (panic: postsig action on SMP system)
The following reply was made to PR kern/24829; it has been noted by GNATS.
From: Jarle Greipsland <jarle%uninett.no@localhost>
To: gnats-bugs%NetBSD.org@localhost, dsl%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
Subject: Re: kern/24829 (panic: postsig action on SMP system)
Date: Tue, 01 Dec 2009 16:48:52 +0100 (CET)
> Synopsis: panic: postsig action on SMP system
> State-Changed-From-To: open->feedback
> State-Changed-By: dsl%NetBSD.org@localhost
> State-Changed-When: Sat, 28 Nov 2009 15:36:13 +0000
> Does the problem happen with the 1:1 thread library?
> I think there were unfixable issues with PTHREAD_CONCURRENCY and
> the old SA threads.
It seems like the panic has gone away. I tried various
combination of http_load and start/stop-sequences of the web
server, and the kernel did not panic. I think we should consider
the kernel problem fixed.
Apache still does not behave well, though. Some threads seems to
end up in a state where they continuously consume CPU time.
Typically for each run of http_load, a handful of threads ended
up in this state. Alas, my attempt at debugging the stuff with
gdb did not succeed. I could not get gdb to print out
thread-specific information (info threads). So, whether the bug
lies within the Apache software or NetBSD's run time libraries is
Main Index |
Thread Index |