public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Olien <dmo@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, maryedie@osdl.org
Subject: Re: FYI: dbt testing on 2.6.0-test4-mm4 fails
Date: Wed, 3 Sep 2003 14:14:41 -0700	[thread overview]
Message-ID: <20030903211441.GA23932@osdl.org> (raw)
In-Reply-To: <20030903102042.52020776.akpm@osdl.org>


Right now, we're looking over older test runs and tracking down exactly
which patch set seems to have caused a break.  We THINK we MIGHT have
a difference in behavior between mm3 and mm3-1.

We'll follow this path for a bit and see where it gets us.

But following that, yes we can put some prink's in and see where
that leads.

On Wed, Sep 03, 2003 at 10:20:42AM -0700, Andrew Morton wrote:
> Dave Olien <dmo@osdl.org> wrote:
> >
> > I'm just mailing you this to keep you informed, Daniel McNeil and
> > I are investigating a failure of the dbt database workload test on
> > 2.6.0-test4-mm4.
> 
> hmm, the direct-io code hasn't changed significantly since February(!).
> 
> Which filesystem are you using?
> 
> One possibility is that some lower-level error occured in the filesystem or
> the device driver but the error code was not correctly propagated back. 
> Could you sprinkle error-path printk's in the direct-io code?
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  parent reply	other threads:[~2003-09-03 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03 17:07 FYI: dbt testing on 2.6.0-test4-mm4 fails Dave Olien
2003-09-03 17:20 ` Andrew Morton
2003-09-03 18:58   ` Cliff White
2003-09-03 21:14   ` Dave Olien [this message]
2003-09-12 21:39 ` Daniel McNeil

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=20030903211441.GA23932@osdl.org \
    --to=dmo@osdl.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maryedie@osdl.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