From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f49.google.com ([209.85.215.49]:33085 "EHLO mail-lf0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755246AbbK0WX7 (ORCPT ); Fri, 27 Nov 2015 17:23:59 -0500 MIME-Version: 1.0 In-Reply-To: <1448648254-12639-1-git-send-email-imre.deak@intel.com> References: <1447844188-21999-1-git-send-email-imre.deak@intel.com> <1448648254-12639-1-git-send-email-imre.deak@intel.com> Date: Fri, 27 Nov 2015 23:23:57 +0100 Message-ID: Subject: Re: [PATCH v3] PCI / PM: tune down RPM suspend error message with EBUSY and EAGAIN retval From: "Rafael J. Wysocki" To: Imre Deak Cc: Bjorn Helgaas , "Rafael J. Wysocki" , Jani Nikula , Daniel Vetter , Linux PM , intel-gfx@lists.freedesktop.org, Linux PCI Content-Type: text/plain; charset=UTF-8 Sender: linux-pci-owner@vger.kernel.org List-ID: On Fri, Nov 27, 2015 at 7:17 PM, Imre Deak wrote: > The runtime PM core doesn't treat EBUSY and EAGAIN retvals from the driver > suspend hooks as errors, but they still show up as errors in dmesg. Tune > them down. > > One problem caused by this was noticed by Daniel: the i915 driver > returns EAGAIN to signal a temporary failure to suspend and as a request > towards the RPM core for scheduling a suspend again. This is a normal > event, but the resulting error message flags a breakage during the > driver's automated testing which parses dmesg and picks up the error. > > v2: > - fix compile breake when CONFIG_PM_SLEEP=n (0-day builder) > v3: > - instead of modifying the suspend_report_result() helper to disinguish > between the runtime and system suspend case, inline the error > printing, it's not used anywhere else (Rafael) > > Reported-by: Daniel Vetter > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92992 > CC: Bjorn Helgaas > CC: Rafael J. Wysocki > Signed-off-by: Imre Deak > --- > drivers/pci/pci-driver.c | 15 +++++++++++++-- > 1 file changed, 13 insertions(+), 2 deletions(-) > > diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c > index 4446fcb..67eb4ac 100644 > --- a/drivers/pci/pci-driver.c > +++ b/drivers/pci/pci-driver.c > @@ -1146,9 +1146,20 @@ static int pci_pm_runtime_suspend(struct device *dev) > pci_dev->state_saved = false; > pci_dev->no_d3cold = false; > error = pm->runtime_suspend(dev); > - suspend_report_result(pm->runtime_suspend, error); > - if (error) > + if (error) { > + /* > + * -EBUSY and -EAGAIN is used to request the runtime PM core > + * to schedule a new suspend, so don't flag it as an error. > + */ KERN_DEBUG and KERN_ERR are log levels, not flags. Besides, maybe we can use pr_err() and pr_debug() here? > + if (error == -EBUSY || error == -EAGAIN) > + printk(KERN_DEBUG "%s(): %pF returns %d\n", __func__, > + pm->runtime_suspend, error); > + else > + printk(KERN_ERR "%s(): %pF returns %d\n", __func__, > + pm->runtime_suspend, error); > + > return error; > + } > if (!pci_dev->d3cold_allowed) > pci_dev->no_d3cold = true; > > -- Thanks, Rafael