All of lore.kernel.org
 help / color / mirror / Atom feed
From: "jianchao.wang" <jianchao.w.wang@oracle.com>
To: Stewart Smith <stewart@linux.ibm.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Christoph Hellwig <hch@infradead.org>,
	Ming Lei <ming.lei@redhat.com>, Hannes Reinecke <hare@suse.com>,
	Johannes Thumshirn <jthumshirn@suse.de>,
	James Smart <james.smart@broadcom.com>,
	Dongli Zhang <dongli.zhang@oracle.com>,
	Laurence Oberman <loberman@redhat.com>,
	stable@vger.kernel.org, Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH] block: Revert v5.0 blk_mq_request_issue_directly() changes
Date: Tue, 9 Apr 2019 13:59:25 +0800	[thread overview]
Message-ID: <300563e5-ebf4-ed62-bbaf-207d3ab5d067@oracle.com> (raw)
In-Reply-To: <87y34jwykf.fsf@linux.vnet.ibm.com>



On 4/9/19 1:13 PM, Stewart Smith wrote:
> cpu 0x4a: Vector: 400 (Instruction Access) at [c000203ff398b100]
>     pc: c0000000021fe700
>     lr: c0000000002001d8: blk_mq_complete_request+0x34/0x138

Would you please figure out what is the source code here with gdb ?

From the backtrace, it seems not the same issue, because no dm-mpath is involved here.

Thanks
Jianchao

>     sp: c000203ff398b390
>    msr: 9000000010009033
>   current = 0xc000203ff3901b00
>   paca    = 0xc000203fff7f3680	 irqmask: 0x03	 irq_happened: 0x01
>     pid   = 658, comm = kworker/u257:2
> Linux version 5.0.7-openpower1 (hostboot@gfw275.aus.stglabs.ibm.com) (gcc version 6.5.0 (Buildroot 2019.02.1-00016-ge01dcd0)) #2 SMP Mon Apr 8 09:14:53 CDT 2019
> 
> [link register   ] c0000000002001d8 blk_mq_complete_request+0x34/0x138
> [c000203ff398b390] c000203ff398b3d0 (unreliable)
> [c000203ff398b3d0] c0000000002d0428 scsi_mq_done+0x48/0x6c
> [c000203ff398b410] c0000000002ee8d8 ata_scsi_simulate+0x78/0x29c
> [c000203ff398b460] c0000000002eee74 ata_scsi_queuecmd+0xa8/0x2cc
> [c000203ff398b4a0] c0000000002d2ac4 scsi_queue_rq+0x7bc/0x810
> [c000203ff398b540] c000000000202570 blk_mq_dispatch_rq_list+0x474/0x5c0
> [c000203ff398b600] c000000000207560 blk_mq_sched_dispatch_requests+0x114/0x18c
> [c000203ff398b660] c0000000002009e4 __blk_mq_run_hw_queue+0xe0/0xf8
> [c000203ff398b6e0] c000000000200a5c __blk_mq_delay_run_hw_queue+0x60/0x184
> [c000203ff398b740] c000000000200c20 blk_mq_run_hw_queue+0x70/0xe4
> [c000203ff398b790] c0000000002077ec blk_mq_sched_insert_request+0x68/0x194
> [c000203ff398b7f0] c0000000001fc1d8 blk_execute_rq_nowait+0x78/0x8c
> [c000203ff398b810] c0000000001fc234 blk_execute_rq+0x48/0x90
> [c000203ff398b860] c0000000002cfa10 __scsi_execute+0xd8/0x1ac
> [c000203ff398b8d0] c0000000002cc31c ioctl_internal_command.constprop.2+0x50/0x144
> [c000203ff398b980] c0000000002cc474 scsi_set_medium_removal+0x64/0x9c
> [c000203ff398b9c0] c0080000101f2754 sd_open+0xe8/0x148 [sd_mod]
> [c000203ff398ba00] c00000000018b730 __blkdev_get+0x198/0x3e4
> [c000203ff398ba70] c00000000018b9cc blkdev_get+0x50/0x35c
> [c000203ff398bb10] c00000000020b140 __device_add_disk+0x468/0x488
> [c000203ff398bbd0] c0080000101f5484 sd_probe_async+0xd4/0x180 [sd_mod]
> [c000203ff398bc60] c00000000009a128 async_run_entry_fn+0x68/0x138
> [c000203ff398bca0] c000000000090858 process_one_work+0x204/0x334
> [c000203ff398bd30] c000000000090ca4 worker_thread+0x2d0/0x394
> [c000203ff398bdb0] c000000000096cb4 kthread+0x14c/0x154
> [c000203ff398be20] c00000000000b72c ret_from_kernel_thread+0x5c/0x70

  reply	other threads:[~2019-04-09  5:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 17:08 [PATCH] block: Revert v5.0 blk_mq_request_issue_directly() changes Bart Van Assche
2019-04-04 21:43 ` Ming Lei
2019-04-04 22:02   ` Bart Van Assche
2019-04-04 23:49   ` Laurence Oberman
2019-04-05  6:06 ` Christoph Hellwig
2019-04-05 12:43   ` Laurence Oberman
2019-04-05 13:58     ` Bart Van Assche
2019-04-05 14:00   ` Bart Van Assche
2019-04-05 17:59     ` Jens Axboe
2019-04-09  5:13 ` Stewart Smith
2019-04-09  5:59   ` jianchao.wang [this message]
2019-04-17  8:02     ` Stewart Smith
2019-04-09 13:51   ` Bart Van Assche

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=300563e5-ebf4-ed62-bbaf-207d3ab5d067@oracle.com \
    --to=jianchao.w.wang@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=dongli.zhang@oracle.com \
    --cc=hare@suse.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=james.smart@broadcom.com \
    --cc=joel@jms.id.au \
    --cc=jthumshirn@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=loberman@redhat.com \
    --cc=ming.lei@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=stewart@linux.ibm.com \
    /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.