From owner-freebsd-alpha Tue Feb 26 13:24:49 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mail3.registeredsite.com (mail3.registeredsite.com [64.224.9.12]) by hub.freebsd.org (Postfix) with ESMTP id 8282237B400 for ; Tue, 26 Feb 2002 13:24:46 -0800 (PST) Received: from mail.optima-hyper.com ([216.2.34.221]) by mail3.registeredsite.com (8.11.6/8.11.4) with ESMTP id g1QKTRx25333 for ; Tue, 26 Feb 2002 15:29:28 -0500 Received: from hqwkst77 [216.2.34.221] by mail.optima-hyper.com (SMTPD32-6.06) id ACFA78C200C0; Tue, 26 Feb 2002 16:24:10 -0500 Reply-To: From: "Yuri Victorovich" To: Subject: RE: "unexpected machine check" on AS1000A Date: Tue, 26 Feb 2002 16:34:52 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Nope, seems that reseating, cleaning, rotating SIMMs doesn't help. Is it a way to find which SIMM exactly causes the problem? By those values that it loggs on "unexpected machine check" crash? Yuri ================================================================ Time to reseat the SIMMs. Had things like this on a AS1000A at work. Half-baked nonbrand simms also tend to give problems on Noritake. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message