linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Krogh <jesper@krogh.cc>
To: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, aradford@gmail.com,
	xfs@oss.sgi.com
Subject: Re: 2.6.38.8 kernel bug in XFS or megaraid driver with heavy I/O load
Date: Tue, 11 Oct 2011 18:07:40 +0200	[thread overview]
Message-ID: <4E9469CC.4090507@krogh.cc> (raw)
In-Reply-To: <20111011141338.GA11808@otto.nzcorp.net>

On 2011-10-11 16:13, Anders Ossowicki wrote:
> On Tue, Oct 11, 2011 at 03:34:48PM +0200, Christoph Hellwig wrote:
>> This is core VM code, and operates purely on on-stack variables except
>> for the page cache radix tree nodes / pages.  So this either could be a
>> core VM bug that no one has noticed yet, or memory corruption.  Can you
>> run memtest86 on the box?
> Unfortunately not, as it is a production server. Pulling it out to memtest 256G
> properly would take too long. But it seems unlikely to me that it should be
> memory corruption. The machine has been running with the same (ecc) memory for
> more than a year and neither the service processor nor the kernel (according to
> dmesg) has caught anything before this. It would be a rare (though I admit not
> impossible) coincidence if we got catastrophic, undetected memory corruption a
> week after attaching a new raid controller with a new disk array.
A sidenote that Anders forgot.. the system was stable for very long time,
but on a 2.6.37 kernel. We upgraded to 2.6.38 to get the raid-controller
support and then it crashed.

Now we're trying to get the new hardware in the air on 2.6.37 with  
backpatched
megaraid driver for the RAID-controller.

-- 
Jesper

  reply	other threads:[~2011-10-11 16:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11  9:17 2.6.38.8 kernel bug in XFS or megaraid driver with heavy I/O load Anders Ossowicki
2011-10-11 13:34 ` Christoph Hellwig
2011-10-11 14:13   ` Anders Ossowicki
2011-10-11 16:07     ` Jesper Krogh [this message]
2011-10-12  0:35     ` Dave Chinner
2011-10-12  4:13       ` Stan Hoeppner
2011-10-12 12:29       ` Anders Ossowicki
2011-10-17 12:40   ` jesper
2011-10-24 16:45     ` Michael Monnerie

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=4E9469CC.4090507@krogh.cc \
    --to=jesper@krogh.cc \
    --cc=aradford@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs@oss.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).