From: Martin Hierling <martin.hierling@fh-luh.de>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.16.18 with general protection fault, perhaps nfsd
Date: Thu, 1 Jun 2006 13:55:23 +0200 [thread overview]
Message-ID: <20060601115523.GC4561@cc.fh-luh.de> (raw)
In-Reply-To: <17534.12716.972995.289153@cse.unsw.edu.au>
Hi,
> I recommend running memtest86 and replacing the bad memory.
will do this tonight, answer tomorrow.
regards Martin
--
----------------------------------------------------------------
Ensign Pillsbury: He's bread Jim!
----------------------------------------------------------------
next prev parent reply other threads:[~2006-06-01 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 16:47 Kernel 2.6.16.18 with general protection fault, perhaps nfsd Martin Hierling
2006-05-31 20:47 ` J. Bruce Fields
2006-06-01 11:53 ` Martin Hierling
2006-06-05 17:52 ` J. Bruce Fields
2006-06-06 7:39 ` Martin Hierling
2006-06-06 13:07 ` J. Bruce Fields
2006-06-01 0:15 ` Neil Brown
2006-06-01 11:55 ` Martin Hierling [this message]
2006-06-03 16:44 ` Martin Hierling
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=20060601115523.GC4561@cc.fh-luh.de \
--to=martin.hierling@fh-luh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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