marcs@crplabs.UUCP (Marc Snyder) (06/05/89)
Netlanders:
I seem to have a problem. Brief background: I am administering
an IBM-AT with a 386 motherboard running at approximately 20MHz. The
software is SCO Xenix 2.3.1. Recently, the system crashed (on two separate
occasions) and these messages were placed into the /usr/adm/messages file:
>TRAP 0000000E in SYSTEM, error code=00000000
> eax=0001A880, ebx=0600072C, ecx=00000000, edx=000098D5
> esi=00000000, edi=F0009723, ebp=06000730, fl=00010282
> uds=00000018, es=06000018, fs=0001003F, gs=0008003F, tr=00000100
> pc=06000020:0001C775, ksp=06000704
>
>kernel: PANIC: non-recoverable kernel page fault
>TRAP 0000000E in SYSTEM, error code=00020000
> eax=00019B60, ebx=0600072C, ecx=060007B4, edx=000098D5
> esi=00000000, edi=F0009723, ebp=06000730, fl=00010282
> uds=00470018, es=00000018, fs=0000003F, gs=081C003F, tr=00000100
> pc=00000020:0001C775, ksp=06000704
>
>kernel: PANIC: non-recoverable kernel page fault
I would assume that this is some type of memory (RAM) fault --
although I may be completely off base. I was wondering if there was some
way to make sense of these messages, and figure out what the problem
is. I would appreciate any help, and will say thanks in advance.
--
Marc Snyder -- System Administrator
Ciba-Geigy Corporation Ardsley, NYjlg@odicon.UUCP (John L. Grzesiak) (06/12/89)
In article <420@crplabs.UUCP>, marcs@crplabs.UUCP (Marc Snyder) writes: > Netlanders: > software is SCO Xenix 2.3.1. Recently, the system crashed (on two separate > occasions) and these messages were placed into the /usr/adm/messages file: > > >kernel: PANIC: non-recoverable kernel page fault > >kernel: PANIC: non-recoverable kernel page fault > > I would assume that this is some type of memory (RAM) fault -- > although I may be completely off base. I was wondering if there was some > > Marc Snyder -- System Administrator > Ciba-Geigy Corporation Ardsley, NY S.C.O. knows about this one, at least two of their tech support people told me that this is a problem with certain 386 computers. I had this problem with a 386 system we were evaluating. As soon as the system went out of paging and into swapping it started. Drove me nuts is all it did! It started with page to frame errors (and vice versa) . That one did prove to be a memory error, but after solving the memory problem we starting getting the exact errors you are having. The cure was 1 part easy and 2 parts tough. 1) Upgrade to 2.3.2. (S.C.O. says the paging algoritym in 2.3.1. is buggy) 2) If this doesn't work - throw the system to a DOS application and get another box for XENIX . (This is what we had to do). 3) If this is a bearer of BAD NEWS - I'm sorry , but I could'nt figure a way around it. (I think I tried everything in the book , from slowing the system down to increasing i/o speed with a ESDI drive, to using large amount of kernal buffer space) ((THE increased buffers did help , but did not remove the problem , just cut the frequency). +-------------------------+---------------------------------+ + John L Grzesiak | "Genius is the output of + + 47 Spring Street | a mind twisted beyond + + Wallingford Ct 06492 | normal recognition" + + | + + !yale!spock!odicon!jlg | Omega Dynamics - Wallingford Ct + + | + +-------------------------+---------------------------------+
mhlevy@sbee.sunysb.edu (Mark Levy) (06/12/89)
I have seen similar problems when the computer is unable to swap or
page, because it simply runs out of memory. It may be that you don't
have enough memory installed for what you're trying to do. I demonstrated
this fault to my boss when he insisted that 2 sessions of VP/ix would run
on a system with 2MB of memory!
Mark
--
~~~~~~~~~ Disclaimer??? We don't need no stinkin' disclaimer!!! ~~~~~~
Mark Levy { mhlevy@sbccvm.BITNET } % Debbie Gibson is pregnant, with
{ mhlevy@sbee.sunysb.edu } % my two headed love child....
{ mhlevy@ccvm.sunysb.edu } % Mojo Nixonadnan@sgtech.UUCP (Adnan Yaqub) (06/13/89)
In article <420@crplabs.UUCP> marcs@crplabs.UUCP (Marc Snyder) writes: I seem to have a problem. Brief background: I am administering an IBM-AT with a 386 motherboard running at approximately 20MHz. The software is SCO Xenix 2.3.1. Recently, the system crashed (on two separate occasions) and these messages were placed into the /usr/adm/messages file: >TRAP 0000000E in SYSTEM, error code=00000000 > eax=0001A880, ebx=0600072C, ecx=00000000, edx=000098D5 > esi=00000000, edi=F0009723, ebp=06000730, fl=00010282 > uds=00000018, es=06000018, fs=0001003F, gs=0008003F, tr=00000100 > pc=06000020:0001C775, ksp=06000704 > >kernel: PANIC: non-recoverable kernel page fault >TRAP 0000000E in SYSTEM, error code=00020000 > eax=00019B60, ebx=0600072C, ecx=060007B4, edx=000098D5 > esi=00000000, edi=F0009723, ebp=06000730, fl=00010282 > uds=00470018, es=00000018, fs=0000003F, gs=081C003F, tr=00000100 > pc=00000020:0001C775, ksp=06000704 > >kernel: PANIC: non-recoverable kernel page fault I would start by doing # nm -n /xenix | pg and find out what was running when the crash occurred (i.e., what exactly is at location 1C775). This clue may point you to the problem. -- Adnan Yaqub Star Gate Technologies, 29300 Aurora Rd., Solon, OH, USA, +1 216 349 1860 ...uunet!abvax!sgtech!adnan