* Re: [Bug 216555] New: Kernel 4.19.135: pci_resource_start, pci_resource_len return wrong value [not found] <bug-216555-41252@https.bugzilla.kernel.org/> @ 2022-10-05 16:53 ` Bjorn Helgaas 2022-10-25 17:49 ` Bjorn Helgaas 0 siblings, 1 reply; 2+ messages in thread From: Bjorn Helgaas @ 2022-10-05 16:53 UTC (permalink / raw) To: veredz72; +Cc: linux-pci [+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 ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bug 216555] New: Kernel 4.19.135: pci_resource_start, pci_resource_len return wrong value 2022-10-05 16:53 ` [Bug 216555] New: Kernel 4.19.135: pci_resource_start, pci_resource_len return wrong value Bjorn Helgaas @ 2022-10-25 17:49 ` Bjorn Helgaas 0 siblings, 0 replies; 2+ messages in thread From: Bjorn Helgaas @ 2022-10-25 17:49 UTC (permalink / raw) To: Zvika Vered; +Cc: linux-pci On Wed, Oct 05, 2022 at 11:53:58AM -0500, Bjorn Helgaas wrote: > 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? I see that you attached a dmesg log and some more details to the bugzilla, thank you! I don't see "AdtIoInit" in the kernel tree, and I can't match the [1172:0001] with anything. Can you also attach the driver source to the bugzilla? Bjorn ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-10-25 17:49 UTC | newest] Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <bug-216555-41252@https.bugzilla.kernel.org/> 2022-10-05 16:53 ` [Bug 216555] New: Kernel 4.19.135: pci_resource_start, pci_resource_len return wrong value Bjorn Helgaas 2022-10-25 17:49 ` Bjorn Helgaas
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).