LKML Archive on
help / color / mirror / Atom feed
From: "David M. Grimes" <>
To: Jim Crilly <>
Subject: Re: AIC7xxx panic
Date: Mon, 8 Oct 2001 20:51:12 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20011007163158.Q1555-100000@gerard> <1002508308.452.3.camel@warblade>
In-Reply-To: <1002508308.452.3.camel@warblade>; from on Sun, Oct 07, 2001 at 10:31:48PM -0400

On Sun, Oct 07, 2001 at 10:31:48PM -0400, Jim Crilly wrote:
> I changed AHC_NSEG from 128 to 512 and as expected the panic went away,
> but does this mean the default should be higher in the kernel or is
> there a real bug here? The main reason I wonder is because it ran fine
> on disk 0 but panic'd on disk 1.

Perhaps this is related (from 2.4.10-acX thread later on l-k):

>From Mon Oct  8 18:34:32 2001
Subject: Re: linux-2.4.10-acX
To: (Mike Fedyk)
From: Alan Cox <>

> > -   Elevator flow control
> Where can I find more information on this?

Read the ll_rw_blk diff. Basically it tries to avoid too many locked
buffers clogging up memory and killing the box. I'm not totally sure its
the right approach.

Were there recent changes in ll_rw_blk which are being addressed by
"Elevator flow control"?  As suggested earlier in this thread, the cause
might be a few layers up, and this seemed relevant.

Can anyone confirm or shed any additional light on this?


  reply	other threads:[~2001-10-09  0:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-07 10:37 Jim Crilly
2001-10-07 10:48 ` Rob Turk
2001-10-07 11:28 ` Jim Crilly
2001-10-07 12:21   ` David M. Grimes
2001-10-07 14:48     ` Gérard Roudier
2001-10-08  2:31       ` Jim Crilly
2001-10-09  0:51         ` David M. Grimes [this message]
2001-10-09 11:47           ` Alan Cox
2001-10-09  2:21       ` Justin T. Gibbs

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: AIC7xxx panic' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).