On 01/31/2017 05:01 PM, Bart Van Assche wrote:
> On Tue, 2017-01-31 at 13:58 -0800, Jens Axboe wrote:
>> Interesting, I'll check this. Doesn't make any sense why the scheduler
>> would be implicated in that, given how we run completions now. But if
>> it complains, then something must be up.
>
> (reduced CC-list)
>
> There is another issue that needs further attention and for which I have
> not yet had the time to root-cause it: several processes became unkillable
> while I was running srp-test (with scheduler "none"). Apparently the dm
> queues got stuck in state BLK_MQ_S_SCHED_RESTART:
>
> # grep -aH '' dm*/*/0/{state,dispatch,*/rq_list}
> dm-0/mq/0/state:0x4
> dm-1/mq/0/state:0x4
> dm-0/mq/0/dispatch:ffff880386d1ca00 {.cmd_type=1, .cmd_flags=0x8801,
> .rq_flags=0x2000, .tag=1637, .internal_tag=-1}
> dm-1/mq/0/dispatch:ffff880388ee5400 {.cmd_type=1, .cmd_flags=0x4000,
> .rq_flags=0x2000, .tag=42, .internal_tag=-1}
> dm-1/mq/0/dispatch:ffff880388ee5600 {.cmd_type=1, .cmd_flags=0x4000,
> .rq_flags=0x2000, .tag=43, .internal_tag=-1}
I think this patch:
http://git.kernel.dk/cgit/linux-block/commit/?h=for-4.11/block&id=12d70958a2e8d587acaa51dafd5d6620e00b7543
should fix it for you. I just ran into the same thing tonight, testing
an unrelated thing. It's the only reason that state should be 0x4 for
you, so it has the same finger print.
The patch has been merged into for-next.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-block" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
