Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Jan Palus <jpalus@fastmail.com>
Cc: "Rob Herring" <robh@kernel.org>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Pali Rohár" <pali@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [Bug 220479] New: [regression 6.16] mvebu: no pci devices detected on turris omnia
Date: Wed, 20 Aug 2025 14:30:55 -0500	[thread overview]
Message-ID: <20250820193055.GA636030@bhelgaas> (raw)
In-Reply-To: <gn4sih6yrohqn35jc3hesxpgqhodtvq44ad7a6tbmknjywowvk@p2y24kjlnprd>

On Wed, Aug 20, 2025 at 09:08:33PM +0200, Jan Palus wrote:
> On 20.08.2025 13:46, Bjorn Helgaas wrote:
> > [+cc maintainers, regressions list]
> > 
> > Jan, thanks very much for the report and the bisection.  Could you
> > attach the devicetree you're using to the bugzilla?
> 
> I guess I could dump it from running system if you'd like me to, but it's
> an upstream one without any customizations.

It's just easier if we know exactly what you're using.  I'm not an
mvebu user and can't guess.

> > On Wed, Aug 20, 2025 at 05:43:39PM +0000, bugzilla-daemon@kernel.org wrote:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=220479
> > > 
> > >            Summary: [regression 6.16] mvebu: no pci devices detected on
> > >                     turris omnia
> > >           Reporter: jpalus@fastmail.com
> > > 
> > > Booting kernel 6.16 results in no PCI devices being detected (output of `lspci`
> > > is completely empty). Bisected to:
> > > 
> > > 5da3d94a23c6c1ee1f896aeeb00965eacf1d0bb3 is the first new commit
> > > commit 5da3d94a23c6c1ee1f896aeeb00965eacf1d0bb3 (HEAD)
> > > Author: Rob Herring (Arm) <robh@kernel.org>
> > > Date:   Thu Nov 7 16:32:55 2024
> > > 
> > >     PCI: mvebu: Use for_each_of_range() iterator for parsing "ranges"
> > > 
> > >     The mvebu "ranges" is a bit unusual with its own encoding of addresses,
> > >     but it's still just normal "ranges" as far as parsing is concerned.
> > >     Convert mvebu_get_tgt_attr() to use the for_each_of_range() iterator
> > >     instead of open coding the parsing.
> > > 
> > >     Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> > >     Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > >     Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > >     Link: https://patch.msgid.link/20241107153255.2740610-1-robh@kernel.org
> > > 
> > >  drivers/pci/controller/pci-mvebu.c | 26 +++++++++-----------------
> > >  1 file changed, 9 insertions(+), 17 deletions(-)
> > > 
> > > 
> > > kernel 6.16 logs following mesages related to PCI:
> > > 
> > > mvebu-pcie soc:pcie: host bridge /soc/pcie ranges:
> > > mvebu-pcie soc:pcie:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
> > > mvebu-pcie soc:pcie:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
> > > mvebu-pcie soc:pcie:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
> > > mvebu-pcie soc:pcie:      MEM 0x00f1048000..0x00f1049fff -> 0x0000048000
> > > mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
> > > mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
> > > mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
> > > mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
> > > mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
> > > mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
> > > mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
> > > mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
> > > mvebu-pcie soc:pcie: pcie0.0: cannot get tgt/attr for mem window
> > > mvebu-pcie soc:pcie: pcie1.0: cannot get tgt/attr for mem window
> > > mvebu-pcie soc:pcie: pcie2.0: cannot get tgt/attr for mem window
> > > mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
> > > pci_bus 0000:00: root bus resource [bus 00-ff]
> > > pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address
> > > [0x00080000-0x00081fff])
> > > pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address
> > > [0x00040000-0x00041fff])
> > > pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address
> > > [0x00044000-0x00045fff])
> > > pci_bus 0000:00: root bus resource [mem 0xf1048000-0xf1049fff] (bus address
> > > [0x00048000-0x00049fff])
> > > pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
> > > pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
> > > PCI: bus0: Fast back to back transfers enabled
> > > pci_bus 0000:00: resource 4 [mem 0xf1080000-0xf1081fff]
> > > pci_bus 0000:00: resource 5 [mem 0xf1040000-0xf1041fff]
> > > pci_bus 0000:00: resource 6 [mem 0xf1044000-0xf1045fff]
> > > pci_bus 0000:00: resource 7 [mem 0xf1048000-0xf1049fff]
> > > pci_bus 0000:00: resource 8 [mem 0xe0000000-0xe7ffffff]
> > > pci_bus 0000:00: resource 9 [io  0x1000-0xeffff]
> > > 
> > > 
> > > while kernel 6.15 logs following:
> > > 
> > > mvebu-pcie soc:pcie: host bridge /soc/pcie ranges:
> > > mvebu-pcie soc:pcie:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
> > > mvebu-pcie soc:pcie:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
> > > mvebu-pcie soc:pcie:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
> > > mvebu-pcie soc:pcie:      MEM 0x00f1048000..0x00f1049fff -> 0x0000048000
> > > mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
> > > mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
> > > mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
> > > mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
> > > mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
> > > mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
> > > mvebu-pcie soc:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
> > > mvebu-pcie soc:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
> > > mvebu-pcie soc:pcie: pcie0.0: Slot power limit 10.0W
> > > mvebu-pcie soc:pcie: pcie1.0: Slot power limit 10.0W
> > > mvebu-pcie soc:pcie: pcie2.0: Slot power limit 10.0W
> > > mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
> > > pci_bus 0000:00: root bus resource [bus 00-ff]
> > > pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address
> > > [0x00080000-0x00081fff])
> > > pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address
> > > [0x00040000-0x00041fff])
> > > pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address
> > > [0x00044000-0x00045fff])
> > > pci_bus 0000:00: root bus resource [mem 0xf1048000-0xf1049fff] (bus address
> > > [0x00048000-0x00049fff])
> > > pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
> > > pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
> > > pci 0000:00:01.0: [11ab:6820] type 01 class 0x060400 PCIe Root Port
> > > pci 0000:00:01.0: PCI bridge to [bus 00]
> > > pci 0000:00:01.0:   bridge window [io  0x0000-0x0fff]
> > > pci 0000:00:01.0:   bridge window [mem 0x00000000-0x000fffff]
> > > /soc/pcie/pcie@1,0: Fixed dependency cycle(s) with
> > > /soc/pcie/pcie@1,0/interrupt-controller
> > > pci 0000:00:02.0: [11ab:6820] type 01 class 0x060400 PCIe Root Port
> > > pci 0000:00:02.0: PCI bridge to [bus 00]
> > > pci 0000:00:02.0:   bridge window [io  0x0000-0x0fff]
> > > pci 0000:00:02.0:   bridge window [mem 0x00000000-0x000fffff]
> > > /soc/pcie/pcie@2,0: Fixed dependency cycle(s) with
> > > /soc/pcie/pcie@2,0/interrupt-controller
> > > pci 0000:00:03.0: [11ab:6820] type 01 class 0x060400 PCIe Root Port
> > > pci 0000:00:03.0: PCI bridge to [bus 00]
> > > pci 0000:00:03.0:   bridge window [io  0x0000-0x0fff]
> > > pci 0000:00:03.0:   bridge window [mem 0x00000000-0x000fffff]
> > > /soc/pcie/pcie@3,0: Fixed dependency cycle(s) with
> > > /soc/pcie/pcie@3,0/interrupt-controller
> > > PCI: bus0: Fast back to back transfers disabled
> > > pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
> > > pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
> > > pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
> > > PCI: bus1: Fast back to back transfers enabled
> > > pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
> > > pci 0000:02:00.0: [168c:003c] type 00 class 0x028000 PCIe Endpoint
> > > pci 0000:02:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]
> > > pci 0000:02:00.0: ROM [mem 0x00000000-0x0000ffff pref]
> > > pci 0000:02:00.0: supports D1
> > > pci 0000:02:00.0: PME# supported from D0 D1 D3hot
> > > pci 0000:00:02.0: ASPM: current common clock configuration is inconsistent,
> > > reconfiguring
> > > pci 0000:00:02.0: ASPM: Bridge does not support changing Link Speed to 2.5 GT/s
> > > pci 0000:00:02.0: ASPM: Retrain Link at higher speed is disallowed by quirk
> > > PCI: bus2: Fast back to back transfers disabled
> > > pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
> > > pci 0000:03:00.0: [168c:0033] type 00 class 0x028000 PCIe Endpoint
> > > pci 0000:03:00.0: BAR 0 [mem 0x00000000-0x0001ffff 64bit]
> > > pci 0000:03:00.0: ROM [mem 0x00000000-0x0000ffff pref]
> > > pci 0000:03:00.0: supports D1
> > > pci 0000:03:00.0: PME# supported from D0 D1 D3hot
> > > pci 0000:00:03.0: ASPM: current common clock configuration is inconsistent,
> > > reconfiguring
> > > pci 0000:00:03.0: ASPM: Bridge does not support changing Link Speed to 2.5 GT/s
> > > pci 0000:00:03.0: ASPM: Retrain Link at higher speed is disallowed by quirk
> > > PCI: bus3: Fast back to back transfers disabled
> > > pci_bus 0000:03: busn_res: [bus 03-ff] end is updated to 03
> > > pci 0000:00:02.0: bridge window [mem 0x00200000-0x003fffff] to [bus 02]
> > > add_size 200000 add_align 200000
> > > pci 0000:00:02.0: bridge window [mem 0xe0000000-0xe03fffff]: assigned
> > > pci 0000:00:03.0: bridge window [mem 0xe0400000-0xe04fffff]: assigned
> > > pci 0000:00:01.0: PCI bridge to [bus 01]
> > > pci 0000:02:00.0: BAR 0 [mem 0xe0000000-0xe01fffff 64bit]: assigned
> > > pci 0000:02:00.0: ROM [mem 0xe0200000-0xe020ffff pref]: assigned
> > > pci 0000:00:02.0: PCI bridge to [bus 02]
> > > pci 0000:00:02.0:   bridge window [mem 0xe0000000-0xe03fffff]
> > > pci 0000:03:00.0: BAR 0 [mem 0xe0400000-0xe041ffff 64bit]: assigned
> > > pci 0000:03:00.0: ROM [mem 0xe0420000-0xe042ffff pref]: assigned
> > > pci 0000:00:03.0: PCI bridge to [bus 03]
> > > pci 0000:00:03.0:   bridge window [mem 0xe0400000-0xe04fffff]
> > > pci_bus 0000:00: resource 4 [mem 0xf1080000-0xf1081fff]
> > > pci_bus 0000:00: resource 5 [mem 0xf1040000-0xf1041fff]
> > > pci_bus 0000:00: resource 6 [mem 0xf1044000-0xf1045fff]
> > > pci_bus 0000:00: resource 7 [mem 0xf1048000-0xf1049fff]
> > > pci_bus 0000:00: resource 8 [mem 0xe0000000-0xe7ffffff]
> > > pci_bus 0000:00: resource 9 [io  0x1000-0xeffff]
> > > pci_bus 0000:02: resource 1 [mem 0xe0000000-0xe03fffff]
> > > pci_bus 0000:03: resource 1 [mem 0xe0400000-0xe04fffff]
> > > pcieport 0000:00:02.0: enabling device (0140 -> 0142)
> > > pcieport 0000:00:03.0: enabling device (0140 -> 0142)
> > 
> > #regzbot introduced: 5da3d94a23c6 ("PCI: mvebu: Use for_each_of_range() iterator for parsing "ranges"")


  reply	other threads:[~2025-08-21  0:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-220479-41252@https.bugzilla.kernel.org/>
2025-08-20 18:46 ` [Bug 220479] New: [regression 6.16] mvebu: no pci devices detected on turris omnia Bjorn Helgaas
2025-08-20 19:08   ` Jan Palus
2025-08-20 19:30     ` Bjorn Helgaas [this message]
2025-08-20 19:51       ` Jan Palus
2025-08-21  0:45   ` Jan Palus
2025-09-02  9:09     ` Klaus Kudielka
2025-09-02 10:33       ` Klaus Kudielka
2025-09-02 20:32   ` Pali Rohár
2025-09-03  1:35     ` Rob Herring
2025-09-03  7:35       ` Pali Rohár
2025-09-03  7:50         ` Manivannan Sadhasivam

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=20250820193055.GA636030@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=jpalus@fastmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=thomas.petazzoni@bootlin.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