We have a NT 4.01 PC running Hummingbird NFS Maestro v. 6.01. Every
time it tries to mount our Alpha 4/166 runnig OSF1 V3.2 the following
happens:
Mar 18 12:39:50 icis vmunix: fh3tovp: bad length: 0
Mar 18 12:39:50 icis vmunix:
Mar 18 12:39:50 icis vmunix: trap: invalid memory read access from kernel mode
Mar 18 12:39:50 icis vmunix:
Mar 18 12:39:50 icis vmunix: faulting virtual address: 0x0000000054a865cc
Mar 18 12:39:50 icis vmunix: pc of faulting instruction: 0xfffffc0000425960
Mar 18 12:39:50 icis vmunix: ra contents at time of fault: 0xfffffc000041b0ec
Mar 18 12:39:50 icis vmunix: sp contents at time of fault: 0xffffffff85b27488
Mar 18 12:39:50 icis vmunix:
Mar 18 12:39:50 icis vmunix: panic (cpu 0): kernel memory fault
Mar 18 12:39:50 icis vmunix: syncing disks... done
Mar 18 12:39:50 icis vmunix: DUMP.prom: dev SCSI 0 6 0 0 0 0 0, block 131072
Mar 18 12:39:50 icis vmunix: DUMP.prom: dev SCSI 0 6 0 0 0 0 0, block 131072
Mar 18 12:39:50 icis vmunix: _at_
I've located fh3tovp to /usr/sys/BINARY/nfs3_server.o. Is the zero
length a bug in Hummingbird or OSF1 3.2 and does anyone know how to
avoid it; are there e.g. any parameters one can set for NFS?
Unfortunately company politics won't allow the obvious solution to run
Samba instead... The other obvious solution is to upgrade to OSF1 4.0D
and hope that it solves the problem but it would be nice to know...
/Jonas
______________________________________________________________________
Jonas Linde init ab jonas_at_init.se www.init.se/~jonas/ +46-707-492496
Received on Wed Mar 18 1998 - 15:39:03 NZST