[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MWHPR03MB2669125A47D3CB7EB530D084BF430@MWHPR03MB2669.namprd03.prod.outlook.com>
Date: Tue, 7 Feb 2017 06:29:33 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Bart Van Assche <Bart.VanAssche@...disk.com>,
"hare@...e.com" <hare@...e.com>, "hare@...e.de" <hare@...e.de>,
"axboe@...nel.dk" <axboe@...nel.dk>
CC: "hch@....de" <hch@....de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"jth@...nel.org" <jth@...nel.org>
Subject: RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue
elements
> From: linux-block-owner@...r.kernel.org [mailto:linux-block-
> owner@...r.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
Powered by blists - more mailing lists