linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: akpm@digeo.com (Andrew Morton)
Cc: plars@linuxtestproject.org (Paul Larson),
	pbadari@us.ibm.com (Badari Pulavarty),
	linux-kernel@vger.kernel.org (lkml),
	lse-tech@lists.sourceforge.net
Subject: Re: Bug in last night's bk test
Date: Mon, 23 Sep 2002 15:52:23 -0700 (PDT)	[thread overview]
Message-ID: <200209232252.g8NMqN110401@eng2.beaverton.ibm.com> (raw)
In-Reply-To: <3D8F9047.B464ABD4@digeo.com> from "Andrew Morton" at Sep 23, 2002 02:05:59 PM PST

> 
> Paul Larson wrote:
> > 
> > The automated nightly testing turned up a bug on one of the test
> > machines last night.  The system that had the problem was running ltp
> > and was a 2-way PII-550, 2GB ram, ext2.  Here is the ksymoops dump:
> > 
> > ksymoops 2.4.5 on i686 2.4.18.  Options used
> >      -V (default)
> >      -K (specified)
> >      -L (specified)
> >      -O (specified)
> >      -m System.map (specified)
> > 
> > kernel BUG at ll_rw_blk.c:1802!
> 
> Ah, yes.
> 
> The direct-io code will build requests which are larger than
> the ips driver is prepared to accept, and the BIO layer correctly
> BUGs out over it.
> 
> We need to convert direct-io to use the bio_add_page() facility
> which Jens has recently added.
> 
> Until that's done you'll need to set BIO_MAX_PAGES to 16 in
> include/linux/bio.h
> 

I am little confused here. I thought IPS driver can handle 64K IO.
Infact, IPS_MAX_SG is set to 17. So it should be able to handle 68K.
I have been told that it can handle more than that.. but for some
reason it was set to 17.

Paul, what kernel are u running ? 2.5.38 ? 

- Badari

  reply	other threads:[~2002-09-23 22:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 21:36 Bug in last night's bk test Paul Larson
2002-09-23 22:05 ` Andrew Morton
2002-09-23 22:52   ` Badari Pulavarty [this message]
2002-09-23 23:13     ` Andrew Morton
2002-09-23 23:37       ` Badari Pulavarty

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=200209232252.g8NMqN110401@eng2.beaverton.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=plars@linuxtestproject.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).