From owner-freebsd-alpha Tue Feb 26 13:29:26 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7FB4E37B400 for ; Tue, 26 Feb 2002 13:29:19 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA18047; Tue, 26 Feb 2002 16:29:19 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g1QLSnN19529; Tue, 26 Feb 2002 16:28:49 -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 Message-ID: <15483.65041.7582.593390@grasshopper.cs.duke.edu> Date: Tue, 26 Feb 2002 16:28:49 -0500 (EST) To: Cc: Subject: RE: "unexpected machine check" on AS1000A In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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 Yuri Victorovich writes: > 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? > Yes & we could also log more information for the correctable errors too. However, doing this requires having sufficient documentation, which I don't think we do. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message