From: Bjorn Helgaas <helgaas@kernel.org>
To: veredz72@gmail.com
Cc: linux-pci@vger.kernel.org
Subject: Re: [Bug 216555] New: Kernel 4.19.135: pci_resource_start, pci_resource_len return wrong value
Date: Wed, 5 Oct 2022 11:53:58 -0500 [thread overview]
Message-ID: <20221005165358.GA2298432@bhelgaas> (raw)
In-Reply-To: <bug-216555-41252@https.bugzilla.kernel.org/>
[+cc linux-pci]
On Wed, Oct 05, 2022 at 01:00:58PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216555
> Summary: Kernel 4.19.135: pci_resource_start, pci_resource_len
> return wrong value
> I used 4.19.135(x64) + rootfs (buildroot) to boot an x86 SBC.
> This SBC is connected via PCIe to a customized PCIe IO card.
>
> In the kernel module, I used pci_resource_start, pci_resource_len to find
> start, length of 3 BARs.
> It worked fine.
>
> Then I used the same kernel, kernel module on another x86 SBC.
> In this SBC, pci_resource_start, pci_resource_len returned wrong data.
> I booted this SBC with Centos 8.2 (4.18) and also with vanilla 4.9.20.
> It worked fine.
>
> Is it possible that 4.19.135 has a BUG ?
It's unlikely that pci_resource_start() and pci_resource_len() are
broken in 4.19.135, but I guess anything is possible.
Can you give any more details about why it seems broken? Dmesg logs
of a boot that fails and one that works, for instance?
Bjorn
next parent reply other threads:[~2022-10-05 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216555-41252@https.bugzilla.kernel.org/>
2022-10-05 16:53 ` Bjorn Helgaas [this message]
2022-10-25 17:49 ` [Bug 216555] New: Kernel 4.19.135: pci_resource_start, pci_resource_len return wrong value 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=20221005165358.GA2298432@bhelgaas \
--to=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=veredz72@gmail.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).