From: Logan Gunthorpe <logang@deltatee.com>
To: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Possible PCI Regression Linux 5.3-rc1
Date: Thu, 25 Jul 2019 09:50:48 -0600 [thread overview]
Message-ID: <4f5afb8e-9013-980f-0553-c687d17ed8d5@deltatee.com> (raw)
In-Reply-To: <SL2P216MB0187E2042E5DB8D9F29E665280C10@SL2P216MB0187.KORP216.PROD.OUTLOOK.COM>
On 2019-07-25 7:18 a.m., Nicholas Johnson wrote:
> On Wed, Jul 24, 2019 at 08:38:14AM -0500, Bjorn Helgaas wrote:
>> On Wed, Jul 24, 2019 at 12:54:00PM +0000, Nicholas Johnson wrote:
>>> 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 wasn't aware of this; thanks for reporting it! I wasn't able to
>> reproduce this in qemu. Can you play with "strace -r lspci -vt" and
>> the like? Maybe try "lspci -n" to see if it's related to looking up
>> the names?
>
> For a second you had me doubting myself - it could have been a Ubuntu
> thing. But no, I just reproduced it on Arch Linux, and double checked
> that it was not doing it on 5.2. Also, the problem occurs even without
> the PCI kernel parameters which I usually pass.
Ok, can you bisect to find the commit that causes this issue?
Thanks,
Logan
next prev parent reply other threads:[~2019-07-25 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 12:54 Possible PCI Regression Linux 5.3-rc1 Nicholas Johnson
2019-07-24 13:38 ` 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 [this message]
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=4f5afb8e-9013-980f-0553-c687d17ed8d5@deltatee.com \
--to=logang@deltatee.com \
--cc=benh@kernel.crashing.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=nicholas.johnson-opensource@outlook.com.au \
/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).