Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!ogicse!zephyr.ens.tek.com!tektronix!nosun!qiclab!m2xenix!quagga!ucthpx!oct1!aim1!deon
From: deon@aim1.uucp (Deon Botha)
Newsgroups: comp.unix.sysv386
Subject: SCO 3.2.0 Panic: svirtophys not found.
Message-ID: <1990Nov17.194220.477@aim1.uucp>
Date: 17 Nov 90 19:42:20 GMT
Organization: Aztec Info Mngmnt
Lines: 31

We are running SCO System/386 on a Mylex i80486-33 board, 16Mb RAM, a MYLEX
EISA SCSI controller and Maxtor drive. Under light loads the system runs fine,
it ran for 3 weeks during porting of applications and initial installation.
As the number of logged users grew to +- 23 users running intensive
COBOL applications under RM-Cobol, a kernel panic with message: "svirtophys -
not found" is reported and the core is dumped. Often a pstat or ps -ef
will cause it, but it has happened on it's own. svirtophys seems to be a
memory managment macro used during paging..this was deduced by examining it's
occurences in /usr/include/sys/immu.h.

If a "nm /unix | grep svirtophys" is run, it is found in the namelist, defined
as external. The Mylex people advised that a known problem exists in 2.3.0
and does not occur under Open Destop. The SLS199 fix does not fix this. I
am in the process of installing ODT for verification. SCO hot-line
replied that similiar problems have been reported under Ingres, and I am 
awaiting further advice.

An upgrade to the new 3.2.2 is not possible as the Mylex SCSI controller
drivers are pending.

Any pointers or tales of similiar woe will be greatly appreciated.
.............................................................
Deon Botha                            :Tel: +27 (21) 419-2690      
Aztec Information Management          :Fax: +27 (21) 21-1040
deon@aim1.UUCP (..uunet!ddsw1!olsa99!oct1!aim1!deon)
--