From owner-freebsd-alpha Fri Feb 4 6:53:34 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by builder.freebsd.org (Postfix) with ESMTP id 334F34187 for ; Fri, 4 Feb 2000 06:53:23 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id JAA07686; Fri, 4 Feb 2000 09:53:35 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA75292; Fri, 4 Feb 2000 09:53:01 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 4 Feb 2000 09:53:00 -0500 (EST) To: Rob Harris Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: help! In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14490.59011.291428.147695@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rob Harris writes: > > I'm running a mission critical app on a box, using FreeBSD 4.0 SNAP > 01012000. I keep getting a panic. > > Also, I've seen this a lot before on one of our LX164s. > <..> > Feb 4 01:58:16 ds10-mc /kernel: Warning: received processor correctable > error. > Feb 4 02:08:17 ds10-mc last message repeated 4 times <..> > error. > Feb 4 05:48:04 ds10-mc /kernel: > Feb 4 05:48:04 ds10-mc /kernel: unexpected machine check: > Feb 4 05:48:04 ds10-mc /kernel: > Feb 4 05:48:04 ds10-mc /kernel: mces = 0x1 > Feb 4 05:48:04 ds10-mc /kernel: vector = 0x670 Sounds like hardware problems to me. From the vector 670 ( = processor incorrectable error) and the previous messages, I suspect you have bad memory. I suspect the correctable errors are memory corruption errors which can be fixed by the ECC bits, and the panic is corruption so bad that it cannot be fixed by the ECC bits. Try yanking simms until the errors stop. Of course, it could also be a problem with the motherboard (bcache) or the CPU (icache/dcache).. You might also try to remove any excess dust buildup & make sure the box is properly cooled. Good luck, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message