hello
question : i got a pcie device microchip pcie switch with xavier ,but the xavier can boot
here is the dmesg log:
below is the messages:
xavier 启动失败.txt (42.7 KB)
printf
WARNING: at platform/drivers/mailbox/mail_mach.c:177
WARNING: at platform/drivers/mailbox/mail_mach.c:161
WARNING: at platform/drivers/mailbox/mail_mach.c:177
WARNING: at platform/drivers/mailbox/mail_mach.c:161
WARNING: at platform/drivers/mailbox/mail_mach.c:177
Hi
Maybe try to add pcie_aspm=off to the Kernel Command Line in the file /boot/extlinux/extlinux.conf.
Best regards
thanks for you replay,i will try
hi sevm89:
I am back,after the Spring Festival,and test at the first time.
but it seems add pcie_aspm=off not worked
the log is still like this：
WARNING: at platform/drivers/mailbox/mail_mach.c:161
WARNING: at platform/drivers/mailbox/mail_mach.c:177
WARNING: at platform/drivers/mailbox/mail_mach.c:161
WARNING: at platform/drivers/mailbox/mail_mach.c:177
WARNING: at platform/drivers/mailbox/mail_mach.c:161
WARNING: at platform/drivers/mailbox/mail_mach.c:177
WARNING: at platform/drivers/mailbox/mail_mach.c:161
WARNING: at platform/drivers/mailbox/mail_mach.c:177
WARNING: at platform/drivers/mailbox/mail_mach.c:161
WARNING: at platform/drivers/mailbox/mail_mach.c:177
WARNING: at platform/drivers/mailbox/mail_mach.c:161
WARNING: at platform/drivers/mailbox/mail_mach.c:177
WARNING: at platform/drivers/mailbox/mail_mach.c:161
WARNING: at platform/drivers/mailbox/mail_mach.c:177
WARNING: at platform/drivers/mailbox/mail_mach.c:161
WARNING: at platform/drivers/mailbox/mail_mach.c:177
WARNING: at platform/drivers/mailbox/mail_mach.c:161
the last log:
] I> CLR PCIE_APB:6
[0016.980] I> tegrabl_pcie_soc_init: (5):
[0016.984] I> APPL initialization …
[0016.987] I> poweron phys
[0016.990] I> tegrabl_locate_pcie_ctrl_in_dt: found match at 0x141a0000
[0016.996] I> tegrabl_power_on_phy: power on phy @0x3eb0000
[0017.001] I> tegrabl_power_on_phy: power on phy @0x3ec0000
[0017.007] I> tegrabl_power_on_phy: power on phy @0x3ed0000
[0017.012] I> tegrabl_power_on_phy: power on phy @0x3ee0000
[0017.017] I> tegrabl_power_on_phy: power on phy @0x3ef0000
[0017.023] I> tegrabl_power_on_phy: power on phy @0x3f00000
[0017.028] I> tegrabl_power_on_phy: power on phy @0x3f10000
[0017.033] I> tegrabl_power_on_phy: power on phy @0x3f20000
[0017.216] I> PCIe controller-5 link is up
[0017.216] I> tegra_pcie_info[5].cfg0_base = 0x3a000000
[0017.217] I> tegra_pcie_info[5].cfg1_base = 0x3a020000
[0017.217] I> tegra_pcie_info[5].atu_dma_base = 0x3a040000
[0017.217] I> tegra_pcie_bus[5].mem = 0x3a200000
[0017.218] I> Scanning busnr: 0 devfn: 0
[0017.218] I> PCIe IDs: 0x1ad010de
[0017.221] I> PCIe RID_CC: 0x60400a1
[0017.225] I> Scanning busnr: 1 devfn: 0
[0017.229] I> PCIe IDs: 0x435211f8
[0017.275] I> PCIe RID_CC: 0xffffffff
[0017.275] I> PCI Config: I/O=0x3a100000, Memory=0x3a200000
I assume you are observing this error with the stock L4T BSP and not with any of the local modifications (apart from debug prints). Please confirm.
I’m suspecting a surprise link-down issue here. In case you are observing the issue with NVMe drives connected, could you please try removing both the drives/one drive at a time and update your observations?
hi dear vidays:
hardware:Jetson xavier p2888
softvare:jetpack 4.6
I have remove both drivers,but the xavier still can’t boot;
and i compared the boot err log and the boot normal log.
Have you fix the problem? Left is ok log, right is err log? We connect by C1, and do not detect the device, how to check it,thanks.
Hi,
I believe PCIe link with switch is not stable, and endpoint’s MMIO access caused boot failure.
Nvidia fixed a bug recently in bootloader PCIe driver, please use latest release build.
If you still see issue, follow below steps to disable PCIe in bootloader and let only Linux kernel enumerate the switch.
Thanks,
Manikanta
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
