summaryrefslogtreecommitdiff
path: root/open_issues/ext2fs_deadlock.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2010-10-28 00:46:15 +0200
committerThomas Schwinge <thomas@schwinge.name>2010-10-28 00:46:15 +0200
commit57e53f663b3b2acd716a37c4a15f033b2ff0c34e (patch)
treecf9c9cab1644e3cacade6594e339055b578e82f3 /open_issues/ext2fs_deadlock.mdwn
parent803bdc6b58f4d7718aba5a93e3b8a9d0b119fe02 (diff)
open_issues/ext2fs_deadlock: Samuel had a quick look.
Diffstat (limited to 'open_issues/ext2fs_deadlock.mdwn')
-rw-r--r--open_issues/ext2fs_deadlock.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/open_issues/ext2fs_deadlock.mdwn b/open_issues/ext2fs_deadlock.mdwn
index 4c5cdb24..369875fe 100644
--- a/open_issues/ext2fs_deadlock.mdwn
+++ b/open_issues/ext2fs_deadlock.mdwn
@@ -43,3 +43,13 @@ accessing it, no matter whether noninvasive mode or not. (Didn't have time to
pull the information out of the process' memory manually (how to do that,
anyways?), and also didn't have time to continue with debugging GDB itself, but
this sounds like a [[!taglink open_issue_gdb]]...)
+
+---
+
+IRC, #hurd, 2010-10-27
+
+ <youpi> thread 8 hung on ports_begin_rpc
+ <youpi> that's probably where one could investigated first
+ <youpi> yes, a lot of threads are hung on that
+ <tschwinge> You mean 0x10b9488, right?
+ <youpi> yes