Re: 4.16-RC7 WARNING: CPU: 2 PID: 0 at block/blk-mq.c:1400 __blk_mq_delay_run_hw_queue

On 03/27/2018 02:01 PM, Ming Lei wrote: > Hi Stefan, > > On Tue, Mar 27, 2018 at 12:04:20PM +0200, Stefan Haberland wrote: >> Hi, >> >> I get the following warning in __blk_mq_delay_run_hw_queue when the >> scheduler is set to mq-deadline for DASD devices on s390. >> >> What I see is that for

Re: 4.16-RC7 WARNING: CPU: 2 PID: 0 at block/blk-mq.c:1400 __blk_mq_delay_run_hw_queue

This warning is harmless, please try the following patch: -- From 7b2b5139bfef80f44d1b1424e09ab35b715fbfdb Mon Sep 17 00:00:00 2001 From: Ming Lei Date: Tue, 27 Mar 2018 19:54:23 +0800 Subject: [PATCH] blk-mq: only run mapped hw queues in blk_mq_run_hw_queues() From

Re: 4.16-RC7 WARNING: CPU: 2 PID: 0 at block/blk-mq.c:1400 __blk_mq_delay_run_hw_queue

Hi Stefan, On Tue, Mar 27, 2018 at 12:04:20PM +0200, Stefan Haberland wrote: > Hi, > > I get the following warning in __blk_mq_delay_run_hw_queue when the > scheduler is set to mq-deadline for DASD devices on s390. > > What I see is that for whatever reason there is a hctx nr 0 which has no >

4.16-RC7 WARNING: CPU: 2 PID: 0 at block/blk-mq.c:1400 __blk_mq_delay_run_hw_queue

Hi, I get the following warning in __blk_mq_delay_run_hw_queue when the scheduler is set to mq-deadline for DASD devices on s390. What I see is that for whatever reason there is a hctx nr 0 which has no hctx->tags pointer set. From my observation it is always hctx nr 0 which has a tags NULL