From: Bjorn Helgaas <bhelgaas@google.com>
To: Qian Cai <quic_qiancai@quicinc.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: Arm64 double PCI ECAM reservations in acpi_resource_consumer()
Date: Wed, 2 Jun 2021 17:09:35 -0500 [thread overview]
Message-ID: <CAErSpo4=uspbvScDzfEw+NjsVJKYf6=DyrC=Gasw2Qdt1gwXYg@mail.gmail.com> (raw)
In-Reply-To: <c82b61f5-00d4-182f-2bb7-3518adf2ca75@quicinc.com>
[+cc linux-pci]
On Wed, Jun 2, 2021 at 4:49 PM Qian Cai <quic_qiancai@quicinc.com> wrote:
>
> Bjorn, I noticed PCI ECAM could be reserved twice on arm64. Firs time through,
>
> [ 19.087790][ T1] acpi_ns_walk_namespace+0xc0/0x390
> [ 19.092927][ T1] acpi_get_devices+0x160/0x1a4
> [ 19.097629][ T1] acpi_resource_consumer+0x8c/0xc0
> [ 19.102680][ T1] pci_acpi_scan_root+0x158/0x4c8
> [ 19.107555][ T1] acpi_pci_root_add+0x450/0x8e8
> [ 19.112345][ T1] acpi_bus_attach+0x300/0x7d0
> [ 19.116960][ T1] acpi_bus_attach+0x178/0x7d0
> [ 19.121576][ T1] acpi_bus_attach+0x178/0x7d0
> [ 19.126190][ T1] acpi_bus_scan+0xa8/0x170
> [ 19.130545][ T1] acpi_scan_init+0x220/0x558
> [ 19.135074][ T1] acpi_init+0x1f4/0x270
>
> where pci_acpi_setup_ecam_mapping() confirmed all reservations are succeed. Then,
>
> [ 19.880588][ T1] acpi_ns_walk_namespace+0xc0/0x390
> [ 19.885725][ T1] acpi_get_devices+0x160/0x1a4
> [ 19.890426][ T1] pnpacpi_init+0xa0/0x10
>
> As the results, those messages are showed up during the boot in pnpacpi_init().
>
> [ 17.763968] system 00:00: [mem 0x10000000000-0x1000fffffff window] could not be reserved
> [ 17.772900] system 00:00: [mem 0x7800000000-0x780fffffff window] could not be reserved
> [ 17.781627] system 00:00: [mem 0x7000000000-0x700fffffff window] could not be reserved
> [ 17.790350] system 00:00: [mem 0x6000000000-0x600fffffff window] could not be reserved
> [ 17.799073] system 00:00: [mem 0x5800000000-0x580fffffff window] could not be reserved
> [ 17.808155] system 00:00: [mem 0x1000000000-0x100fffffff window] could not be reserved
> [ 17.816862] system 00:00: [mem 0x600000000-0x60fffffff window] could not be reserved
> [ 17.825417] system 00:00: [mem 0x400000000-0x40fffffff window] could not be reserved
>
> Looking through the x86's version of pci_acpi_scan_root(), it won't call acpi_resource_consumer(), so I suppose this bug is only affecting arm64?
This might be related to
https://lore.kernel.org/linux-acpi/20210510234020.1330087-1-luzmaximilian@gmail.com/T/#u
Can you try applying that patch to see if it is related?
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <bhelgaas@google.com>
To: Qian Cai <quic_qiancai@quicinc.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: Arm64 double PCI ECAM reservations in acpi_resource_consumer()
Date: Wed, 2 Jun 2021 17:09:35 -0500 [thread overview]
Message-ID: <CAErSpo4=uspbvScDzfEw+NjsVJKYf6=DyrC=Gasw2Qdt1gwXYg@mail.gmail.com> (raw)
In-Reply-To: <c82b61f5-00d4-182f-2bb7-3518adf2ca75@quicinc.com>
[+cc linux-pci]
On Wed, Jun 2, 2021 at 4:49 PM Qian Cai <quic_qiancai@quicinc.com> wrote:
>
> Bjorn, I noticed PCI ECAM could be reserved twice on arm64. Firs time through,
>
> [ 19.087790][ T1] acpi_ns_walk_namespace+0xc0/0x390
> [ 19.092927][ T1] acpi_get_devices+0x160/0x1a4
> [ 19.097629][ T1] acpi_resource_consumer+0x8c/0xc0
> [ 19.102680][ T1] pci_acpi_scan_root+0x158/0x4c8
> [ 19.107555][ T1] acpi_pci_root_add+0x450/0x8e8
> [ 19.112345][ T1] acpi_bus_attach+0x300/0x7d0
> [ 19.116960][ T1] acpi_bus_attach+0x178/0x7d0
> [ 19.121576][ T1] acpi_bus_attach+0x178/0x7d0
> [ 19.126190][ T1] acpi_bus_scan+0xa8/0x170
> [ 19.130545][ T1] acpi_scan_init+0x220/0x558
> [ 19.135074][ T1] acpi_init+0x1f4/0x270
>
> where pci_acpi_setup_ecam_mapping() confirmed all reservations are succeed. Then,
>
> [ 19.880588][ T1] acpi_ns_walk_namespace+0xc0/0x390
> [ 19.885725][ T1] acpi_get_devices+0x160/0x1a4
> [ 19.890426][ T1] pnpacpi_init+0xa0/0x10
>
> As the results, those messages are showed up during the boot in pnpacpi_init().
>
> [ 17.763968] system 00:00: [mem 0x10000000000-0x1000fffffff window] could not be reserved
> [ 17.772900] system 00:00: [mem 0x7800000000-0x780fffffff window] could not be reserved
> [ 17.781627] system 00:00: [mem 0x7000000000-0x700fffffff window] could not be reserved
> [ 17.790350] system 00:00: [mem 0x6000000000-0x600fffffff window] could not be reserved
> [ 17.799073] system 00:00: [mem 0x5800000000-0x580fffffff window] could not be reserved
> [ 17.808155] system 00:00: [mem 0x1000000000-0x100fffffff window] could not be reserved
> [ 17.816862] system 00:00: [mem 0x600000000-0x60fffffff window] could not be reserved
> [ 17.825417] system 00:00: [mem 0x400000000-0x40fffffff window] could not be reserved
>
> Looking through the x86's version of pci_acpi_scan_root(), it won't call acpi_resource_consumer(), so I suppose this bug is only affecting arm64?
This might be related to
https://lore.kernel.org/linux-acpi/20210510234020.1330087-1-luzmaximilian@gmail.com/T/#u
Can you try applying that patch to see if it is related?
Bjorn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-02 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 21:49 Arm64 double PCI ECAM reservations in acpi_resource_consumer() Qian Cai
2021-06-02 22:09 ` Bjorn Helgaas [this message]
2021-06-02 22:09 ` Bjorn Helgaas
2021-06-03 0:15 ` Qian Cai
2021-06-03 0:15 ` Qian Cai
2021-06-03 14:16 ` Lorenzo Pieralisi
2021-06-03 14:16 ` Lorenzo Pieralisi
2021-06-03 15:44 ` Qian Cai
2021-06-03 15:44 ` Qian Cai
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='CAErSpo4=uspbvScDzfEw+NjsVJKYf6=DyrC=Gasw2Qdt1gwXYg@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=quic_qiancai@quicinc.com \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.