From: Mark Lord <liml@rtr.ca>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
mingo@elte.hu
Subject: Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
Date: Mon, 30 Oct 2006 13:11:48 -0500 [thread overview]
Message-ID: <45464064.2090108@rtr.ca> (raw)
In-Reply-To: <45463C5B.7070900@rtr.ca>
Mark Lord wrote:
> Jens Axboe wrote:
..
>> diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
>> index 4bae64e..da9bddf 100644
>> --- a/block/cfq-iosched.c
>> +++ b/block/cfq-iosched.c
..
It's still there. I also see it with the SLES10 kernel 2.6.16.21-0.8.
[ INFO: inconsistent lock state ]
2.6.19-rc3-git7-ml #3
---------------------------------
inconsistent {in-softirq-W} -> {softirq-on-W} usage.
startproc/4046 [HC0[0]:SC0[0]:HE1:SE1] takes:
(&q->__queue_lock){-+..}, at: [<c0219091>] cfq_set_request+0x351/0x3b0
{in-softirq-W} state was registered at:
[<c01376b1>] mark_lock+0x81/0x5f0
[<c0138a90>] __lock_acquire+0x660/0xc10
[<c013939d>] lock_acquire+0x5d/0x80
[<c0361c59>] _spin_lock+0x29/0x40
[<c029fa24>] scsi_device_unbusy+0x64/0x90
[<c029a5bc>] scsi_finish_command+0x1c/0xa0
[<c02115c2>] blk_done_softirq+0x62/0x70
[<c0122a27>] __do_softirq+0x87/0x100
[<c0122af5>] do_softirq+0x55/0x60
[<c0122f3c>] ksoftirqd+0x7c/0xd0
[<c0130f76>] kthread+0xf6/0x100
[<c0103c6f>] kernel_thread_helper+0x7/0x18
[<ffffffff>] 0xffffffff
irq event stamp: 3331
hardirqs last enabled at (3331): [<c016326d>] kmem_cache_alloc+0x6d/0xa0
hardirqs last disabled at (3330): [<c016321f>] kmem_cache_alloc+0x1f/0xa0
softirqs last enabled at (3012): [<c0122af5>] do_softirq+0x55/0x60
softirqs last disabled at (2971): [<c0122af5>] do_softirq+0x55/0x60
other info that might help us debug this:
no locks held by startproc/4046.
stack backtrace:
[<c0104042>] dump_trace+0x192/0x1c0
[<c0104088>] show_trace_log_lvl+0x18/0x30
[<c010483f>] show_trace+0xf/0x20
[<c01049a5>] dump_stack+0x15/0x20
[<c0137291>] print_usage_bug+0x251/0x270
[<c0137ae7>] mark_lock+0x4b7/0x5f0
[<c0138aae>] __lock_acquire+0x67e/0xc10
[<c013939d>] lock_acquire+0x5d/0x80
[<c0361c59>] _spin_lock+0x29/0x40
[<c0219091>] cfq_set_request+0x351/0x3b0
[<c020c7fc>] elv_set_request+0x1c/0x40
[<c020fcff>] get_request+0x23f/0x270
[<c0210537>] get_request_wait+0x27/0x120
[<c02107ca>] __make_request+0x5a/0x350
[<c020f40f>] generic_make_request+0x16f/0x220
[<c02117e4>] submit_bio+0x64/0x110
[<c018e969>] mpage_bio_submit+0x19/0x20
[<c018fe85>] mpage_readpages+0x105/0x140
[<c014d67f>] __do_page_cache_readahead+0x17f/0x260
[<c014d7d2>] blockable_page_cache_readahead+0x72/0xd0
[<c014da25>] page_cache_readahead+0x135/0x1e0
[<c01474ce>] do_generic_mapping_read+0x55e/0x5a0
[<c01496b1>] generic_file_aio_read+0x101/0x270
[<c01669b5>] do_sync_read+0xd5/0x120
[<c01672d1>] vfs_read+0xa1/0x160
[<c0167851>] sys_read+0x41/0x70
[<c0102f71>] sysenter_past_esp+0x56/0x8d
[<b7efd410>] 0xb7efd410
=======================
next prev parent reply other threads:[~2006-10-30 18:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 14:33 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state Mark Lord
2006-10-30 14:43 ` Jens Axboe
2006-10-30 14:57 ` Arjan van de Ven
2006-10-30 15:44 ` Jens Axboe
2006-10-30 16:16 ` Arjan van de Ven
2006-10-30 16:26 ` Jens Axboe
2006-10-30 16:31 ` Arjan van de Ven
2006-10-30 17:52 ` Jens Axboe
2006-10-30 17:54 ` Ingo Molnar
2006-10-30 18:03 ` Jens Axboe
2006-10-30 17:54 ` Mark Lord
2006-10-30 18:11 ` Mark Lord [this message]
2006-10-30 18:16 ` Jens Axboe
2006-10-30 18:30 ` Mark Lord
2006-10-30 18:35 ` Mark Lord
2006-10-30 18:45 ` Arjan van de Ven
2006-10-30 18:56 ` Jens Axboe
2006-10-30 18:52 ` Jens Axboe
2006-10-30 18:59 ` Mark Lord
2006-10-30 19:04 ` Jens Axboe
2006-10-30 18:20 ` Mark Lord
2006-10-30 17:56 ` Arjan van de Ven
2006-10-30 17:57 ` Ingo Molnar
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=45464064.2090108@rtr.ca \
--to=liml@rtr.ca \
--cc=arjan@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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).