From: Dexuan Cui <decui@microsoft.com>
To: Bart Van Assche <Bart.VanAssche@sandisk.com>,
"hare@suse.com" <hare@suse.com>, "hare@suse.de" <hare@suse.de>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "hch@lst.de" <hch@lst.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"jth@kernel.org" <jth@kernel.org>
Subject: RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements
Date: Tue, 7 Feb 2017 06:29:33 +0000 [thread overview]
Message-ID: <MWHPR03MB2669125A47D3CB7EB530D084BF430@MWHPR03MB2669.namprd03.prod.outlook.com> (raw)
In-Reply-To: <MWHPR03MB26695ACBEBDB30E3E2E108FBBF430@MWHPR03MB2669.namprd03.prod.outlook.com>
> From: linux-block-owner@vger.kernel.org [mailto:linux-block-
> owner@vger.kernel.org] On Behalf Of Dexuan Cui
> with the linux-next kernel.
>
> I can boot the guest with linux-next's next-20170130 without any issue,
> but since next-20170131 I haven't succeeded in booting the guest.
>
> With next-20170203 (mentioned in my mail last Friday), I got the same
> calltrace as Hannes.
>
> With today's linux-next (next-20170206), actually the calltrace changed to
> the below.
> [ 122.023036] ? remove_wait_queue+0x70/0x70
> [ 122.051383] async_synchronize_full+0x17/0x20
> [ 122.076925] do_init_module+0xc1/0x1f9
> [ 122.097530] load_module+0x24bc/0x2980
I don't know why it hangs here, but this is the same calltrace in my
last-Friday mail, which contains 2 calltraces. It looks the other calltrace has
been resolved by some changes between next-20170203 and today.
Here the kernel is trying to load the Hyper-V storage driver (hv_storvsc), and
the driver's __init and .probe have finished successfully and then the kernel
hangs here.
I believe something is broken recently, because I don't have any issue before
Jan 31.
Thanks,
-- Dexuan
next prev parent reply other threads:[~2017-02-07 6:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 9:48 [PATCH] genhd: Do not hold event lock when scheduling workqueue elements Hannes Reinecke
2017-01-31 0:31 ` Bart Van Assche
2017-01-31 16:15 ` Hannes Reinecke
2017-02-03 12:22 ` Dexuan Cui
2017-02-07 2:23 ` Dexuan Cui
2017-02-07 2:56 ` Bart Van Assche
2017-02-07 3:48 ` Dexuan Cui
2017-02-07 6:29 ` Dexuan Cui [this message]
2017-02-07 16:09 ` Jens Axboe
2017-02-08 10:48 ` Dexuan Cui
2017-02-08 17:43 ` Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements") Jens Axboe
2017-02-08 18:03 ` hch
2017-02-09 7:35 ` Dexuan Cui
2017-02-09 13:08 ` hch
2017-02-10 14:49 ` Dexuan Cui
2017-02-14 13:47 ` hch
2017-02-14 14:17 ` Dexuan Cui
2017-02-14 14:28 ` hch
2017-02-14 14:46 ` Dexuan Cui
2017-02-14 14:51 ` hch
2017-02-14 15:54 ` Dexuan Cui
2017-02-14 16:34 ` hch
2017-02-15 13:51 ` Dexuan Cui
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=MWHPR03MB2669125A47D3CB7EB530D084BF430@MWHPR03MB2669.namprd03.prod.outlook.com \
--to=decui@microsoft.com \
--cc=Bart.VanAssche@sandisk.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jth@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.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).