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: Tue, 14 Jun 2005 13:06:14 +0200	[thread overview]
Message-ID: <20050614110614.GH5155@suse.de> (raw)
In-Reply-To: <EXCHG2003xf4yp8ARf30000046f@EXCHG2003.microtech-ks.com>

Andi Kleen mentioned that this may be a BIOS or driver problem.
Drivers accessing incorrect memory mappings may cause a watchdog to
trigger, which will elicit an MCE.

The address is just over 2GB; the BIOS may have created the
memory hole there. Can you disable memory remapping in the
BIOS?

Olaf


On Fri, Jun 10, 2005 at 03:53:14PM -0500, Roger Heflin wrote:
> We have looked at this more carefully, the customer has
> got me more information and details.   It looks like some
> way nfs exercises a network bug and causes the network driver
> to crash.    The machine/os has survived a full kickstart
> (with a several hundred MB install by 100 plus identical
> machines without that exercising the bug) and a quite a
> bit of light nfs usage, but heavier nfs usage, including
> using bonnie will make the machines fall over fairly quick.
> 
> We are checking for what sort of issues there could be with
> the network driver/network firmware/bmc card.   
> 
> For information this is a Quad Tyan 4882 with 32GB of ram
> (16 have 64GB of ram) with the customer having over 100
> of the Quads.
> 
> There is also a large number of duals, but after further
> examination we don't believe those have the issue.
> 
>                          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

-- 
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-14 11:06 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
2005-06-10 20:53   ` Roger Heflin
2005-06-14 11:06     ` Olaf Kirch [this message]

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=20050614110614.GH5155@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