From: Bhanu Seshu Kumar Valluri <bhanuseshukumar@gmail.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
bhelgaas@google.com, kw@linux.com,
LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, lucas.demarchi@intel.com,
rafael.j.wysocki@intel.com,
Manivannan Sadhasivam <mani@kernel.org>,
bhanuseshukumar@gmail.com
Subject: Re: [PATCH 1/2] PCI: Setup bridge resources earlier
Date: Mon, 27 Oct 2025 13:40:10 +0530 [thread overview]
Message-ID: <81fd91f2-638c-466d-9b27-705a44632713@gmail.com> (raw)
In-Reply-To: <b3a49920-1cff-4ea2-519a-318030ba8797@linux.intel.com>
On 21/10/25 00:16, Ilpo Järvinen wrote:
> On Sat, 18 Oct 2025, Bhanu Seshu Kumar Valluri wrote:
>
>> On 18/10/25 00:22, Bjorn Helgaas wrote:
>>> On Fri, Oct 17, 2025 at 11:52:58PM +0530, Bhanu Seshu Kumar Valluri wrote:
>>>>
>>>> I want to report that this PATCH also break PCI RC port on TI-AM64-EVM.
>>>>
>>>> I did git bisect and it pointed to the a43ac325c7cb ("PCI: Set up bridge resources earlier")
>>>>
>>>> Happy to help if any testing or logs are required.
>>>
>>> Thanks for the report! Can you test this patch?
>>>
>>> https://patch.msgid.link/20251014163602.17138-1-ilpo.jarvinen@linux.intel.com
>>>
>>> That patch is queued up as
>>> https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/commit/?id=469276c06aff
>>> and should appear in v6.18-rc2 on Sunday if all goes well.
>>>
>>> If that doesn't work, let us know and we'll debug this further.
>>
>> I applied above patch on top of commit f406055cb18c ("Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux")
>>
>> Did pci rescan and run kselftest (pci_endpoint_test). It is working.
>>
>> Thanks for the patch.
>
> Thanks for testing the revert.
>
>> Happy to help if any testing or logs are required.
>
> I'd be interested to understand what goes wrong with the change I was
> trying to make as I want to attempt the same change later, but with all
> known issues solved by supporting changes, obviously :-).
>
> The log snippets you provided are unfortunately too short to contain all
> the necessary information (missing e.g. root bus resources and possibly
> other helpful details).
>
> So if you could provide dmesg and /proc/iomem contents from broken and
> working (with the revert) cases to let me easily compare them, that would
> help. Please take the dmesg with dyndbg="file drivers/pci/*.c +p" on
> kernel's cmdline.
>
> No further actions needed beyond that until later if I need to test some
> of those supporting changes before retrying all this in the mainline. It
> may take some time, even more than one kernel cycle as there have been
> quite many regressions.
>
>
Hi
I captured logs with dyndbg="file drivers/pci/*.c +p. See the links below.
Working kernel logs
https://github.com/bhanuseshukumar/kernel_logs/blob/main/working_log
Non Working kernel logs
https://github.com/bhanuseshukumar/kernel_logs/blob/main/not_working_log
Happy to help if any testing or logs are required.
Regards,
Bhanu Seshu Kumvar Valluri
next prev parent reply other threads:[~2025-10-27 8:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 13:42 [PATCH 0/2] PCI: Fix bogus resource overlaps Ilpo Järvinen
2025-09-24 13:42 ` [PATCH 1/2] PCI: Setup bridge resources earlier Ilpo Järvinen
2025-10-06 8:00 ` Val Packett
2025-10-06 10:46 ` Ilpo Järvinen
2025-10-06 20:08 ` Val Packett
2025-10-07 15:43 ` Ilpo Järvinen
2025-10-09 7:29 ` Val Packett
2025-10-10 17:01 ` Ilpo Järvinen
2025-10-12 6:29 ` Val Packett
2025-10-16 7:42 ` Manivannan Sadhasivam
2025-10-13 21:01 ` Bjorn Helgaas
2025-10-28 22:47 ` Bjorn Helgaas
2025-10-30 22:08 ` Bjorn Helgaas
2025-10-13 18:07 ` Guenter Roeck
2025-10-14 11:20 ` Ilpo Järvinen
2025-10-17 18:22 ` Bhanu Seshu Kumar Valluri
2025-10-17 18:27 ` Bhanu Seshu Kumar Valluri
2025-10-17 18:52 ` Bjorn Helgaas
2025-10-18 1:57 ` Bhanu Seshu Kumar Valluri
2025-10-20 18:46 ` Ilpo Järvinen
2025-10-27 8:10 ` Bhanu Seshu Kumar Valluri [this message]
2025-10-27 13:49 ` Ilpo Järvinen
2025-09-24 13:42 ` [PATCH 2/2] PCI: Resources outside their window must set IORESOURCE_UNSET Ilpo Järvinen
2025-09-25 21:21 ` Bjorn Helgaas
2025-09-26 12:21 ` Ilpo Järvinen
2025-09-26 19:30 ` Bjorn Helgaas
2025-09-29 10:34 ` Ilpo Järvinen
2025-09-30 15:47 ` Geert Uytterhoeven
2025-09-30 16:32 ` Ilpo Järvinen
2025-10-01 11:49 ` Geert Uytterhoeven
2025-10-01 13:06 ` Ilpo Järvinen
2025-10-01 14:08 ` Geert Uytterhoeven
2025-10-02 14:54 ` Ilpo Järvinen
2025-10-02 15:25 ` Geert Uytterhoeven
2025-10-02 16:59 ` Ilpo Järvinen
2025-10-03 8:36 ` Geert Uytterhoeven
2025-10-03 14:58 ` Ilpo Järvinen
2025-10-06 10:14 ` Geert Uytterhoeven
2025-10-06 12:37 ` Ilpo Järvinen
2025-10-06 13:17 ` Geert Uytterhoeven
2025-10-07 17:30 ` Ilpo Järvinen
2025-10-08 8:40 ` Kai-Heng Feng
2025-10-08 13:57 ` Geert Uytterhoeven
2025-09-24 23:48 ` [PATCH 0/2] PCI: Fix bogus resource overlaps Bjorn Helgaas
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=81fd91f2-638c-466d-9b27-705a44632713@gmail.com \
--to=bhanuseshukumar@gmail.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mani@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).