All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jake Maciejewski <maciejej@msoe.edu>
To: Alex Zarochentsev <zam@namesys.com>
Cc: Isaac Chanin <chanin@WPI.EDU>, reiserfs-list@namesys.com
Subject: Re: AMD64 progress?
Date: Tue, 08 Feb 2005 12:25:58 -0600	[thread overview]
Message-ID: <1107887159.12393.6.camel@gentoo> (raw)
In-Reply-To: <20050207195147.GB7482@backtop.namesys.com>

On Mon, 2005-02-07 at 22:51 +0300, Alex Zarochentsev wrote:
> On Mon, Feb 07, 2005 at 01:34:56PM -0600, Jake Maciejewski wrote:
> > I'm running reiser4progs 1.0.3 and 2.6.10 patched with reiser4 from
> > 2.6.11-rc3-mm1 (and this patch).
> > 
> > I've been doing the simultaneous dd and kernel compilation that has
> > always crashed reiser4 on AMD64 in the past. After about an hour with
> > debugging and two hours without debugging, I'm thinking of more ways to
> > torture the FS. For now it looks like reiser4 is working on AMD64!
> 
> i think so.  reiser4/amd64 passed 5h of stress testing instead of crashing in
> first 30min.
> 

Have you been stress testing with debugging disabled? I was doing some
extreme testing and crashed reiser4 with this patch twice. The same test
that crashed it one of the times passes on reiserfs (didn't try the
other), and if enable debugging, I can torture reiser4 all night and
still not crash it. I'll do some more tests and try to identify a
simple, reproducible crash scenario.

> > 
> > How did you track this bug down anyway? Do you have AMD64 hardware, or
> 
> yes, we have amd64 h/w now.
> 
> > did you look over the code and discover an invalid assumption? 
> 
> I found it only after realizing that reiser4_find_next_set_bit
> is broken :( (its simple replacement worked fine)
> 
> > If this
> > bug is indeed fixed, are we any closer to inclusion in vanilla?
> > 
> > On Mon, 2005-02-07 at 16:29 +0300, Alex Zarochentsev wrote:
> > > Hello,
> > > 
> > > On Sat, Jan 15, 2005 at 09:26:01PM -0500, Isaac Chanin wrote:
> > > > 
> > > > Also tested this patch, similar results as to what I've been getting - 
> > > > ie. working for awhile (more than a few hours even this time, but that 
> > > > could just be coincidence, i suppose) and then going down with the normal 
> > > > reiser4_find_next_zero_bit(bnode_working_data(bnode), end_offset, 
> > > > start_offset) >= end_offset error.  For the exact message see 
> > > > http://users.wpi.edu/~chanin/r4newpatch.txt.
> > > > 
> > > 
> > > please try attached patch (it is for fs/reiser4 subtree)
> > > 
> > -- 
> > Jake Maciejewski <maciejej@msoe.edu>
> > 
> 
-- 
Jake Maciejewski <maciejej@msoe.edu>


  reply	other threads:[~2005-02-08 18:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13  5:33 AMD64 progress? Jake Maciejewski
2005-01-14  0:03 ` David Masover
2005-01-14 20:17 ` Alex Zarochentsev
2005-01-14 22:58   ` Jake Maciejewski
2005-01-16  2:26   ` Isaac Chanin
2005-02-07 13:29     ` Alex Zarochentsev
2005-02-07 19:34       ` Jake Maciejewski
2005-02-07 19:51         ` Alex Zarochentsev
2005-02-08 18:25           ` Jake Maciejewski [this message]
2005-02-08 19:12             ` Alex Zarochentsev
2005-02-08 20:49               ` Jake Maciejewski
2005-02-08 20:29       ` Isaac Chanin

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=1107887159.12393.6.camel@gentoo \
    --to=maciejej@msoe.edu \
    --cc=chanin@WPI.EDU \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@namesys.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 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.