Re: panic on HEAD

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:Ok, so I applied the patch.  After about 20 hours, the machine starting
:acting weird.  It would still ping, but I could not connect via ssh.  So,
:I went to the console.  I was able to enter username and password, and
:after that, nothing.  After about 5 minutes, I ctrl-alt-esc'd, and panic'd
:the machine.  The core and kernel is uploading to leaf: ~/public/*.2
:
:--Peter

    oops, sorry about that blank reply!

    Ok, from your dump it looks like the TCP thread on cpu #1 got stuck
    in the interrupt serializer but the serializer was in an unlocked
    state.  I found a bug in the serializer code that could result in
    the serializer not waking up waiters.

    Keep the first patch in place, and apply this patch in addition.

						-Matt

Index: lwkt_serialize.c
===================================================================
RCS file: /cvs/src/sys/kern/lwkt_serialize.c,v
retrieving revision 1.4
diff -u -r1.4 lwkt_serialize.c
--- lwkt_serialize.c	26 May 2005 09:10:10 -0000	1.4
+++ lwkt_serialize.c	9 Sep 2005 17:18:47 -0000
@@ -119,7 +119,7 @@
 	atomic_intr_cond_enter(&s->interlock, lwkt_serialize_sleep, s);
 	if (atomic_intr_handler_is_enabled(&s->interlock) == 0)
 	    func(arg);
-	atomic_intr_cond_exit(&s->interlock, lwkt_serialize_sleep, s);
+	atomic_intr_cond_exit(&s->interlock, lwkt_serialize_wakeup, s);
     }
 }