From owner-freebsd-hackers  Sat Oct 14 22:31:45 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id WAA03135
          for hackers-outgoing; Sat, 14 Oct 1995 22:31:45 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA03130
          for <freebsd-hackers@freebsd.org>; Sat, 14 Oct 1995 22:31:42 -0700
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id WAA18454; Sat, 14 Oct 1995 22:31:41 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id WAA03953; Sat, 14 Oct 1995 22:31:22 -0700
Message-Id: <199510150531.WAA03953@corbin.Root.COM>
To: Ade Barkah <mbarkah@hemi.com>
cc: freebsd-hackers@freebsd.org
Subject: Re: what is... kernel trap 19? 
In-reply-to: Your message of "Sat, 14 Oct 95 23:11:14 MDT."
             <199510150511.XAA00283@hemi.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sat, 14 Oct 1995 22:31:21 -0700
Sender: owner-hackers@freebsd.org
Precedence: bulk

>Occasionally, one of our servers die with a kernel trap 19:
>
>NMI ... going to debugger
>Kernel: type 19 trap, code=0
>stopped at
>   _copyout+0x35:  repe     movsl (%esi), %es: (%edi)

   NMI's are usually caused by memory parity errors. It sounds like you've
either got a bad SIMM or you have the timing (wait states) set incorrectly.

-DG