Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!news.iastate.edu!davis From: davis@ee.iastate.edu (Jim Davis) Newsgroups: comp.unix.sysv386 Subject: Re: PANIC: Kernel mode trap Keywords: panic Message-ID: Date: 25 Dec 90 23:23:07 GMT References: <47590@apple.Apple.COM> Sender: news@news.iastate.edu (USENET News System) Distribution: na Organization: Iowa State University, Ames IA Lines: 34 erekose@apple.com (Erik Scheelke) writes: >I am looking for any information about the following panic that occurs >occasionally on my system: >PANIC: Kernel mode trap type 0x0000000e >Has anyone else every seen this? I am using Intel's version of AT&T Unix >System V 3.2.2. I have their TCP/IP and NFS installed also. The reason >I mention this is that there is a small correlation between when the panic >occurs and network traffic into (not out from tho...) the system. >Can anyone explain what causes a Kernel mode trap in general? Type 0x0e? >Thank you for any help! >Erik Scheelke I had the same type of trap with version 3.2.1. In my case, I think I didn't have enough stream data buffers allocated, so when network traffic got out of hand, the system crashed. You can check to see if this is a problem by running "crash" as root and typing "strstat". This will give you a list of stream buffers (by size) and what the high water mark is. The default was 384 buffers for the 64-byte and 128-byte buffers, and I gradually increased that to 1024 for each before it stopped crashing. Sometime later, I installed 3.2.2 and the system strated crashing again, so I'll have to do this again. Good Luck! Jim Davis davis@isuee1.ee.iastate.edu