mazer@bek-owl.cns.caltech.edu (Jamie Mazer) (10/02/90)
One of our systems here, running RTU 5.0 is experiencing rather frequent and (thus far) unexplained crashes. In general, the crashes seem occur when medium-to-large x-clients are running, usually on NCD X-terminals. The console reports something like this: lomap: rmap overflow, lost 129-131 lomap: rmap overflow, lost 133-134 .... lomap: rmap overflow, lost 154-155 iomalloc going to sleep: size=0x3000 At this point the system is pretty mangled: I can log in on a tty-line and safely reboot the machine, but can't connect via an x-term or any other network connection, and I can't reload the network software without rebooting. Has anyone seen this? I can't find anything about it in the system manuals and we never had anything like this happen under version 4. I can reliably generate this crash with about 5 minutes of puttering around, so it's rather dangerous for us. Thanks for any help or advice, like what exactly the console error messages mean?? /Jamie \/ mazer@bek-owl.cns.caltech.edu \/ "I'm learning to live with \/ /\ JMazer@CALTECH.BITNET /\ a lot of things" - Darkman /\ Articles to: concurrent@soma.bcm.tmc.edu or uunet!soma.bcm.tmc.edu!concurrent Administrative stuff: concurrent-request@soma.bcm.tmc.edu Stan Barber, Moderator