All of lore.kernel.org
 help / color / mirror / Atom feed
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:30:25 -0500	[thread overview]
Message-ID: <454644C1.4080702@rtr.ca> (raw)
In-Reply-To: <20061030181645.GF14055@kernel.dk>

Jens Axboe wrote:
> Can you do:
> 
> $ gdb vmlinux
>   l *cfq_set_request+0x351
> 
> assuming you built with DEBUG_INFO enabled.

Here it is again, from kernel with FRAME_POINTERS and DEBUG_INFO enabled:

=================================
[ INFO: inconsistent lock state ]
2.6.19-rc3-git7-ml #6
---------------------------------
inconsistent {in-softirq-W} -> {softirq-on-W} usage.
startproc/3964 [HC0[0]:SC0[0]:HE1:SE1] takes:
 (&q->__queue_lock){-+..}, at: [<c021780e>] cfq_set_request+0x33e/0x3a0
{in-softirq-W} state was registered at:
  [<c0137439>] mark_lock+0x79/0x600
  [<c013880d>] __lock_acquire+0x64d/0xc20
  [<c013914d>] lock_acquire+0x5d/0x80
  [<c035ea8b>] _spin_lock+0x2b/0x40
  [<c029ee87>] scsi_device_unbusy+0x67/0xa0
  [<c029992c>] scsi_finish_command+0x1c/0xa0
  [<c029f04f>] scsi_softirq_done+0xcf/0xf0
  [<c020fc8b>] blk_done_softirq+0x6b/0x80
  [<c0122732>] __do_softirq+0x92/0x110
  [<c0122815>] do_softirq+0x65/0x70
  [<c0122c85>] ksoftirqd+0x85/0xd0
  [<c0130d48>] kthread+0xe8/0xf0
  [<c0103c4b>] kernel_thread_helper+0x7/0x1c
  [<ffffffff>] 0xffffffff
irq event stamp: 1927
hardirqs last  enabled at (1927): [<c0162a15>] kmem_cache_alloc+0x75/0xb0
hardirqs last disabled at (1926): [<c01629c2>] kmem_cache_alloc+0x22/0xb0
softirqs last  enabled at (0): [<c011b653>] copy_process+0x353/0x1290
softirqs last disabled at (0): [<00000000>] 0x0

other info that might help us debug this:
no locks held by startproc/3964.

stack backtrace:
 [<c0104088>] dump_trace+0x1c8/0x200
 [<c01040da>] show_trace_log_lvl+0x1a/0x30
 [<c0104832>] show_trace+0x12/0x20
 [<c0104999>] dump_stack+0x19/0x20
 [<c0137053>] print_usage_bug+0x243/0x250
 [<c0137962>] mark_lock+0x5a2/0x600
 [<c0138832>] __lock_acquire+0x672/0xc20
 [<c013914d>] lock_acquire+0x5d/0x80
 [<c035ea8b>] _spin_lock+0x2b/0x40
 [<c021780e>] cfq_set_request+0x33e/0x3a0
 [<c020af3f>] elv_set_request+0x1f/0x50
 [<c020e40d>] get_request+0x21d/0x250
 [<c020ec4c>] get_request_wait+0x1c/0x100
 [<c020eebd>] __make_request+0x5d/0x330
 [<c020db44>] generic_make_request+0x174/0x230
 [<c020fed0>] submit_bio+0x60/0x110
 [<c018dcfc>] mpage_bio_submit+0x1c/0x30
 [<c018f363>] mpage_readpages+0x103/0x140
 [<c01aab49>] reiserfs_readpages+0x19/0x20
 [<c014d511>] __do_page_cache_readahead+0x161/0x220
 [<c014d632>] blockable_page_cache_readahead+0x62/0xc0
 [<c014d86f>] page_cache_readahead+0x11f/0x1d0
 [<c0147511>] do_generic_mapping_read+0x501/0x540
 [<c01495a3>] generic_file_aio_read+0xf3/0x240
 [<c0166020>] do_sync_read+0xd0/0x110
 [<c01668e4>] vfs_read+0x94/0x160
 [<c0166e2d>] sys_read+0x3d/0x70
 [<c0102f4d>] sysenter_past_esp+0x56/0x8d
 [<b7f84410>] 0xb7f84410
 =======================

(gdb) l *cfq_set_request+0x33e
0xc021780e is in cfq_set_request (block/cfq-iosched.c:1224).
1219            if (unlikely(!cfqd))
1220                    return;
1221
1222            spin_lock(cfqd->queue->queue_lock);
1223
1224            cfqq = cic->cfqq[ASYNC];
1225            if (cfqq) {
1226                    struct cfq_queue *new_cfqq;
1227                    new_cfqq = cfq_get_queue(cfqd, CFQ_KEY_ASYNC, cic->ioc->task,
1228                                             GFP_ATOMIC);



  reply	other threads:[~2006-10-30 18:30 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
2006-10-30 18:16                   ` Jens Axboe
2006-10-30 18:30                     ` Mark Lord [this message]
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=454644C1.4080702@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 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.