Linux NFS development
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: Roger Heflin <rheflin@atipa.com>
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 09:56:37 +0200	[thread overview]
Message-ID: <20050610075637.GB5534@suse.de> (raw)
In-Reply-To: <EXCHG2003FbN4TZyabY000003d9@EXCHG2003.microtech-ks.com>

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

  reply	other threads:[~2005-06-10  7:56 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 [this message]
2005-06-10 13:15   ` Roger Heflin
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=20050610075637.GB5534@suse.de \
    --to=okir@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=rheflin@atipa.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