From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=UhFO=WB=vger.kernel.org=linux-pci-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,
	USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 9F35EC0650F
	for <linux-pci@archiver.kernel.org>; Mon,  5 Aug 2019 12:47:08 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
	by mail.kernel.org (Postfix) with ESMTP id 6FE2420B1F
	for <linux-pci@archiver.kernel.org>; Mon,  5 Aug 2019 12:47:08 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=default; t=1565009228;
	bh=h7SfAciD2Px7XN6QUh4y+tAAK3kYv0LTgrkeiN8HNZE=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From;
	b=toaIcDyavYFbSvyEd8kDLb33kaInVGfohryu6EJOEzuKKR0LBqYR0mxK0Qtq2VwHd
	 ZyVpDZ1CU24/67XsV3Nu79T2aklByn/ZJzgtxVPIm/NqvFlEsIT9FyH4ZfqN3CCtC6
	 ED3W7/FGN6OvNzogk/zlGsO7LC3w2qC3TSyRvcNw=
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1727553AbfHEMrH (ORCPT <rfc822;linux-pci@archiver.kernel.org>);
        Mon, 5 Aug 2019 08:47:07 -0400
Received: from mail.kernel.org ([198.145.29.99]:35012 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1727357AbfHEMrH (ORCPT <rfc822;linux-pci@vger.kernel.org>);
        Mon, 5 Aug 2019 08:47:07 -0400
Received: from localhost (173-25-83-245.client.mchsi.com [173.25.83.245])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by mail.kernel.org (Postfix) with ESMTPSA id BE952205C9;
        Mon,  5 Aug 2019 12:47:06 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=default; t=1565009227;
        bh=h7SfAciD2Px7XN6QUh4y+tAAK3kYv0LTgrkeiN8HNZE=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=cVZYaAUW0k4J9VxVFIKF7kW0vWTLQyJUPrq2chA0gTyWGbDpKXQDdFcITGr1wjveF
         tIx8SqLr8WtXounIvPTAXzaWApRbT8RnMroJ0lQzEJf3Hih/0ocyq333O7c9VRSxUa
         +vPjfAjOfZpb3sHYNtvfjK1o9yjXIUyQrxF0+YAw=
Date:   Mon, 5 Aug 2019 07:47:05 -0500
From:   Bjorn Helgaas <helgaas@kernel.org>
To:     Mika Westerberg <mika.westerberg@linux.intel.com>
Cc:     Matthias Andree <matthias.andree@gmx.de>,
        linux-pci@vger.kernel.org,
        "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: regression: PCIe resume from suspend stalls I/O and causes
 interrupt storms in Linux 5.3-rc2 (5.2.5, 5.1.20) on Ryzen 7 1700/AMD X370
 MSI board since 5817d78eba34f6c86f5462ae2c5212f80a013357, 5.2/5.3 w/ pcieIRQ
 loop.
Message-ID: <20190805124704.GP151852@google.com>
References: <935c6fd8-c606-836a-9e59-772b9111d5d6@gmx.de>
 <20190805122751.GL2640@lahna.fi.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190805122751.GL2640@lahna.fi.intel.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-pci-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-pci.vger.kernel.org>
X-Mailing-List: linux-pci@vger.kernel.org

On Mon, Aug 05, 2019 at 03:27:51PM +0300, Mika Westerberg wrote:
> Are you able to get dmesg after resume or is it completely dead? It
> would help you we could see how long it tries to wait for the downstream
> link by passing "pciepordrv.dyndbg" to the kernel command line.

"pcieportdrv.dyndbg" (with "t"), I think.