Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!dog.ee.lbl.gov!nosc!humu!pegasus!pinhead!todd
From: todd@pinhead.pegasus.com (Todd Ogasawara)
Newsgroups: comp.unix.sysv386
Subject: panic: RAM problem or something else?
Keywords: ISC 2.2, Everex 386/25, parity error
Message-ID: <1991May08.185945.6963@pinhead.pegasus.com>
Date: 8 May 91 18:59:45 GMT
Organization: Hawaii Medical Service Association
Lines: 35

One of my UNIX boxes crashed the other day with the following panic message
on the console.

	FATAL: Parity error on motherboard
	PANIC: Parity error at address 0x007D8BCA
	DEBUGGER ; ebp ; 0x0E0000DB4

The system is configured as follows:

	Everex Step 386/25, 8M RAM, 25MHz 80387
	Everex VGA board
	Everex ESDI hard disk controller
	Everex Serial/Parallel board
	Wangtek tape drive & controller
	Digiboard PC/16i
	Cleo Communications 3270 PC/XL U/X
	Interactive UNIX 2.2 (System V/386 R3)

When I rebooted the system, it passed the little POST RAM test for all
8M. UNIX seemed to come up clean after cleaning up the disk with fsck a
bit. The system seems stable so far. I am considering shutting down UNIX
and running some DOS-based RAM checkers. But, I thought I'd check
collective net wisdom before taking any action. I.e., is it really a RAM
problem or am I seeing some kind of interaction? I haven't added any new
hardware or made any new kernel modifications in about two months. The only
thing I did recently (about two weeks ago) was to load software onto the
Cleo 3270 board's onboard RAM.

BTW. The system has been up contiuously for about three months without
any other problems noted.

-- 
Todd Ogasawara ::: Hawaii Medical Service Association
Internet       ::: todd@pinhead.pegasus.com
Telephone      ::: (808) 536-9162 ext. 7