From 5bd36fdff16871eb7d06fc26cac07e7f2703432b Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 29 Nov 2012 01:33:22 +0100 Subject: IRC. --- open_issues/fork_deadlock.mdwn | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) (limited to 'open_issues/fork_deadlock.mdwn') diff --git a/open_issues/fork_deadlock.mdwn b/open_issues/fork_deadlock.mdwn index 6b90aa0a..c1fa9208 100644 --- a/open_issues/fork_deadlock.mdwn +++ b/open_issues/fork_deadlock.mdwn @@ -63,3 +63,34 @@ Another one in `dash`: stopped = 1 i = 6 [...] + + +# IRC, OFTC, #debian-hurd, 2012-11-24 + + the lockups are about a SIGCHLD which gets lost + ah, ok + which makes bash spin + is that happening more often recently, or it's just something i + just noticed? + it's more often recently + where "recently" means "some months ago" + I didn't notice exactly when + i see + it's at most since june, apparently + (libtool managed to build without a fuss, while now it's a pain) + (libtool building is a good test, it seems to be triggering quite + reliably) + + +## IRC, freenode, #hurd, 2012-11-27 + + we also have the shell wait issue + it's particularly bad on libtool calls + the libtool package (with testsuite) is a good reproducer :) + the symptom is shell scripts eating CPU + busy-waiting for a SIGCHLD which never gets received + that could be what i got + + http://www.gnu.org/software/hurd/microkernel/mach/gnumach/memory_management.html + last part + perhaps watch has the same issue as the shell, yes -- cgit v1.2.3