public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Neil Brown <neilb@suse.de>, Chuck Ebbert <cebbert@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] 2.6.21-rc6-git5 in cfq_dispatch_insert
Date: Tue, 24 Apr 2007 23:40:40 +0400	[thread overview]
Message-ID: <462E5D38.5000801@wasp.net.au> (raw)
In-Reply-To: <20070423073543.GE5311@kernel.dk>

Jens Axboe wrote:

> Ok, can you try and reproduce with this one applied? It'll keep the
> system running (unless there are other corruptions going on), so it
> should help you a bit as well. It will dump some cfq state info when the
> condition triggers that can perhaps help diagnose this. So if you can
> apply this patch and reproduce + send the output, I'd much appreciate
> it!
> 

I think I'm wearing holes in my platters. This is being a swine to hit, but I finally got some..
It seems to respond to a combination of high cpu usage and relatively high disk utilisation.

I tried all sorts of acrobatics with multiple readers and hammering the array while reading from 
individual drives..

The only reliable way I can reproduce this seems to be on a degraded array running a "while true ; 
do md5sum -c md5 ; done" on about a 180GB directory of files. It is taking anywhere from 4 to 96 
hours to hit it though.. but at least it's reproducible.


[105449.653682] cfq: rbroot not empty, but ->next_rq == NULL! Fixing up, report the issue to 
lkml@vger.kernel.org
[105449.683646] cfq: busy=1,drv=0,timer=0
[105449.694871] cfq rr_list:
[105449.702715]   3108: sort=0,next=00000000,q=0/1,a=1/0,d=0/0,f=69
[105449.720693] cfq busy_list:
[105449.729054] cfq idle_list:
[105449.737418] cfq cur_rr:
[115435.022192] cfq: rbroot not empty, but ->next_rq == NULL! Fixing up, report the issue to 
lkml@vger.kernel.org
[115435.052160] cfq: busy=1,drv=0,timer=0
[115435.063383] cfq rr_list:
[115435.071227]   3196: sort=0,next=00000000,q=0/1,a=1/0,d=0/0,f=69
[115435.089205] cfq busy_list:
[115435.097566] cfq idle_list:
[115435.105930] cfq cur_rr:
[115616.651883] cfq: rbroot not empty, but ->next_rq == NULL! Fixing up, report the issue to 
lkml@vger.kernel.org
[115616.681848] cfq: busy=1,drv=0,timer=0
[115616.693071] cfq rr_list:
[115616.700916]   3196: sort=0,next=00000000,q=0/1,a=1/0,d=0/0,f=61
[115616.718893] cfq busy_list:
[115616.727253] cfq idle_list:
[115616.735617] cfq cur_rr:
[119679.564753] cfq: rbroot not empty, but ->next_rq == NULL! Fixing up, report the issue to 
lkml@vger.kernel.org
[119679.594732] cfq: busy=1,drv=0,timer=0
[119679.605955] cfq rr_list:
[119679.613799]   3241: sort=0,next=00000000,q=0/1,a=1/0,d=0/0,f=69
[119679.631778] cfq busy_list:
[119679.640136] cfq idle_list:
[119679.648502] cfq cur_rr:

Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

  reply	other threads:[~2007-04-24 19:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 10:14 [OOPS] 2.6.21-rc6-git5 in cfq_dispatch_insert Brad Campbell
2007-04-15 10:49 ` Brad Campbell
2007-04-15 23:53   ` Adrian Bunk
2007-04-16  3:23     ` Brad Campbell
2007-04-16 22:39   ` Chuck Ebbert
2007-04-17  5:10     ` Neil Brown
2007-04-17  8:13       ` Brad Campbell
2007-04-17 11:48       ` Brad Campbell
2007-04-17 20:39       ` Bartlomiej Zolnierkiewicz
2007-04-18 12:37       ` Jens Axboe
2007-04-18 13:19         ` Brad Campbell
2007-04-18 13:21           ` Jens Axboe
2007-04-22  7:37             ` Brad Campbell
2007-04-23  7:35               ` Jens Axboe
2007-04-24 19:40                 ` Brad Campbell [this message]
2007-04-25  8:34                   ` Neil Brown
2007-04-25  8:46                     ` Jens Axboe
2007-04-25  9:34                       ` Jens Axboe
2007-04-25  9:37                       ` Neil Brown
2007-04-25  9:47                         ` Jens Axboe
2007-04-25 10:02                           ` Brad Campbell
2007-04-25 10:18                             ` Jens Axboe
2007-04-25 13:59                               ` Roland Kuhn
2007-04-25 10:25                           ` Neil Brown
2007-04-25 10:36                             ` Jens Axboe
2007-04-25  9:54                         ` Brad Campbell
2007-04-25  8:50                     ` Brad Campbell
2007-04-25 10:06                     ` Brad Campbell
2007-04-25 10:59                       ` Neil Brown
2007-04-25 11:17                         ` Degraded RAID performance - Was : " Brad Campbell
2007-04-18 13:19         ` Jens Axboe
     [not found] <79880979-51BB-4D28-A3E8-3AE0F56F5B0A@e18.physik.tu-muenchen.de>
     [not found] ` <20070424091807.GA3744@kernel.dk>
     [not found]   ` <6A6800B3-F9C8-4046-9E1C-A8CEA81B2CE0@e18.physik.tu-muenchen.de>
     [not found]     ` <20070424093904.GB3744@kernel.dk>
     [not found]       ` <20070424094003.GC3744@kernel.dk>
2007-04-24 12:27         ` Roland Kuhn
2007-04-24 12:32           ` Jens Axboe
2007-04-24 13:03             ` Roland Kuhn
2007-04-24 13:07               ` Jens Axboe

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=462E5D38.5000801@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=cebbert@redhat.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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