Path: utzoo!utgpu!watmath!uunet!ginosko!usc!rutgers!att!andante!ulysses!dptg!mtunb!jcm
From: jcm@mtunb.ATT.COM (was-John McMillan)
Newsgroups: unix-pc.general
Subject: NMI/Parity Error
Summary: Are having these recurringly?  If so, E-mail me
Keywords: 3B1 parity errors
Message-ID: <1626@mtunb.ATT.COM>
Date: 19 Aug 89 15:20:21 GMT
Reply-To: jcm@mtunb.UUCP (John McMillan)
Organization: AT&T ISL Middletown NJ USA
Lines: 28


I'm curious about a customer's reported level of problems -- well
beyond anything I've ever experienced, except with a few of my
MOST-experimental kernels ];-).  I'm polling to see if this
is hitting anyone else.

I'd appreciate E-mail (to: att!mtunb!jcm) if you:
	1) are having multiple PANIC crashes per week
	2) from	NMI/Parity Errors -- Where the right-3 *hpte digits vary
					and the right-3 BSR1 digits vary
	      Ie., I'm insensitive if you have REAL Parity Errors, Sorry ];-)
	3) while running 3.51 kernels.

It would speed things up if you include:
	a) Kernel version [a,c,c+...] and checksum [sum(1)];
	b) A list of hardware (combo cards, printers&port used...);
	c) Environment -- circuit protection, home/office, etc;
	d) Any interesting usage details -- heavy traffic, programs
		typically running at time of crash.
	e) A phone number -- which is unlikely to be used;
	f) An E-MAIL ADDRESS THAT REALLY WORKS, or dial-in info!
	
(Having muttered the above, note that in a just-previously posted
"follow-up" I mentioned that pre-UNIX3.51C+ kernel/combo software there
were vulnerabilities to RS-232-induced crashes -- mostly trap 4/trap 11
with garbage left in the PC [like address D8D26000].)

Thanks -- john mcmillan -- att!mtunb!jcm