From: Nick Piggin <piggin@cyberone.com.au>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Badness in as_completed_request
Date: Wed, 05 Nov 2003 20:18:54 +1100 [thread overview]
Message-ID: <3FA8C07E.4050703@cyberone.com.au> (raw)
In-Reply-To: <20031105085817.GH21853@vitelus.com>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
Aaron Lehmann wrote:
>I've been seeing this about every day for the past month or so, while
>tracking 2.6.0-test*. Usually by the time I feel like reporting it I'm
>a few revisions behind and decide to upgrade before complaining about
>it. Now I'm running -test9 and it still happens. This happens every
>few day or so under normal load and every few minutes under high I/O
>load. I'm running an x86 system with a 3ware RAID5:
>
>Badness in as_completed_request at drivers/block/as-iosched.c:919
>
This warning is harmless. Here is a patch against 2.6.0-test9-mm2.
Please test that kernel as it has a few other important as-iosched
fixes. Thanks.
[-- Attachment #2: as-warn-fix.patch --]
[-- Type: text/plain, Size: 591 bytes --]
linux-2.6-npiggin/drivers/block/as-iosched.c | 2 --
1 files changed, 2 deletions(-)
diff -puN drivers/block/as-iosched.c~as-warn-fix drivers/block/as-iosched.c
--- linux-2.6/drivers/block/as-iosched.c~as-warn-fix 2003-11-05 20:16:42.000000000 +1100
+++ linux-2.6-npiggin/drivers/block/as-iosched.c 2003-11-05 20:16:58.000000000 +1100
@@ -965,8 +965,6 @@ static void as_completed_request(request
return;
if (ad->changed_batch && ad->nr_dispatched == 1) {
- WARN_ON(ad->batch_data_dir == arq->is_sync);
-
kblockd_schedule_work(&ad->antic_work);
ad->changed_batch = 0;
_
prev parent reply other threads:[~2003-11-05 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 8:58 Aaron Lehmann
2003-11-05 9:18 ` Nick Piggin [this message]
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=3FA8C07E.4050703@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=aaronl@vitelus.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®