Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751321AbdH3GPI (ORCPT <rfc822;w@1wt.eu>);
        Wed, 30 Aug 2017 02:15:08 -0400
Received: from vulcan.natalenko.name ([104.207.131.136]:42736 "EHLO
        vulcan.natalenko.name" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750814AbdH3GPG (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 30 Aug 2017 02:15:06 -0400
DMARC-Filter: OpenDMARC Filter v1.3.2 vulcan.natalenko.name 223C423E660
Authentication-Results: vulcan.natalenko.name; dmarc=fail (p=none dis=none) header.from=natalenko.name
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Wed, 30 Aug 2017 08:15:02 +0200
From: oleksandr@natalenko.name
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
        linux-block@vger.kernel.org, linux-raid@vger.kernel.org,
        linux-kernel@vger.kernel.org, Shaohua Li <shli@kernel.org>
Subject: Re: I/O hangs after resuming from suspend-to-ram
In-Reply-To: <20170830051725.GA5840@ming.t460p>
References: <3926917.BCSovyVWdL@natalenko.name>
 <1615033.Xza1AIGLzP@natalenko.name> <20170829002425.GA28904@ming.t460p>
 <2329566.kid2YYBOAQ@natalenko.name> <20170830021537.GA4897@ming.t460p>
 <20170830051725.GA5840@ming.t460p>
Message-ID: <692537117e26fe71b5e07cd8c86b38e4@natalenko.name>
User-Agent: Roundcube Webmail/1.3.0 
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=natalenko.name;
        s=arc-20170712; t=1504073703;
        h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references;
        bh=M062/Is2hpCoZG2le+7VwnzpYKaB0Aol2C9ESggdqhM=;
        b=Hq6cDIiZvRLm9fyyxHY34C/feTRWCeI/F6d90V51SCNoFWsRBXONCthAjUUh/KRZJAmLVC
        k8DgX4mZOlkBrQ6BFTTKnMgRcu7T8iuS8/TsIxYHMCoWsER+Pgtp59zqj7LoeyXdItyUeH
        3cIC+PEqblKue0mDpvFydt6dMWymeFE=
ARC-Seal: i=1; s=arc-20170712; d=natalenko.name; t=1504073703; a=rsa-sha256;
        cv=none;
        b=RvvqO/pV9aTiTBu2mleRsgJagLLj8c9iPwlFHhsot2gQLJdxRLAfBfTI3SlOzpcxvhr9RPl6jbaYYcz0Ob14X4vwszS+gdZZkGR54i4Nbv9/qyUYk/fGgycmRshazplOJOZy6ZPlAFMle+bGSnVGiX7csmr3NHKz2djLhZ7M5OA=
ARC-Authentication-Results: i=1; auth=pass smtp.auth=oleksandr@natalenko.name
        smtp.mailfrom=oleksandr@natalenko.name
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 918
Lines: 29

Hello.

Addressing your questions below.

> Can't reproduce even with putting dmcypt on raid10 after applying my 
> patch.

Just a side note, that dm-crypt is not necessary here — I am able to 
trigger hang with RAID10 and LVM only.

> BTW, could you share us which blk-mq scheduler you are using on sata?

Okay, now it makes sense. Previously, without your patch I was able to 
reproduce the issue with "mq-deadline", "bfq" and "none". Now, I cannot 
trigger it with "none" set, but "mq-deadline" still hangs for me. Does 
this mean each scheduler should be modified separately?

> Could you apply the following debug patch and provide the dmesg log 
> after running the commands below?

Is it still relevant since I confirm issue to be fixed with "none"?

Thanks.

30.08.2017 07:17, Ming Lei написав:
> …SNIP…
> Can't reproduce even with putting dmcypt on raid10 after applying
> my patch.
> …SNIP…