Date: Tue, 25 Feb 2020 21:20:45 -0800 From: bob prohaska <fbsd@www.zefox.net> To: Kyle Evans <kevans@freebsd.org> Cc: Mark Millard <marklmi@yahoo.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, bob prohaska <fbsd@www.zefox.net> Subject: Re: Showstoppers for RPI3 Message-ID: <20200226052045.GA79939@www.zefox.net> In-Reply-To: <CACNAnaEiv5NZZz%2BxfETkhSZ-zbjZ3Ya6z7pyteheP4zj3EK1Gg@mail.gmail.com> References: <20200225175446.GA77976@www.zefox.net> <11951E01-EC13-4FBB-938A-AEB5700C4281@yahoo.com> <CACNAnaEiv5NZZz%2BxfETkhSZ-zbjZ3Ya6z7pyteheP4zj3EK1Gg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Tue, Feb 25, 2020 at 07:57:00PM -0600, Kyle Evans wrote: > On Tue, Feb 25, 2020 at 5:05 PM Mark Millard via freebsd-arm > <freebsd-arm@freebsd.org> wrote: > > > > > > If you are seeing vm.pfault_oom_attempts="-1" fail to work on or > > after head -r357253 (from 2020-Jan-29) that is likely new news. Haven't checked yet, but it sounds like post-r357253 should be ok. Alas, the frying pan is cooling but the fire is still hot: > > The armstub8-gic.bin/armstub8.bin RAM not being reported to the > > kernel as RAM to avoid touching is a known problem for aarch64 > > RPi*'s. But, as far as I know, no one has indicated that they are > > working on getting such RPi*'s to well report armstub8*.bin RAM > > to the kernel --or that they are planning to do so. > > > > I've forwarded your patch on to some relevant U-Boot folk to try and > get some feedback from them, since they likely understand the process > better -- I would suspect reserving the second page in U-Boot as well > is the proper solution. Sounds like that fix is not yet on the horizon. Would explicit bug reports be helpful? Thanks! bob prohaskahome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200226052045.GA79939>