Date: Fri, 12 Mar 2021 17:25:59 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 254238] sdhci_bcm0-slot0: Controller timeout with main-n245392-8423f5d4c12 Message-ID: <bug-254238-227-bp6W2DRxDI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254238-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254238 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #1 from Mark Millard <marklmi26-fbsd@yahoo.com> --- Note: As I understand things, this submittal is based in part on using: A) Possibly based on old RPi* firmware but which vintage is unknown. B) An old u-boot (2020.07, not 2020.10). C) An old loader.efi (as bootaa64.efi). For (A) it would help if the output of # strings start4.efi | grep VC_BUILD_ID_ was reported so that the context was better known. (Not seen so far on the lists either.) Notes abourt (B) and (C) are in the referenced list material. I have recommended that trying with all of this updated and reporting on the results so that the reporting context and investigation context would be matched without trying to revet to the odd mix of history now apparently involved. I'll note that the content from a few commits earlier: FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20210311-15565e0a217-257277.img.xz does not show this problem on teh RPi4B 8 GiByte that I tried (but you need to avoid USB storage media becuase of another issue that would cause a debug-kernel panic). -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254238-227-bp6W2DRxDI>