Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754202AbdG3NuU (ORCPT <rfc822;w@1wt.eu>);
        Sun, 30 Jul 2017 09:50:20 -0400
Received: from vulcan.natalenko.name ([104.207.131.136]:48872 "EHLO
        vulcan.natalenko.name" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751002AbdG3NuS (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 30 Jul 2017 09:50:18 -0400
DMARC-Filter: OpenDMARC Filter v1.3.2 vulcan.natalenko.name 2BD9022163E
Authentication-Results: vulcan.natalenko.name; dmarc=fail (p=none dis=none) header.from=natalenko.name
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Mike Galbraith <efault@gmx.de>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
        linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
        gregkh@linuxfoundation.org
Subject: Re: blk-mq breaks suspend even with runtime PM patch
Date: Sun, 30 Jul 2017 15:50:15 +0200
Message-ID: <1662218.y9oETEnj5A@natalenko.name>
In-Reply-To: <1501391551.17388.31.camel@gmx.de>
References: <5912148.iRCpNe8Dyb@natalenko.name> <1501391551.17388.31.camel@gmx.de>
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=1501422616;
        h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references;
        bh=AZuNbHTq/B1dG88exYGCLPU7slU0Ljkqg1s5/+hIbio=;
        b=WNxCqlJxgA0BJgW0mWb7ITo5rCVgdfIabxyHvudi4+VftlRRpdEt3odTBRJXBYd6r3zxpT
        90TBpQK+IHWHrzX1pOdVAfkEQ4bBoj8DPMx2a+Rm/MqsUKtu0BvfDVwlKNmKbQ6p3DGGua
        552idF0bNqNLtqgN2L0EVzGmVV2EOnc=
ARC-Seal: i=1; s=arc-20170712; d=natalenko.name; t=1501422616; a=rsa-sha256;
        cv=none;
        b=PBV/AjeRRcxTMbVkqGuiRwHwkJA42d4s6dDJJCneVC4YPMmcXqHlCEU/VC76Avcx04ZZip3YU0ULS1pJVna8+if92CBGXp/LDn+/cPsMwYwSpwxiG7THutSXkCdeOyjDzGpOXGlN5qusPmVHGDCuZV4Bd3gGUCFL+TykLrz6LbY=
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 v6UDoOqh020578
Content-Length: 740
Lines: 21

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.