From: Jens Axboe <jens.axboe@oracle.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-next@vger.kernel.org
Subject: Re: next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
Date: Mon, 17 Nov 2008 19:06:04 +0100 [thread overview]
Message-ID: <20081117180604.GV26778@kernel.dk> (raw)
In-Reply-To: <a4423d670811170739w3cab002aqda014ab87ebed529@mail.gmail.com>
On Mon, Nov 17 2008, Alexander Beregalov wrote:
> 2008/11/15 Alexander Beregalov <a.beregalov@gmail.com>:
> > 2008/11/15 Jens Axboe <jens.axboe@oracle.com>:
> >> On Fri, Nov 14 2008, Alexander Beregalov wrote:
> >>> WARNING: at block/blk-barrier.c:246 blk_do_ordered+0x22b/0x26a()
> >>> Modules linked in:
> >>> Pid: 0, comm: swapper Not tainted 2.6.28-rc4-next-20081114 #3
> >>> Call Trace:
> >>> <IRQ> [<ffffffff80236d63>] warn_on_slowpath+0x58/0x7d
> >>> [<ffffffff802570e3>] ? mark_lock+0x1c/0x37a
> >>> [<ffffffff803a69f9>] ? elv_rb_del+0x30/0x4b
> >>> [<ffffffff803b1092>] ? cfq_remove_request+0x180/0x1d8
> >>> [<ffffffff803afd03>] ? __cfq_slice_expired+0xd6/0xeb
> >>> [<ffffffff803afd31>] ? cfq_slice_expired+0x19/0x1b
> >>> [<ffffffff803b1832>] ? cfq_dispatch_requests+0x2c1/0x37e
> >>> [<ffffffff803aa98c>] blk_do_ordered+0x22b/0x26a
> >>> [<ffffffff803a6560>] elv_next_request+0x1d0/0x210
> >>> [<ffffffff80439c7c>] scsi_request_fn+0x9e/0x539
> >>> [<ffffffff80255c66>] ? put_lock_stats+0xe/0x27
> >>> [<ffffffff803a827e>] blk_invoke_request_fn+0x3b/0x6e
> >>> [<ffffffff803a87fd>] __blk_run_queue+0x25/0x29
> >>> [<ffffffff803a8822>] blk_run_queue+0x21/0x35
> >>> [<ffffffff80439509>] scsi_run_queue+0x2cf/0x379
> >>> [<ffffffff8043a33e>] scsi_next_command+0x36/0x46
> >>> [<ffffffff8043a509>] scsi_end_request+0x92/0xa4
> >>> [<ffffffff8043aae7>] scsi_io_completion+0x1a7/0x3ad
> >>> [<ffffffff80434551>] scsi_finish_command+0xe9/0xf2
> >>> [<ffffffff8043afd5>] scsi_softirq_done+0x10e/0x117
> >>> [<ffffffff803ac393>] blk_done_softirq+0x7f/0x8f
> >>> [<ffffffff8023c173>] __do_softirq+0x70/0x101
> >>> [<ffffffff8020cc0c>] call_softirq+0x1c/0x28
> >>> [<ffffffff8020e229>] do_softirq+0x39/0x8a
> >>> [<ffffffff8023bd78>] irq_exit+0x45/0xa2
> >>> [<ffffffff8020e53a>] do_IRQ+0x16a/0x19c
> >>> [<ffffffff8020bceb>] ret_from_intr+0x0/0xf
> >>> <EOI> [<ffffffff80212e09>] ? mwait_idle+0x3e/0x48
> >>> [<ffffffff80212e00>] ? mwait_idle+0x35/0x48
> >>> [<ffffffff8020a940>] ? cpu_idle+0x51/0xba
> >>> [<ffffffff80514f9c>] ? rest_init+0x70/0x72
> >>> ---[ end trace 115cb4be7e150bb9 ]---
> >>
> >> I'm assuming this is new with -next and doesn't happen with 2.6.28-rc4?
> > Yes.
> >> Is it reproducible in -next?
> > I have seen it only once yet.
>
> I have the same warning on 2.6.28-rc5-next-20081117, reproducible on dbench.
How big is the file system, how much ram do you have, what are your
mount options, how many dbench clients, and what dbench version? I tried
reproducing it today with no luck on -git + for-2.6.29.
--
Jens Axboe
next prev parent reply other threads:[~2008-11-17 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 13:56 next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered() Alexander Beregalov
2008-11-15 16:07 ` Jens Axboe
2008-11-15 17:25 ` Alexander Beregalov
2008-11-17 15:39 ` Alexander Beregalov
2008-11-17 18:06 ` Jens Axboe [this message]
2008-11-18 18:05 ` Alexander Beregalov
2008-11-18 18:07 ` Alexander Beregalov
2008-11-18 18:09 ` 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=20081117180604.GV26778@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).