From: "Roger Heflin" <rheflin@atipa.com>
To: "'Olaf Kirch'" <okir@suse.de>
Cc: <nfs@lists.sourceforge.net>
Subject: RE: NFS crash on Suse, any ideas on which normal nfs patch could be a cause/fix?
Date: Fri, 10 Jun 2005 08:15:08 -0500 [thread overview]
Message-ID: <EXCHG2003PNXRPmcarc00000406@EXCHG2003.microtech-ks.com> (raw)
In-Reply-To: <20050610075637.GB5534@suse.de>
The other three don't do this, so there may just be something
about this machine that is otherwise wrong, so this error may
not be from this problem, though it is odd given that the machine
does not exhibit this message with any other tests.
We know what bad ram/bad cpu looks like, the machines all have ECC,
and are getting no ecc errors, and they pass several days of running
a intensive memory/cpu program with no ecc errors, no crashes outside
of using NFS.
We also have never seen a MCE with a actual kernel routine listed
off to the side like that, and we have seen at least 100+ MCE's of
other sorts, and have fixed them by replacing ram or cpus.
Roger
> -----Original Message-----
> From: Olaf Kirch [mailto:okir@suse.de]
> Sent: Friday, June 10, 2005 2:57 AM
> To: Roger Heflin
> Cc: nfs@lists.sourceforge.net
> Subject: Re: [NFS] NFS crash on Suse, any ideas on which
> normal nfs patch could be a cause/fix?
>
> On Thu, Jun 09, 2005 at 01:50:13PM -0500, Roger Heflin wrote:
> > The kernel crash message was:
> >
> > CPU 0: Machine Check Exception: 4 Bank 4: f60da00100000813
> > RIP !INEXACT! 10:<ffffffff8022fae2> {copy_user_generic_c0x8/0x26}
> > TSC 3d101af6bf756 ADDR 4304010
> > Kernel panic: Machine check
>
> This is not an NFS bug, it's a machine check exception. Your
> machines have bad RAM it seems.
>
> Olaf
> --
> Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
> okir@suse.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
>
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-06-10 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 18:50 NFS crash on Suse, any ideas on which normal nfs patch could be a cause/fix? Roger Heflin
2005-06-10 7:56 ` Olaf Kirch
2005-06-10 13:15 ` Roger Heflin [this message]
2005-06-10 20:53 ` Roger Heflin
2005-06-14 11:06 ` Olaf Kirch
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=EXCHG2003PNXRPmcarc00000406@EXCHG2003.microtech-ks.com \
--to=rheflin@atipa.com \
--cc=nfs@lists.sourceforge.net \
--cc=okir@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