linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.70-mm9
Date: 16 Jun 2003 08:59:14 -0700	[thread overview]
Message-ID: <1055779165.1397.870.camel@w-ming2.beaverton.ibm.com> (raw)
In-Reply-To: <20030614232049.6610120d.akpm@digeo.com>

On Sat, 2003-06-14 at 23:20, Andrew Morton wrote:
> Mingming Cao <cmm@us.ibm.com> wrote:
> >
> > On Sat, 2003-06-14 at 01:01, Andrew Morton wrote:
> > 
> > > Was elevator=deadline observed to fail in earlier kernels?  If not then it
> > > may be an anticipatory scheduler bug.  It certainly had all the appearances
> > > of that.
> > Yes, with elevator=deadline the many fsx tests failed on 2.5.70-mm5.
> >  
> > > So once you're really sure that elevator=deadline isn't going to fail,
> > > could you please test elevator=as?
> > > 
> > Ok, the deadline test was run for 10 hours then I stopped it (for the
> > elevator=as test).  
> > 
> > But the test on elevator=as (2.5.70-mm9 kernel) still failed, same
> > problem.  Some fsx tests are sleeping on io_schedule().  
> > 
> > Next I think I will re-run test on elevator=deadline for 24 hours, to
> > make sure the problem is really gone there.  After that maybe try a
> > different Qlogic Driver, currently I am using the driver from Qlogic
> > company(QLA2XXX V8).
> 
> Martin has just observed what appears to be the same failure on
> 2.5.71-mjb1, which is the deadline scheduler, using qlogicisp.
> 
> Again, some IO appears to have been submitted but it never came back.
> 
> It could be a bug in the requests queueing code somewhere, or in the device
> driver.
> 
> So a good thing to do now would be to find the workload+IO
> scheduler+filesystem which triggers it most easily, and run that with a
> different device driver.  The feral driver (drivers/scsi/isp/ in -mm)
> should be suitable for that test.
> 

I re-run the tests on the deadline scheduler on 2.5.70-mm9 kernel for 24
hours,  serveral fsx tests failed as before, same as as scheduler.  So
the problem is not gone on deadline scheduler, it shows up on both
deadline and as scheduler when running fsx tests on exts3 filesystem. 
It's easy to reproduce: fsx tests +ext3 + deadline/as scheduler + with
QLA2xxx v8 driver.

Now I am going to run the same test with feral driver. Will let you
know.

Mingming



  reply	other threads:[~2003-06-16 15:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13  8:33 2.5.70-mm9 Andrew Morton
2003-06-13  9:17 ` 2.5.70-mm9 Andrew Morton
2003-06-13 10:50 ` Bug in 2.5.70-mm9: df: `/': Value too large for defined data type Thomas Schlichter
2003-06-13 20:09   ` Andrew Morton
2003-06-13 17:57 ` 2.5.70-mm9 Brandon Low
2003-06-14  7:51 ` 2.5.70-mm9 Mingming Cao
2003-06-14  8:01   ` 2.5.70-mm9 Andrew Morton
2003-06-15  0:41     ` 2.5.70-mm9 Mingming Cao
2003-06-15  4:14       ` 2.5.70-mm9 Nick Piggin
2003-06-16 16:25         ` 2.5.70-mm9 Mingming Cao
2003-06-15  6:20       ` 2.5.70-mm9 Andrew Morton
2003-06-16 15:59         ` Mingming Cao [this message]
2003-06-18  7:13         ` 2.5.70-mm9 Mingming Cao
2003-06-18  7:38           ` 2.5.70-mm9 Andrew Morton
2003-06-18 13:54             ` 2.5.70-mm9 James Bottomley
2003-06-15  1:14 ` 2.5.70-mm9 Diego Calleja García
2003-06-15  7:58   ` 2.5.70-mm9 Felipe Alfaro Solana
2003-06-15 11:22     ` 2.5.70-mm9 Diego Calleja García
2003-06-13 22:21 2.5.70-mm9 Shane Shrybman

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=1055779165.1397.870.camel@w-ming2.beaverton.ibm.com \
    --to=cmm@us.ibm.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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).