From: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Logan Gunthorpe <logang@deltatee.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Possible PCI Regression Linux 5.3-rc1
Date: Wed, 24 Jul 2019 12:54:00 +0000 [thread overview]
Message-ID: <SL2P216MB01878BBCD75F21D882AEEA2880C60@SL2P216MB0187.KORP216.PROD.OUTLOOK.COM> (raw)
Hi all,
I was just rebasing my patches for linux 5.3-rc1 and noticed a possible
regression that shows on both of my machines. It is also reproducible
with the unmodified Ubuntu mainline kernel, downloadable at [1].
Running the lspci command takes 1-3 seconds with 5.3-rc1 (rather than an
imperceivable amount of time). Booting with pci.dyndbg does not reveal
why.
$ uname -r
5.3.0-050300rc1-generic
$ time lspci -vt 1>/dev/null
real 0m2.321s
user 0m0.026s
sys 0m0.000s
If none of you are aware of this or what is causing it, I will submit a
bug report to Bugzilla.
I am away from 2019-07-27 to mid 2019-08-04. I will post my patches for
5.3-rc1 before I leave. If possible, please have a quick look over them
while I am away for trivial changes or oopsies for me to fix, so that I
can fire off another series ASAP, so that later when we do a full
analysis, there are less problems.
Thank you!
Kind regards,
Nicholas Johnson
[1]
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc1/
next reply other threads:[~2019-07-24 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 12:54 Nicholas Johnson [this message]
2019-07-24 13:38 ` Possible PCI Regression Linux 5.3-rc1 Bjorn Helgaas
2019-07-24 15:48 ` Logan Gunthorpe
2019-07-25 13:21 ` Nicholas Johnson
2019-07-25 13:18 ` Nicholas Johnson
2019-07-25 15:50 ` Logan Gunthorpe
2019-08-04 8:47 ` Nicholas Johnson
2019-08-05 8:59 ` Nicholas Johnson
2019-08-05 12:34 ` Mika Westerberg
2019-08-05 14:09 ` Nicholas Johnson
2019-08-05 14:25 ` Nicholas Johnson
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=SL2P216MB01878BBCD75F21D882AEEA2880C60@SL2P216MB0187.KORP216.PROD.OUTLOOK.COM \
--to=nicholas.johnson-opensource@outlook.com.au \
--cc=benh@kernel.crashing.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mika.westerberg@linux.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;
as well as URLs for NNTP newsgroup(s).