From: Dan Williams <dan.j.williams@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jens Axboe <jens.axboe@oracle.com>, Neil Brown <neilb@suse.de>,
Jacek Luczak <difrost.kernel@gmail.com>,
Prakash Punnoor <prakash@punnoor.de>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-raid@vger.kernel.org
Subject: Re: WARNING in 2.6.25-07422-gb66e1f1
Date: Thu, 08 May 2008 11:46:19 -0700 [thread overview]
Message-ID: <1210272379.9697.3.camel@dwillia2-linux.ch.intel.com> (raw)
In-Reply-To: <200805082039.01316.rjw@sisk.pl>
On Thu, 2008-05-08 at 11:39 -0700, Rafael J. Wysocki wrote:
> I get a similar warning with RAID1 on one of my test boxes:
>
> WARNING: at /home/rafael/src/linux-2.6/include/linux/blkdev.h:443 blk_remove_plug+0x85/0xa0()
> Modules linked in: raid456 async_xor async_memcpy async_tx xor raid0 ehci_hcd ohci_hcd sd_mod edd raid1 ext3 jbd fan sata_uli pata_ali thermal processor
> Pid: 2159, comm: md1_raid1 Not tainted 2.6.26-rc1 #158
>
> Call Trace:
> [<ffffffff80238bbf>] warn_on_slowpath+0x5f/0x80
> [<ffffffff8025e8d8>] ? __lock_acquire+0x748/0x10d0
> [<ffffffff80348f55>] blk_remove_plug+0x85/0xa0
> [<ffffffffa004df64>] :raid1:flush_pending_writes+0x44/0xb0
> [<ffffffffa004e649>] :raid1:raid1d+0x59/0xfe0
> [<ffffffff8025e8d8>] ? __lock_acquire+0x748/0x10d0
> [<ffffffff8025dc4f>] ? trace_hardirqs_on+0xbf/0x150
> [<ffffffff8043ea8c>] md_thread+0x3c/0x110
> [<ffffffff8024f6a0>] ? autoremove_wake_function+0x0/0x40
> [<ffffffff8043ea50>] ? md_thread+0x0/0x110
> [<ffffffff8024f23d>] kthread+0x4d/0x80
> [<ffffffff8020c548>] child_rip+0xa/0x12
> [<ffffffff8020bc5f>] ? restore_args+0x0/0x30
> [<ffffffff8024f1f0>] ? kthread+0x0/0x80
> [<ffffffff8020c53e>] ? child_rip+0x0/0x12
>
> ---[ end trace 05d4e0844c61f45d ]---
>
> This is the WARN_ON_ONCE(!queue_is_locked(q)) in queue_flag_clear(),
> apparently.
Yes, it triggers on all RAID levels. The patch in this message:
http://marc.info/?l=linux-raid&m=121001065404056&w=2
>
...fixes the raid 0/1/10/5/6 cases, but I am still trying to isolate an
issue (potentially unrelated) with linear arrays.
--
Dan
next prev parent reply other threads:[~2008-05-08 18:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 9:51 WARNING in 2.6.25-07422-gb66e1f1 Prakash Punnoor
2008-05-04 13:02 ` Jacek Luczak
2008-05-04 18:38 ` Jens Axboe
2008-05-05 7:24 ` Neil Brown
2008-05-05 18:03 ` Dan Williams
2008-05-05 19:02 ` Jens Axboe
2008-05-08 18:39 ` Rafael J. Wysocki
2008-05-08 18:46 ` Dan Williams [this message]
2008-05-08 23:18 ` Dan Williams
2008-05-09 2:15 ` Neil Brown
2008-05-09 4:59 ` Dan Williams
2008-05-09 5:38 ` Neil Brown
2008-05-09 5:38 ` Neil Brown
2008-05-12 17:46 ` Dan Williams
2008-05-13 1:08 ` Neil Brown
2008-05-05 18:31 ` Prakash Punnoor
2008-05-05 23:08 ` Gabriel C
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=1210272379.9697.3.camel@dwillia2-linux.ch.intel.com \
--to=dan.j.williams@intel.com \
--cc=difrost.kernel@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=prakash@punnoor.de \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.