linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: maneesh@in.ibm.com
Cc: mbligh@aracnet.com, James.Bottomley@SteelEye.com,
	linux-kernel@vger.kernel.org
Subject: Re: 2.5.73-mm1 falling over in SDET
Date: Mon, 30 Jun 2003 11:19:26 -0700	[thread overview]
Message-ID: <20030630111926.5d883a3b.akpm@digeo.com> (raw)
In-Reply-To: <20030630130432.GD4065@in.ibm.com>

Maneesh Soni <maneesh@in.ibm.com> wrote:
>
> > I tried sdet on 16-way numaq with 2.5.73-mm2. It completes the run on ext2 
> > (no OOMs), but gives following oops while running on ext3
> > 
> 
> Looks like that was some one off oops.. on second iteration I could run
> sdet on ext3 also without any oops or oom.

No, I think that assertion failure in journal_dirty_metadata() was more
than a once off, whatever that is.  There is probably something wrong in
there, but from a moderate-sized look I cannot see what it is.

Unless inspiration strikes we will need to wait until someone can hit it
with some sort of repeatability and then run with the ext3-debug patch
applied and enabled.

http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.73/ext3-debug.patch

This will give a trace of what happened to that buffer and should allow me
to fix the bug.


  reply	other threads:[~2003-06-30 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-28 14:31 2.5.73-mm1 falling over in SDET Martin J. Bligh
2003-06-28 15:36 ` Martin J. Bligh
2003-06-29  0:02   ` Andrew Morton
2003-06-29  3:28     ` James Bottomley
2003-06-29  5:35       ` Martin J. Bligh
2003-06-30 10:17         ` Maneesh Soni
2003-06-30 13:04           ` Maneesh Soni
2003-06-30 18:19             ` Andrew Morton [this message]
2003-06-28 17:29 ` Andrew Morton

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=20030630111926.5d883a3b.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.com \
    --cc=mbligh@aracnet.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).