From: Bart Van Assche <bvanassche@acm.org>
To: Stewart Smith <stewart@linux.ibm.com>, 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>,
Jianchao Wang <jianchao.w.wang@oracle.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 06:51:52 -0700 [thread overview]
Message-ID: <17e00997-fd0c-686c-1c0d-f57fff8e52ea@acm.org> (raw)
In-Reply-To: <87y34jwykf.fsf@linux.vnet.ibm.com>
On 4/8/19 10:13 PM, Stewart Smith wrote:
> At least when this patch is cherry-picked back on top of 5.0.7, it
> doesn't seem to fully fix the problem for us (which is ppc64le). We hit
> this at some point while eudev is finding disks and we have a process
> mounting them to see what's there:
>
> cpu 0x4a: Vector: 400 (Instruction Access) at [c000203ff398b100]
> pc: c0000000021fe700
> lr: c0000000002001d8: blk_mq_complete_request+0x34/0x138
> 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
Can you bisect this crash?
Thanks,
Bart.
prev parent reply other threads:[~2019-04-09 13:51 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
2019-04-17 8:02 ` Stewart Smith
2019-04-09 13:51 ` Bart Van Assche [this message]
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=17e00997-fd0c-686c-1c0d-f57fff8e52ea@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=dongli.zhang@oracle.com \
--cc=hare@suse.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=jianchao.w.wang@oracle.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 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).