Subject: Coda on NetBSD 1.4.1/KAME/sparc
To: None <tech-pkg@netbsd.org, current-users@netbsd.org,>
From: None <ww@shadowfax.styx.org>
List: port-sparc
Date: 05/29/2000 22:42:45
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Hello,

I have been  trying to get coda to work on  NetBSD/sparc 1.4.1 (out of
the  KAME  distribution --  it  seems the  most  stable  for IPv6  and
IPSec). I'm using coda-5.3.5 out  of the coda5_client directory in the
package tree.

1.4.1 seems to have support  for coda on certain architectures (i386),
but not on sparc. After adding  an entry for character major number 62
in sys/arch/sparc/sparc/conf.c  I can get  venus to run, but  it dumps
core fairly early on. It seems that venus disables core dumps, so I'll
probably  have to  modify it  to disable  this to  get  more debugging
information. For now, the last lines of a ktrace produce:

   215 venus    CALL  open(0x15a5a6,0x2,0)
   215 venus    NAMI  "/dev/cfs0"
   215 venus    RET   open 3
   215 venus    CALL  write(0x3,0xeffff818,0xc)
   215 venus    GIO   fd 3 wrote 12 bytes
       "\0\0\0\^Y\0\0\0\0\M-o\M^?\M-x\M^@"
   215 venus    RET   write 12/0xc
   215 venus    CALL  close(0x3)
   215 venus    RET   close 0
   215 venus    CALL  break(0x177ffc)
   215 venus    RET   break 0
   215 venus    CALL  break(0x178ffc)
   215 venus    RET   break 0
   215 venus    CALL  gettimeofday(0x1771b4,0)
   215 venus    RET   gettimeofday 0
   215 venus    PSIG  SIGSEGV SIG_DFL
   215 venus    NAMI  "venus.core"

It seems  to open  /dev/cfs0 ok, but  then it mysteriously  cores some
time after doing a gettimeofday().

At first  glance, this doesn't  seem to be  a problem with  the kernel
driver,  so   I'm  wondering  if   anyone  has  seen   this  behaviour
before. I'll try digging in the coda  sources to see if I can find the
problem... 

Cheers,
- -w
- --
Will Waites \________
ww@shadowfax.styx.org\____________________________
Idiosyntactix Ministry of Research and Development\
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (OpenBSD)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>

iQEXAwUBOTMqoA4cK24IcAwYFAM1ZwP5AaG1bycvW82ofJ29Eg0AE7+PkHbZ3Rvj
6BvHr4LEzFrJhsICzLiJKbpS309vp87V2Esmi8aiz+h/ANJIhA7jCpObRBvNAqZ6
Dm1RhWyof7kW2twOXRoMuE7yKwXc0OTowrlunWTgQHOKXGWQbstLpuTyXLU6hZC6
xM04djYMyqoEAL9Dmz3kaZmPo57wAFPVPAeyLgbVGLZirBvDoOiT7EG4J7dYpoZR
vmkCbyHisl634dFRiRIDJEZO95P/u/kpPWnFLk3BQhWHzCp4vqx3ytgrnFZgLIoP
DKeIsZe7jMlmG/8tNafPt/8ehstLYx454SVxidtOSGNnD0pW7ZZnVJpO
=dM1N
-----END PGP SIGNATURE-----