[00:20:10] --- Simon has become available
[00:25:59] --- phalenor has left
[00:26:04] --- phalenor has become available
[00:31:08] --- Simon has left
[00:38:58] --- lama has become available
[03:13:30] --- jaltman/FrogsLeap has left: Disconnected
[03:15:43] --- jaltman/FrogsLeap has become available
[04:00:10] --- jaltman/FrogsLeap has left: Disconnected
[07:02:44] --- reuteras has left
[07:46:41] --- deason has become available
[08:22:56] --- lama has left
[11:01:47] --- rra has become available
[14:46:49] --- deason has left
[15:36:08] --- kula has become available
[18:45:52] --- rra has left: Disconnected
[19:00:50] <kaduk@mit.edu/barnowl> I reproduced the bonnie++ hang that GAWollman reported on
port-freebsd.
Interestingly, it is not immediate, but the process starts using less
and less CPU, presumably as the various kernel worker threads get hung
one by one.
[19:03:57] --- Russ has become available
[19:26:16] <kaduk@mit.edu/barnowl> Or maybe not.  The afsd threads are all ("all") in
afs_osi_sleep(&afs_brsDaemons), but the bonnie++ thread is in
ObtainDCacheForWriting: afs_osi_Sleep(&afs_WaitForCacheDrain).
[22:01:26] --- Russ has left: Disconnected
[22:17:35] --- reuteras has become available
[22:29:20] --- steven.jenkins has left
[22:30:41] --- Russ has become available
[22:32:03] --- steven.jenkins has become available
[23:04:25] --- steven.jenkins has left
[23:38:04] --- steven.jenkins has become available
[23:43:00] --- steven.jenkins has left
[23:44:33] --- steven.jenkins has become available
[23:59:22] --- Russ has left: Disconnected