What pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring means?

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX1
1

Hi,

I got the message pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring in the kernel. How do I troubleshoot it?

Thanks.

2

Is this the dev carrier board? And what release is it using (“head -n 1 /etc/nv_tegra_release”)? What is connected to the PCIe slot? Does anything show under “lspci”?

3

Hi,

Yes and is 28.1, nothing is connected to the PCIe slot and lspci return:

00:02.0 PCI bridge: NVIDIA corporation device …
01:00.0 Ethernet controller: …

Can you tell me where in the device tree to look for?

So sorry is pci 0000:00:02.0 bridge configuration invalid, seems that is wrongly configured to bus 00-00 instead of bus 01.

Thanks.

4

I am surprised to see output from lspci with nothing connected. Normally on the TX1/R28.1 the bridge won’t show up unless you have something connected to the external card slot (no device tree change should be required). Is anything custom about this hardware? Or the boot parameters? What is the output of “cat /proc/cmdline”?

5

Any particular option to look at? I got too many to write down.

6

Generally speaking configuration is via the device tree or kernel command line options. With the information given there isn’t any way to be more specific. The “/proc/cmdline” is one source of information, but much more would need to be known about the hardware or modifications.

7

fbcon=map:0 console=tty0 console=ttyUSB0,115200n8 console=ttyS0,115200n8 tegraid=21.1.2.0.0 memtype=0 vpr_resize ddr_die=1536M@2048M ddr_die=1536M@3584M section=256M usb_port_owner_info=1 lane_owner_info=0 emc_max_dvfs=1 touch_id=0@63 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff2bf000 nvdumper_reserved=0xff23f000 core_edp_mv=1075 core_edp_ma=4000 power_supply=Adapter androidboot.modem=none androidboot.serialno=0324616166364 androidboot.security=enabled gpt android.kerneltype=normal androidboot.touch_vendor_id=0 androidboot.touch_panel_id=63 androidboot.touch_feature=0 no_console_suspend=1 debug_uartport=lsport,2 earlyprintk=uart8250-32bit,0x70006000 is_hdmi_initialised=1

8

This is a modified kernel command line. Was extlinux.conf or U-Boot modified? One very problematic missing parameter is the “root=/dev/mmcblk0p1”.

9

Yes, but does not matter, it works.

I think this message is normal but possibly worded more alarmingly than necessary.

Probably because the bridge has not been enumerated yet.

10

Yes, if something caused the bus to attempt enumeration early on (possibly before configuration was completed), then I would expect a message such as this since it doesn’t know configuration was incomplete. There is always a tug-of-war between “clear” and “sufficiently terse/minimal” messages.