All of lore.kernel.org
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
	linux-mips@vger.rutgers.edu
Subject: Memory corruption on Indy
Date: Mon, 15 Feb 1999 00:27:46 +0100	[thread overview]
Message-ID: <19990215002746.C644@uni-koblenz.de> (raw)

Hi all,

since quite some time I've tried to find a memory corruption bug on my Indy.
I now suspect that the actual cause is a hardware problem and a recent
IRIX kernel core dump supports that theory.  Just to be on the safe side,
could people running Linux on Indys please run something like

  find / -fstype ext2 -type f | xargs md5sym

several times and compare the obtained output.  Do they differ in any
unexplainable way?

Thanks,

  Ralf

             reply	other threads:[~1999-02-14 23:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-14 23:27 ralf [this message]
1999-02-15  0:32 ` Memory corruption on Indy Thomas Bogendoerfer
1999-02-15  1:05   ` ralf
     [not found]   ` <Pine.SOL.3.95.990216085734.25445A-100000@ecom5>
1999-02-22 22:27     ` R4600 MIPS/Linux ralf
     [not found]       ` <Pine.SOL.3.95.990225231407.26058D-100000@ecom5>
1999-02-27 16:53         ` Kernel support for R4600 MIPS ralf
1999-02-27 17:45           ` Warner Losh

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=19990215002746.C644@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.