From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752778AbdBINdu (ORCPT ); Thu, 9 Feb 2017 08:33:50 -0500 Received: from verein.lst.de ([213.95.11.211]:52362 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752038AbdBINdq (ORCPT ); Thu, 9 Feb 2017 08:33:46 -0500 Date: Thu, 9 Feb 2017 14:08:00 +0100 From: "hch@lst.de" To: Dexuan Cui Cc: Jens Axboe , Bart Van Assche , "hare@suse.com" , "hare@suse.de" , "Martin K. Petersen" , "linux-kernel@vger.kernel.org" , "linux-block@vger.kernel.org" , "jth@kernel.org" Subject: Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements") Message-ID: <20170209130800.GA12057@lst.de> References: <1486436195.2791.1.camel@sandisk.com> <9199d528-f220-5b77-d657-c510ca210067@kernel.dk> <20170208180314.GA17838@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Dexuan, I've spent some time with the logs and looking over the code and couldn't find any smoking gun. I start to wonder if it might just be a timing issue? Can you try one or two things for me: 1) run with the blk-mq I/O path for scsi by either enabling it a boot / module load time with the scsi_mod.use_blk_mq=Y option, or at compile time by enabling the CONFIG_SCSI_MQ_DEFAULT option. If that fails with the commit a blk-mq run before the commit would also be useful. 2) if possible run a VM config without the virtual CD-ROM drive - a lot of the scsi log chatter is about handling timeouts on the CD drive, so that might be able to isolate issues a bit better. Note that I'll be offline from this afternoon European time until Sunday night as I'm out in the mountains at a lodge without internet access, but this issue will be my priority once back.