Folks,

I am playing with coda on an amd64 machine running a fairly recent
version of NetBSD-current (running 64bit for what it is worth).  The
version of coda is 6.9.1 and was built from the NetBSD pkgsrc (though
I had to tweak things to get it to build).  I set up coda and started
everything up, started up venus on the same machine and was able to
see my volume fine - do a clog and was able to create a file in the
volume.  It all looked quite good but some minutes later my coda
volume disappeared, venus was in a zombie state.  I rebuilt venus to
include debug and when I attach with gdb a backtrace gives:

(gdb) bt
#0  0x00007f7ffc92ff92 in _sys___sigsuspend14 () from /usr/lib/libc.so.12
#1  0x0000000000462631 in SigChoke (sig=10) at sighand.cc:251
#2  <signal handler called>
#3  0x00000000004305dd in MarinerLog (
    fmt=0x48d460 "cache::EndStatusWalk [%d]\n   [%d, %d, %d, %d] [%d, %d, %d] [%d, %d, %1.1f]%s") at mariner.cc:243
#4  0x00000000004293b9 in hdb::StatusWalk (this=0x508f3710, vp=0x611600, 
    TotalBytesToFetch=0x450a3f34, BytesFetched=<value optimized out>)
    at hdb.cc:664
#5  0x000000000042953b in hdb::Walk (this=0x508f3710, m=<value optimized out>, 
    local_id=0) at hdb.cc:893
#6  0x0000000000429e7b in HDBDaemon () at hdb_daemon.cc:121
#7  0x0000000000456ad0 in VprocPreamble (arg=<value optimized out>)
    at vproc.cc:148
#8  0x00007f7ffd204687 in Create_Process_Part2 () from /usr/pkg/lib/liblwp.so.2
#9  0x00007f7ffd205249 in L1 () from /usr/pkg/lib/liblwp.so.2
#10 0xfffefdfcfbfaf9f8 in ?? ()
Cannot access memory at address 0x450a4000
(gdb) 

the last bit in the venus.log is:

[ T(01) : 0108 : 23:09:30 ] BeginRvmTruncate (2, 33744, I)
[ T(01) : 0108 : 23:09:30 ] EndRvmTruncate

[ H(07) : 0001 : 23:10:11 ] HDBDaemon just woke up
[ H(07) : 0001 : 23:10:11 ] userent::Connect: ViceGetAttrPlusSHA(siren)
[ H(07) : 0001 : 23:10:11 ] userent::Connect: ViceGetAttrPlusSHA() -> 22
[ H(07) : 0001 : 23:10:11 ] userent::Connect: VGAPlusSHA_Supported -> 1
[ H(07) : 0001 : 23:10:11 ] *****  FATAL SIGNAL (10) *****

the strange thing is the logs show that venus handled the horde daemon
wakeup fine previously.  Anyone have any ideas?

-- 
Brett Lymn