deon@aim1.uucp (Deon Botha) (11/18/90)
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) --
paul@tetrauk.UUCP (Paul Ashton) (11/24/90)
> 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. We are developing an OLTP application that uses all 16 Meg of memory, causes up to 8 Meg of swapping, makes extensive use of ipc resources including 2.5 Meg shared memory on a Compaq 386/20e with ODT 1.0. After said usage we get the svirtophys panic when using the tape drive unless we reboot first. Before you ask, we do intend to use a bigger machine soon :-) -- Paul