From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
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.
Date: Mon, 5 Aug 2019 18:08:03 +0300 [thread overview]
Message-ID: <20190805150803.GU2640@lahna.fi.intel.com> (raw)
In-Reply-To: <0d234153-3c30-c0da-7419-220528897fbf@gmx.de>
On Mon, Aug 05, 2019 at 04:01:11PM +0200, Matthias Andree wrote:
> Am 05.08.19 um 15:00 schrieb Mika Westerberg:
> > On Mon, Aug 05, 2019 at 07:47:05AM -0500, Bjorn Helgaas wrote:
> >> 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.
> > Right, thanks for the correction.
>
> Hi Mika, Bjorn,
>
> thanks for picking this up. I have used pcieportdrv.dyndbg=+p (not sure
> if something else would have worked) and was lucky that I could transfer
> dmesg to a USB stick before the machine went completely unusable.
>
> $ grep pcieport dmesg.txt
>
> [ 0.698739] pcieport 0000:00:01.3: Signaling PME with IRQ 28
> [ 0.698799] pcieport 0000:00:01.3: AER: enabled with IRQ 28
> [ 0.698966] pcieport 0000:00:03.1: Signaling PME with IRQ 29
> [ 0.699017] pcieport 0000:00:03.1: AER: enabled with IRQ 29
> [ 0.699188] pcieport 0000:00:07.1: Signaling PME with IRQ 30
> [ 0.699230] pcieport 0000:00:07.1: AER: enabled with IRQ 30
> [ 0.699816] pcieport 0000:00:08.1: Signaling PME with IRQ 31
> [ 0.699860] pcieport 0000:00:08.1: AER: enabled with IRQ 31
> [ 119.637492] pcieport 0000:00:03.1: waiting downstream link for 100 ms
> [ 119.649285] pcieport 0000:00:08.1: waiting downstream link for 100 ms
> [ 119.649287] pcieport 0000:00:07.1: waiting downstream link for 100 ms
> [ 119.649376] pcieport 0000:00:01.3: waiting downstream link for 100 ms
> [ 119.803025] pcieport 0000:16:08.0: waiting downstream link for 100 ms
> [ 119.803031] pcieport 0000:16:01.0: waiting downstream link for 100 ms
Can you also attach the dmesg.txt to the bugzilla entry?
next prev parent reply other threads:[~2019-08-05 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 19:03 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 Matthias Andree
2019-08-05 12:27 ` Mika Westerberg
2019-08-05 12:47 ` Bjorn Helgaas
2019-08-05 13:00 ` Mika Westerberg
2019-08-05 14:01 ` Matthias Andree
2019-08-05 15:08 ` Mika Westerberg [this message]
2019-08-05 15:56 ` Matthias Andree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190805150803.GU2640@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthias.andree@gmx.de \
--cc=rafael.j.wysocki@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox