Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")

From	"hch@lst.de" <hch@lst.de>
Newsgroups	linux.kernel
Subject	Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
Date	2017-02-09 14:40 +0100
Message-ID	<t8X76-6JS-83@gated-at.bofh.it> (permalink)
References	(5 earlier) <t8gEO-5ar-25@gated-at.bofh.it> <t8y8F-7Ir-5@gated-at.bofh.it> <t8Exs-3hZ-19@gated-at.bofh.it> <t8F0v-3Hv-31@gated-at.bofh.it> <t8RuF-3aL-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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.

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Hannes Reinecke <hare@suse.com> - 2017-01-31 17:20 +0100
  RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Dexuan Cui <decui@microsoft.com> - 2017-02-03 13:30 +0100
    RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Dexuan Cui <decui@microsoft.com> - 2017-02-07 03:30 +0100
      Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Bart Van Assche <Bart.VanAssche@sandisk.com> - 2017-02-07 04:00 +0100
        RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Dexuan Cui <decui@microsoft.com> - 2017-02-07 07:30 +0100
          Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Jens Axboe <axboe@kernel.dk> - 2017-02-07 17:20 +0100
            RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Dexuan Cui <decui@microsoft.com> - 2017-02-08 12:00 +0100
              Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when  scheduling workqueue elements") Jens Axboe <axboe@kernel.dk> - 2017-02-08 18:50 +0100
                Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event         lock when scheduling workqueue elements") "hch@lst.de" <hch@lst.de> - 2017-02-08 19:20 +0100
                RE: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock  when scheduling workqueue elements") Dexuan Cui <decui@microsoft.com> - 2017-02-09 08:40 +0100
                Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event         lock when scheduling workqueue elements") "hch@lst.de" <hch@lst.de> - 2017-02-09 14:40 +0100

csiph-web