Date: Sat, 25 Sep 2004 10:11:51 -0700
From: William Lee Irwin III <wli@holomorphy.com>
To: Jens Axboe <axboe@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc2-mm3
Message-ID: <20040925171151.GQ9106@holomorphy.com>
References: <20040924014643.484470b1.akpm@osdl.org> <20040925124334.GL9106@holomorphy.com> <20040925163724.GB11525@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040925163724.GB11525@suse.de>
Organization: The Domain of Holomorphy
User-Agent: Mutt/1.5.6+20040722i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1243
Lines: 28

On Sat, Sep 25 2004, William Lee Irwin III wrote:
>> I hope this isn't terribly redundant, but I've tripped over a bogon in
>> 2.6.9-rc2-mm3 similar to the one I reported for 2.6.9-rc2-mm1. The box
>> was actually idle at the time.

On Sat, Sep 25, 2004 at 06:37:27PM +0200, Jens Axboe wrote:
> Same bug, not fixed yet. I'll see if I can get it fixed on monday, I've
> seen it here a few times as well. Seems not to be easily reproducable
> and no real pattern to when it does. In the mean time, you can replace
> the BUG_ON() with a
> 	if (cfqq->allocated[crq->is_write] == 0) {
> 		WARN_ON(1);
> 		cfqq->allocated[crq->is_write] = 1;
> 	}
> and the system should work fine.

I can work with that. I merely thought it may be a useful datapoint to
show that it wasn't a one-off occurrence and/or that it occurred with
multiple kernels with varying combinations of patches and fixes, rather
than pressing the issue per se (though apparently you can reproduce it).
Thanks for looking into it.

-- wli
-
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/