LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "sitsofe@gmail.com" <sitsofe@gmail.com>, "tj@kernel.org" <tj@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"sth@linux.vnet.ibm.com" <sth@linux.vnet.ibm.com>,
	"hoeppner@linux.vnet.ibm.com" <hoeppner@linux.vnet.ibm.com>,
	"asamymuthupa@micron.com" <asamymuthupa@micron.com>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [BISECTED][REGRESSION] Hang while booting EeePC 900
Date: Mon, 2 Apr 2018 13:47:28 +0000	[thread overview]
Message-ID: <f40e3f7bf4b4305f73bab6eec83eab20b5d8a167.camel@wdc.com> (raw)
In-Reply-To: <CALjAwxh-PVYFnYFCJpGOja+m5SzZ8Sa4J7ohxdK=r8NyOF-EMA@mail.gmail.com>

On Sun, 2018-04-01 at 15:35 +0100, Sitsofe Wheeler wrote:
> While trying to boot an EeePC 900 on the latest git mainline kernel a
> hang is encountered while systemd is starting services but this did
> not happen with 4.15. A bisection narrowed it down to the commit
> 358f70da49d77c43f2ca11b5da584213b2add29c ("blk-mq: make
> blk_abort_request() trigger timeout path"). Here's the bisection log:

Please repost on the linux-block mailing list. I think that mailing list is
more appropriate for this bug report.

Thanks,

Bart.

  reply	other threads:[~2018-04-02 13:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-01 14:35 [BISECTED][REGRESSION] Hang while booting EeePC 900 Sitsofe Wheeler
2018-04-02 13:47 ` Bart Van Assche [this message]
2018-04-02 14:33 ` Jens Axboe
2018-04-02 17:32   ` Sitsofe Wheeler
2018-04-02 20:29     ` Tejun Heo
2018-04-02 21:02       ` Sitsofe Wheeler
2018-04-02 22:04         ` [PATCH] blk-mq: Directly schedule q->timeout_work when aborting a request Tejun Heo
2018-04-02 22:35           ` Jens Axboe
2018-04-06 20:06           ` Sasha Levin
2018-04-10 18:43           ` Martin Steigerwald
2018-04-10 20:46             ` Martin Steigerwald
2018-04-05  8:14       ` [BISECTED][REGRESSION] Hang while booting EeePC 900 Sitsofe Wheeler
2018-04-05 14:42         ` Tejun Heo

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=f40e3f7bf4b4305f73bab6eec83eab20b5d8a167.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=asamymuthupa@micron.com \
    --cc=axboe@kernel.dk \
    --cc=hoeppner@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sitsofe@gmail.com \
    --cc=sth@linux.vnet.ibm.com \
    --cc=tj@kernel.org \
    /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).