Date: Sun, 15 Mar 2020 18:54:00 -0700 From: Mark Millard <marklmi@yahoo.com> To: Kyle Evans <kevans@freebsd.org> Cc: bob prohaska <fbsd@www.zefox.net>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: Panic on Rpi3 at r358976 Message-ID: <90DE70B3-F3A5-4EFE-832C-7C412744D974@yahoo.com> In-Reply-To: <CACNAnaGuXH%2B3sB7qexz9-eC87=WmZrhwvuyb%2BkEMVdXPxB6LHQ@mail.gmail.com> References: <20200315041203.GA55605@www.zefox.net> <CACNAnaGuXH%2B3sB7qexz9-eC87=WmZrhwvuyb%2BkEMVdXPxB6LHQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On 2020-Mar-15, at 17:33, Kyle Evans <kevans at freebsd.org> wrote:
> On Sat, Mar 14, 2020 at 11:12 PM bob prohaska <fbsd@www.zefox.net> wrote:
>>
>> Tried to boot a kernel built from r358976 on a Pi3 and got a panic:
>>
>> [... snip ...]
>
> Hi,
>
> I've got a patch against sysutils/u-boot-rpi{3,4} based on what I've
> submitted upstream that I'm test-building again and will soon be
> submitting to Phabricator; please give it a shot and confirm if it
> makes life happier or not:
> https://people.freebsd.org/~kevans/rpi-psci.diff
I grep'd in the area that holds where I did the
investigative patch that enabled the RPi4 to boot
and such without the armstub8-gic.bin memory being
slamed. (I've not done any clean-out of the materials
in that area.)
The result is not suggestive of CONFIG_RPI_EFI_NR_SPIN_PAGES
making a difference:
# grep -r CONFIG_RPI_EFI_NR_SPIN_PAGES /wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/u-boot-2019.10/
#
(I.e., nothing found.) The same was true for grep'ing
in the wider area:
/wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/
By contrast, for CONFIG_ENV_FAT_DEVICE_AND_PART :
# grep -r CONFIG_ENV_FAT_DEVICE_AND_PART /wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/u-boot-2019.10/
/wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/u-boot-2019.10/configs/am65x_evm_r5_defconfig:CONFIG_ENV_FAT_DEVICE_AND_PART="1:1"
. . . (I'll not show the other 33 lines of matches) . . .
I will show .h and .c source lines using
CONFIG_ENV_FAT_DEVICE_AND_PART :
wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/u-boot-2019.10/env/fat.c: CONFIG_ENV_FAT_DEVICE_AND_PART,
/wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/u-boot-2019.10/env/fat.c: CONFIG_ENV_FAT_DEVICE_AND_PART,
/wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/u-boot-2019.10/include/configs/sama5d27_som1_ek.h:#define CONFIG_BOOTCOMMAND "fatload mmc " CONFIG_ENV_FAT_DEVICE_AND_PART " 0x21000000 at91-sama5d27_som1_ek.dtb; " \
/wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/u-boot-2019.10/include/configs/sama5d27_som1_ek.h: "fatload mmc " CONFIG_ENV_FAT_DEVICE_AND_PART " 0x22000000 zImage; " \
/wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/u-boot-2019.10/include/configs/sama5d2_xplained.h:#define CONFIG_BOOTCOMMAND "fatload mmc " CONFIG_ENV_FAT_DEVICE_AND_PART " 0x21000000 at91-sama5d2_xplained.dtb; " \
/wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/u-boot-2019.10/include/configs/sama5d2_xplained.h: "fatload mmc " CONFIG_ENV_FAT_DEVICE_AND_PART " 0x22000000 zImage; " \
A file that lists the potential CONFG_* names seems to be:
/wrkdirs/usr/ports/sysutils/u-boot-rpi4/work/u-boot-2019.10/u-boot.cfg.configs
and it does not have CONFIG_RPI_EFI_NR_SPIN_PAGES .
I've no evidence that 2019.10 would make any use of
a CONFIG_RPI_EFI_NR_SPIN_PAGES definition.
Still, I can try it later if desired.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90DE70B3-F3A5-4EFE-832C-7C412744D974>