From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754734AbdBGQJb (ORCPT ); Tue, 7 Feb 2017 11:09:31 -0500 Received: from mail-io0-f181.google.com ([209.85.223.181]:35981 "EHLO mail-io0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754518AbdBGQJS (ORCPT ); Tue, 7 Feb 2017 11:09:18 -0500 Subject: Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements To: Dexuan Cui , Bart Van Assche , "hare@suse.com" , "hare@suse.de" References: <1484732896-22941-1-git-send-email-hare@suse.de> <1485822639.2669.16.camel@sandisk.com> <532c55c4-15da-d2f9-401c-36bc4343756b@suse.com> <1486436195.2791.1.camel@sandisk.com> Cc: "hch@lst.de" , "linux-kernel@vger.kernel.org" , "linux-block@vger.kernel.org" , "jth@kernel.org" From: Jens Axboe Message-ID: <9199d528-f220-5b77-d657-c510ca210067@kernel.dk> Date: Tue, 7 Feb 2017 09:09:16 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/06/2017 11:29 PM, Dexuan Cui wrote: >> 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. Can you try and bisect it? -- Jens Axboe