> -----Original Message----- > From: KY Srinivasan > Sent: Wednesday, April 5, 2017 9:21 PM > To: Bart Van Assche <bart.vanass...@sandisk.com>; linux- > ker...@vger.kernel.org; linux-bl...@vger.kernel.org; Long Li > <lon...@microsoft.com>; ax...@kernel.dk > Cc: Stephen Hemminger <sthem...@microsoft.com> > Subject: RE: [PATCH] block-mq: set both block queue and hardware queue > restart bit for restart > > > > > -----Original Message----- > > From: Bart Van Assche [mailto:bart.vanass...@sandisk.com] > > Sent: Wednesday, April 5, 2017 8:46 PM > > To: linux-kernel@vger.kernel.org; linux-bl...@vger.kernel.org; Long Li > > <lon...@microsoft.com>; ax...@kernel.dk > > Cc: Stephen Hemminger <sthem...@microsoft.com>; KY Srinivasan > > <k...@microsoft.com> > > Subject: Re: [PATCH] block-mq: set both block queue and hardware queue > > restart bit for restart > > > > On Thu, 2017-04-06 at 03:38 +0000, Long Li wrote: > > > > -----Original Message----- > > > > From: Bart Van Assche [mailto:bart.vanass...@sandisk.com] > > > > > > > > Please drop this patch. I'm working on a better solution. > > > > > > Thank you. Looking forward to your patch. > > > > Hello Long, > > > > It would help if you could share the name of the block or SCSI driver > > with which you ran into that lockup and also if you could share the > > name of the I/O scheduler used in your test. > > The tests that indicated the issue were run Hyper-V. The driver is > storvsc_drv.c The I/O scheduler was I think noop.
Yes, we see I/O hung on scheduler none. Also tried on mq-deadline, same hung with the same cause. > > K. Y > > > > Thanks, > > > > Bart.
