From: Ian W MORRISON <ianwmorrison@gmail.com>
To: axboe@kernel.dk
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
kashyap.desai@broadcom.com, loberman@redhat.com, osandov@fb.com,
hch@lst.de, bart.vanassche@wdc.com, hare@suse.de,
ming.lei@redhat.com
Subject: Re: [PATCH] Revert "blk-mq: issue directly if hw queue isn't busy in case of 'none'"
Date: Wed, 29 Aug 2018 02:07:06 +1000 [thread overview]
Message-ID: <CAFXWsS_661mkZa1iYEs+8-O-fdFF6bEcqtZrNBzVaNthT2U46w@mail.gmail.com> (raw)
In-Reply-To: <211633e2-a812-d489-e11c-c3f271c465fc@kernel.dk>
On Wed, 29 Aug 2018 at 01:48, Jens Axboe <axboe@kernel.dk> wrote:
>
> On 8/28/18 9:47 AM, Ian W MORRISON wrote:
> > Kernel oops when booting on Bay and Cherry Trail devices
> > such as Intel Compute Stick. Bisected as:
> >
> > commit 6ce3dd6eec11 ("blk-mq: issue directly if hw queue isn't busy in case of 'none'")
> >
> > This patch reverts the above commit.
>
> Did I miss the posting of that oops? Just curious where this is
> going wrong. Not adverse to reverting, but I'd like to try to
> understand the issue first.
>
> --
> Jens Axboe
>
I've not been able to capture it however manually transcribing what is
on the screen:
mmc0: Got data interrupt 0x00000002 even though no data operation
followed by:
mmc0: sdhci: ============= SDHCI REGISTER DUMP ==============
Do you want any specific register value or should I transcribe each
(as I am working from an image taken at boot)?
next prev parent reply other threads:[~2018-08-28 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 15:47 [PATCH] Revert "blk-mq: issue directly if hw queue isn't busy in case of 'none'" Ian W MORRISON
2018-08-28 15:48 ` Jens Axboe
2018-08-28 16:07 ` Ian W MORRISON [this message]
2018-08-28 16:09 ` Jens Axboe
[not found] ` <CAFXWsS82zi7w81-=4ALwMiFm9iQd=NgF3sSBLfvNdU2czEzxwg@mail.gmail.com>
2018-08-28 16:13 ` Jens Axboe
2018-08-28 17:01 ` Ian W MORRISON
2018-08-28 17:12 ` Jens Axboe
2018-08-28 19:11 ` Hunter, Adrian
2018-08-29 6:15 ` Ulf Hansson
2018-08-29 14:01 ` Jens Axboe
2018-08-30 12:05 ` Ulf Hansson
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=CAFXWsS_661mkZa1iYEs+8-O-fdFF6bEcqtZrNBzVaNthT2U46w@mail.gmail.com \
--to=ianwmorrison@gmail.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kashyap.desai@broadcom.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.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).