From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Date: Fri, 14 Jun 2019 19:53:31 +0200 Subject: [U-Boot] Jetson TX2 hangs during dhcp boot In-Reply-To: References: <20190614170934.GA31159@suse.de> <97f9c274-b471-1e50-305e-b1f826c4c52c@suse.de> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: u-boot@lists.denx.de Am 14.06.19 um 19:26 schrieb Varun Wadekar: >>> ERROR: ARI request timed out: req 89 on CPU 4 >>> ASSERT: plat/nvidia/tegra/soc/t186/drivers/mce/ari.c <127> : retries >>> != 0U > > This time out means that TEGRA_ARI_ROC_FLUSH_CACHE_TRBITS ARI call timed out. Looks like the firmware responsible for handling this ARI call is stuck or overloaded and not servicing any calls. Does this ARI firmware sit in the Arm cores' DRAM? If so, can you share which memory region it needs? Same question for BL31 - is that TZDRAM_BASE? If so, where to find the size? The TF-A docs are not so telling of those layout details. https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/plat/nvidia-tegra.rst U-Boot only reserves any memrsv entries of the FDT, not other memory nodes such as within your sysram at 30000000. Those may need C code in U-Boot to reserve them from usage by UEFI apps such as GRUB and Linux. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm64/boot/dts/nvidia/tegra186.dtsi Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg)