Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S268516AbRG3L4n>; Mon, 30 Jul 2001 07:56:43 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S268533AbRG3L4e>; Mon, 30 Jul 2001 07:56:34 -0400
Received: from bish.net ([208.139.225.12]:61327 "EHLO bish.net")
	by vger.kernel.org with ESMTP id <S268516AbRG3L4X>;
	Mon, 30 Jul 2001 07:56:23 -0400
Date: Mon, 30 Jul 2001 07:55:42 -0400 (EDT)
From: Mark <mark@bish.net>
Reply-To: Mark <mark@bish.net>
To: Jonathan Hudson <jonathan@daria.co.uk>
cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel version 2.4.7 compile errors (fwd)
In-Reply-To: <20010730094356.C74F210800@trespassersw.daria.co.uk>
Message-ID: <Pine.LNX.3.96.1010730075301.654G-100000@bish.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Original-Recipient: rfc822;linux-kernel-outgoing

NOTE: I'm not subscribed - please Cc: mark@bish.net

On Mon, 30 Jul 2001, Jonathan Hudson wrote:
>
>Dodgy RAM. Had the same problem some time ago. The machine would run
>memtest86 as long as you like, no problem. Compile a kernel and I'd
>get these bit errors. Reboot, powercycle, look at the file -- no
>problem, probably compile next time.
>
>Replacing the RAM fixed the problem.
>
>

I already replaced the RAM and did the power cycle.


------------------------------------------------------------------------
| Mark Bishop  (mark@bish.net)         |             Computer Engineer |
| 813.258.2390                         |             Network Engineer  |
| http://bish.net                      |          Embedded Programmer  |



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/