aboutsummaryrefslogtreecommitdiff
path: root/open_issues/fork_deadlock.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/fork_deadlock.mdwn')
-rw-r--r--open_issues/fork_deadlock.mdwn35
1 files changed, 32 insertions, 3 deletions
diff --git a/open_issues/fork_deadlock.mdwn b/open_issues/fork_deadlock.mdwn
index 1b8575c4..f8bf936e 100644
--- a/open_issues/fork_deadlock.mdwn
+++ b/open_issues/fork_deadlock.mdwn
@@ -3373,6 +3373,35 @@ Thread 1 (Thread 9076.1):
$8 = (struct hurd_sigstate *) 0x121a008
-# VI
-
-[[!message-id "877govry7a.fsf@kepler.schwinge.homeip.net"]]
+# IRC, OFTC, #debian-hurd, 2012-11-24
+
+ <youpi> the lockups are about a SIGCHLD which gets lost
+ <pinotree> ah, ok
+ <youpi> which makes bash spin
+ <pinotree> is that happening more often recently, or it's just something i
+ just noticed?
+ <youpi> it's more often recently
+ <youpi> where "recently" means "some months ago"
+ <youpi> I didn't notice exactly when
+ <pinotree> i see
+ <youpi> it's at most since june, apparently
+ <youpi> (libtool managed to build without a fuss, while now it's a pain)
+ <youpi> (libtool building is a good test, it seems to be triggering quite
+ reliably)
+
+
+## IRC, freenode, #hurd, 2012-11-27
+
+ <youpi> we also have the shell wait issue
+ <youpi> it's particularly bad on libtool calls
+ <youpi> the libtool package (with testsuite) is a good reproducer :)
+ <youpi> the symptom is shell scripts eating CPU
+ <youpi> busy-waiting for a SIGCHLD which never gets received
+ <braunr> that could be what i got
+ <braunr>
+ http://www.gnu.org/software/hurd/microkernel/mach/gnumach/memory_management.html
+ <braunr> last part
+ <youpi> perhaps watch has the same issue as the shell, yes
+
+
+# [[!message-id "877govry7a.fsf@kepler.schwinge.homeip.net"]]