Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp688459pxb; Fri, 28 Jan 2022 08:02:11 -0800 (PST) X-Google-Smtp-Source: ABdhPJw0rIcw6Ge5Z+VSVRKaI6OsLebZfp5qzDlqeCs7lpGvgE1muTlFTWjJcVsKhet5nPfTViC7 X-Received: by 2002:a17:902:8204:: with SMTP id x4mr9344038pln.18.1643385731217; Fri, 28 Jan 2022 08:02:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643385731; cv=none; d=google.com; s=arc-20160816; b=wAPogAS60RsYG7Z1N6yQVdePMazAT87ZmJUWPt18bv5VQpXXwuldqSvW4wDRAJDPKH iOcmN7EGMIFpubtOvoyFV1PKg9PY1+rbIRKSkMZ+dQFIGCBb7KJeXnm/GR4ZFseI3zej 7a1lvWOjEGXKarOUr8BXyNLmMJtAf5QylQyyEfNCv7hXAuUaBPZT40wa0+AtppD0RWjT Os03u8cs8GDi4SoXELgCfWOa78Y5h3TNWjtz70KQrhCTDYyNxcLetDFQWYaY52J95LQw DsGbfB3Q0Ey1CBzKxRtmJQXjUvzrN27aBfFRB304uLyNEZnFVw1KRmiKK8Wtug+2qcky ntYw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=oZ+muMxsYAdOfLFCfYelUSEsPZYYdxDi6dVCQc7XtEo=; b=CEggVFVF67GACq9FwEbciQ1Iorpq7dc70lxLx543E5H4Dc/TtSb8kNaK4YgL+EP/M2 5AmsforH+2AXh5Ov94wiqOlC8GU9tDsyeu1QTuDeucSP8xSWxo4ezZjEx5YDHKllF8uJ J29wxuJonJxs0BC6ZjbwVEwO6r/CyxVDPzJO7tw/BJcfJ/aULdTWQw0PuMGDyab2u0/w soXoPrr29NpGVCEnc/p5NIfgG4Kr+rOTrqM1ucWno0SZXtYSHZMWJ6wfo8+Tl+yJmOpL /9oqUmzO2h3ZdxIMcEaxV8qS1lyQoIw2TkXiaqp1NEe7z+kv8pkB5uEn+MMyJ9SL+4ab MBPw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 74si5473768pgc.808.2022.01.28.08.01.57; Fri, 28 Jan 2022 08:02:11 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239599AbiA0TCU (ORCPT + 99 others); Thu, 27 Jan 2022 14:02:20 -0500 Received: from mail-yb1-f174.google.com ([209.85.219.174]:41967 "EHLO mail-yb1-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238995AbiA0TCT (ORCPT ); Thu, 27 Jan 2022 14:02:19 -0500 Received: by mail-yb1-f174.google.com with SMTP id g14so11572527ybs.8; Thu, 27 Jan 2022 11:02:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oZ+muMxsYAdOfLFCfYelUSEsPZYYdxDi6dVCQc7XtEo=; b=iEv4a7slcmntQU698Y8QAPK4Q8RNk1ObPSD6D+UqFsNt35HzAdQ+MeY8r/aqXj1rTS uJiM5PWFTq7sRHvMGud2k80+EEE9eU9fG3ESSnZ1wujbGfaa9FO6E+bwoOHNa51aEoTy N/1AlmC2vFaAAtItQqAgkpSwBAdFonVyy21tPCaOvxE8KkoxvuTyEFVZQUlrTAn8dy4n aTT7wVVIiiel8NB71XnVJNVpxory23i8hd5XbUMoRyEWUtJnrREow8itQPGiqA7R/VrF LJomre2Ft1DPItC6Dg08zFALj9HfJBu4eeqY4w+xf7sx8bIVgugo70X7y3GHCexMFabL dS+A== X-Gm-Message-State: AOAM532Wgcwm5iZSF4IWHZ+p9SKOuqh5XNrNGghrxxLh1VyU+yywcYZk NF291u+5VDsu3JqLwf6s+hR9B1lobBmhWOebERM= X-Received: by 2002:a25:c102:: with SMTP id r2mr8103463ybf.330.1643310138759; Thu, 27 Jan 2022 11:02:18 -0800 (PST) MIME-Version: 1.0 References: <20220121210905.GA1114868@dhcp-10-100-145-180.wdc.com> In-Reply-To: <20220121210905.GA1114868@dhcp-10-100-145-180.wdc.com> From: "Rafael J. Wysocki" Date: Thu, 27 Jan 2022 20:02:07 +0100 Message-ID: Subject: Re: [Bug] nvme blocks PC10 since v5.15 - bisected To: Keith Busch Cc: "Rafael J. Wysocki" , Sagi Grimberg , Christoph Hellwig , Len Brown , Linux PM , Linux Kernel Mailing List , m.heingbecker@googlemail.com, linux-nvme Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 21, 2022 at 10:09 PM Keith Busch wrote: > > On Fri, Jan 21, 2022 at 08:00:49PM +0100, Rafael J. Wysocki wrote: > > Hi Keith, > > > > It is reported that the following commit > > > > commit e5ad96f388b765fe6b52f64f37e910c0ba4f3de7 > > Author: Keith Busch > > Date: Tue Jul 27 09:40:44 2021 -0700 > > > > nvme-pci: disable hmb on idle suspend > > > > An idle suspend may or may not disable host memory access from devices > > placed in low power mode. Either way, it should always be safe to > > disable the host memory buffer prior to entering the low power mode, and > > this should also always be faster than a full device shutdown. > > > > Signed-off-by: Keith Busch > > Reviewed-by: Sagi Grimberg > > Signed-off-by: Christoph Hellwig > > > > is the source of a serious power regression occurring since 5.15 > > (please see https://bugzilla.kernel.org/show_bug.cgi?id=215467). > > > > After this commit, the SoC on the affected system cannot enter > > C-states deeper than PC2 while suspended to idle which basically > > defeats the purpose of suspending. > > > > What may be happening is that nvme_disable_prepare_reset() that is not > > called any more in the ndev->nr_host_mem_descs case somehow causes the > > LTR of the device to change to "no requirement" which allows deeper > > C-states to be entered. > > > > Can you have a look at this, please? > > I thought platforms that wanted full device shutdown behaviour would > always set acpi_storage_d3. Is that not happening here? Evidently, it isn't. Also that flag is about putting the device into D3, which need not be necessary as long as the LTR is set to "don't care".