Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!snorkelwacker.mit.edu!thunder.mcrcim.mcgill.edu!insl!clyde.concordia.ca!ccu.umanitoba.ca!umbalnea
From: umbalnea@ccu.umanitoba.ca (Scott L. Balneaves)
Newsgroups: comp.unix.sysv386
Subject: Re: PANIC: Kernel mode trap
Keywords: panic
Message-ID: <1990Dec27.040638.9049@ccu.umanitoba.ca>
Date: 27 Dec 90 04:06:38 GMT
References: <47590@apple.Apple.COM>
Distribution: na
Organization: University of Manitoba, Winnipeg, Canada
Lines: 23

In article <47590@apple.Apple.COM> erekose@apple.com (Erik Scheelke) writes:
>I am looking for any information about the following panic that occurs
>occasionally on my system:

I work with SCO Unix v 3.2.2 where I work, so this may or may not be of help,
but...

An SCO box that we had was connected to a SUN network, and used as a gateway.
We found that we would get intermittant network crashes, and sometimes, the
whole SCO box would go down.  We finally found (after much hair pulling)
that the "Reccomended" TCP/IP STREAMS buffers we way too low.  Specifically,
the NSTREAMS kernal parameter, and the NBLK4092 and NBLK1024 parameters.

I don't know what you have to do to change these kernal parms on your system,
but I would suggest bumping them up by 20-30%, monitoring the system,
and then lowering the buffers that are not being used.  On SCO, there's
a system util. called crash (ADM) that allows you to look into the
kernal to see buffer allocations, etc.  If you have something like this
on your system, it may be invaluable.

Hope this helps!

Scott