From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264294AbTLVCRD (ORCPT ); Sun, 21 Dec 2003 21:17:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264301AbTLVCRD (ORCPT ); Sun, 21 Dec 2003 21:17:03 -0500 Received: from fed1mtao02.cox.net ([68.6.19.243]:62922 "EHLO fed1mtao02.cox.net") by vger.kernel.org with ESMTP id S264294AbTLVCRB (ORCPT ); Sun, 21 Dec 2003 21:17:01 -0500 Date: Sun, 21 Dec 2003 18:17:00 -0800 From: "Barry K. Nathan" To: Maciej Zenczykowski Cc: Arnaud Fontaine , Mike Fedyk , Marcelo Tosatti , linux-kernel@vger.kernel.org Subject: Re: Oops with 2.4.23 Message-ID: <20031222021659.GA4857@ip68-4-255-84.oc.oc.cox.net> References: <20031219224402.GA1284@scrappy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Dec 20, 2003 at 12:35:24AM +0100, Maciej Zenczykowski wrote: > you did run memtest for a minimum dozen hours? sometimes it takes that > long to find errors... On one machine (with a bad power supply, as it turned out) it took memtest86 almost 18 hours to report an error. So 12 hours isn't enough either. (On a related note, one machine that I tested with mprime's Torture Test took I think close to 43 hours to show a failure. In that case I don't know if the failure was the CPU or the motherboard, because in the end both failed on that system.) -Barry K. Nathan