mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Rick Warner <rick@microway.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: very strange issue with sata,<4G Ram, and ext3
Date: Thu, 05 May 2005 23:37:43 +0200	[thread overview]
Message-ID: <m364xxtkuw.fsf@defiant.localdomain> (raw)
In-Reply-To: <200504291045.58893.rick@microway.com> (Rick Warner's message of "Fri, 29 Apr 2005 10:45:58 -0400")

Rick Warner <rick@microway.com> writes:

> This morning, we tried updating to a newer pxelinux (3.07) and had the same 
> results.  We then tried using etherboot with a mknbi tagged image and also 
> had the same results.   Since we are getting the same problem on 3 different 
> motherboards with 2 different network adapters, I have not looked into 
> updating the boot rom on the nics.  Should I?

I remember I had memory corruption problems with an old version of
Etherboot few years ago. The machines were mostly AMD K6 based,
network cards were SMC EPIC100 (Etherpower II) and/or RTL 8139.

Memtest86 (downloaded with Etherboot) complained about random errors.
I think Linux didn't show any such illness.
This was Etherboot 4.something. Upgrading to 5.something fixed the
problem.

I suspect you're using Etherboot newer than 4.x though. I'd probably
give memtest86 loaded from network a try.
-- 
Krzysztof Halasa

  parent reply	other threads:[~2005-05-05 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 16:16 Rick Warner
2005-04-28 17:32 ` Rick Warner
2005-04-28 22:48 ` Alan Cox
2005-04-29 14:45   ` Rick Warner
2005-05-04 19:29     ` Rick Warner
2005-05-05 15:00       ` Alan Cox
2005-05-05 21:37     ` Krzysztof Halasa [this message]
2005-05-06 13:39       ` Rick Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m364xxtkuw.fsf@defiant.localdomain \
    --to=khc@pm.waw.pl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rick@microway.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®