Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752427AbdHHQgF (ORCPT <rfc822;w@1wt.eu>);
        Tue, 8 Aug 2017 12:36:05 -0400
Received: from vulcan.natalenko.name ([104.207.131.136]:42416 "EHLO
        vulcan.natalenko.name" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752259AbdHHQgD (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 8 Aug 2017 12:36:03 -0400
DMARC-Filter: OpenDMARC Filter v1.3.2 vulcan.natalenko.name 8CEC622C224
Authentication-Results: vulcan.natalenko.name; dmarc=fail (p=none dis=none) header.from=natalenko.name
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Jens Axboe <axboe@kernel.dk>
Cc: Greg KH <gregkh@linuxfoundation.org>, Mike Galbraith <efault@gmx.de>,
        Christoph Hellwig <hch@lst.de>, linux-block@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: blk-mq breaks suspend even with runtime PM patch
Date: Tue, 08 Aug 2017 18:36:01 +0200
Message-ID: <2416479.dXsOYsr7UT@natalenko.name>
In-Reply-To: <843d7ee7-63b9-d34c-6d91-dea0b940d330@kernel.dk>
References: <5912148.iRCpNe8Dyb@natalenko.name> <20170808162252.GC23338@kroah.com> <843d7ee7-63b9-d34c-6d91-dea0b940d330@kernel.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=natalenko.name;
        s=arc-20170712; t=1502210161;
        h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references;
        bh=6jhego6ZD8dRmeK5KYEcWnHDrI9jCIhjoCcaf/v5NVk=;
        b=Sts6pnl770Oh3mpWylfRUk2asFjnfBh3J/fqVmBhQoL0RPd3qOAmywCp+iPC+uXQupNzxy
        CJDjuOpriZtzd/osE5CR43eJsU1gqRcNf2WYAb3ikKBWkotei4ZbC6MmFoirkICtsTQOdH
        ztug+QT1R2oBlEFENBnNABgluYsnO1Q=
ARC-Seal: i=1; s=arc-20170712; d=natalenko.name; t=1502210161; a=rsa-sha256;
        cv=none;
        b=Ojj+5E6p74oS8z1z/OQzGlvNiAIL6tk4hxrY2dETg9duokwn0JCnTUJCnxxEeOGlt7YJ1SS4cU/GRoHa7GFsvUDzeIVhdq3j8k+oiNX0TEJnZZC8S/8kMrZ8EwvntZztcRXm8VbJ/ZbgeklOLADLIyYX6D4rZ1+/quDqmdeP1tI=
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-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by nfs id v78Ga979010767
Content-Length: 1333
Lines: 38

Could you queue "block: disable runtime-pm for blk-mq" too please? It is also 
related to suspend-resume freezes that were observed by multiple users.

Thanks.

On úterý 8. srpna 2017 18:33:29 CEST Jens Axboe wrote:
> On 08/08/2017 10:22 AM, Greg KH wrote:
> > On Sun, Jul 30, 2017 at 03:50:15PM +0200, Oleksandr Natalenko wrote:
> >> Hello Mike et al.
> >> 
> >> On neděle 30. července 2017 7:12:31 CEST Mike Galbraith wrote:
> >>> FWIW, first thing I'd do is update that 4.12.0 to 4.12.4, and see if
> >>> stable fixed it.
> >> 
> >> My build already includes v4.12.4.
> >> 
> >>> If not, I'd find these two commits irresistible.
> >>> 
> >>> 5f042e7cbd9eb blk-mq: Include all present CPUs in the default queue
> >>> mapping
> >>> 4b855ad37194f blk-mq: Create hctx for each present CPU
> >> 
> >> I've applied these 2 commits, and cannot reproduce the issue anymore.
> >> Looks
> >> like a perfect hit, thanks!
> >> 
> >>> 'course applying random upstream bits does come with some risk, trying
> >>> a kernel already containing them has less "entertainment" potential.
> >> 
> >> Should you consider applying them to v4.12.x stable series? CC'ing Greg
> >> just in case.
> > 
> > I can queue these up if I get an ack from the developers/maintainers
> > that it is ok to do so...
> 
> You can add those two commits to stable.