From: "hch@lst.de" <hch@lst.de>
To: Dexuan Cui <decui@microsoft.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Bart Van Assche <Bart.VanAssche@sandisk.com>,
"hare@suse.com" <hare@suse.com>, "hare@suse.de" <hare@suse.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"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: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
Date: Thu, 9 Feb 2017 14:08:00 +0100 [thread overview]
Message-ID: <20170209130800.GA12057@lst.de> (raw)
In-Reply-To: <MWHPR03MB26698583CE04682F588ACAD4BF450@MWHPR03MB2669.namprd03.prod.outlook.com>
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.
next prev parent reply other threads:[~2017-02-09 13:33 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
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 [this message]
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=20170209130800.GA12057@lst.de \
--to=hch@lst.de \
--cc=Bart.VanAssche@sandisk.com \
--cc=axboe@kernel.dk \
--cc=decui@microsoft.com \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=jth@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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