All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: mroconnor@oel.state.nj.us
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel bug in file-item.c
Date: Wed, 29 Apr 2009 14:40:19 -0400	[thread overview]
Message-ID: <1241030419.20099.55.camel@think.oraclecorp.com> (raw)
In-Reply-To: <49F89E91.3020604@oel.state.nj.us>

On Wed, 2009-04-29 at 14:38 -0400, Marc R. O'Connor wrote:
> > 
> >> I have done that on all btrfs partitions I have and btrfsck did not
> >> return anything odd.
> >>
> > 
> > In that case, the bad ordering is being introduced at run time.  Could
> > you please run memtest86 on the box?
> > 
> > -chris
> > 
> > 
>  memtest comes back with two errors very early on then reboots the
> sysrescueCD. :(

Well, then I'm surprised btrfs doesn't crash more violently and more
often ;)

Do you think you're hitting a memtest bug or is the HW really bad?

-chris





  reply	other threads:[~2009-04-29 18:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 17:39 kernel bug in file-item.c Marc R. O'Connor
2009-04-28 19:23 ` Chris Mason
2009-04-28 19:30   ` Marc R. O'Connor
2009-04-29 16:04   ` Marc R. O'Connor
2009-04-29 17:53     ` Chris Mason
2009-04-29 18:21       ` Marc R. O'Connor
2009-04-29 18:30         ` Chris Mason
2009-04-29 18:38           ` Marc R. O'Connor
2009-04-29 18:40             ` Chris Mason [this message]
2009-04-29 18:46               ` Marc R. O'Connor
2009-04-29 18:50               ` Zach Brown
2009-04-29 19:04                 ` Marc R. O'Connor
2009-04-30  7:23                   ` Dmitri Nikulin
2009-04-29 19:32               ` Tracy Reed
2009-04-30  9:08                 ` Paul Komkoff
2009-04-30 16:54                   ` Tracy Reed
2009-05-01  2:13                     ` Dmitri Nikulin

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=1241030419.20099.55.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mroconnor@oel.state.nj.us \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.