From owner-freebsd-arm@freebsd.org Wed Feb 26 01:57:12 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C7661247CBA for ; Wed, 26 Feb 2020 01:57:12 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48RzSm0nFBz4Xqm for ; Wed, 26 Feb 2020 01:57:12 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qv1-f48.google.com (mail-qv1-f48.google.com [209.85.219.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id BAC724833 for ; Wed, 26 Feb 2020 01:57:11 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qv1-f48.google.com with SMTP id y8so619976qvk.6 for ; Tue, 25 Feb 2020 17:57:11 -0800 (PST) X-Gm-Message-State: APjAAAXtDbpqhc1QCJ3Ryr7tdZ27oQjxRjEaTq9A/nzaDYr28OAFEDlr lmYZcFsaUlPuvP2Y2J65hkHWcLHIhcbrNvGeu/A= X-Google-Smtp-Source: APXvYqzjv41pCuOVHB5/y3DTVYZrhesitA1RKKT0vl8kTIoG+ZBCAG0Mjf9mGUZJGOprz/7/hsJn2TQ17qNFKnGM0jo= X-Received: by 2002:a05:6214:b23:: with SMTP id w3mr2250106qvj.181.1582682231304; Tue, 25 Feb 2020 17:57:11 -0800 (PST) MIME-Version: 1.0 References: <20200225175446.GA77976@www.zefox.net> <11951E01-EC13-4FBB-938A-AEB5700C4281@yahoo.com> In-Reply-To: <11951E01-EC13-4FBB-938A-AEB5700C4281@yahoo.com> From: Kyle Evans Date: Tue, 25 Feb 2020 19:57:00 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Showstoppers for RPI3 To: Mark Millard Cc: bob prohaska , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 01:57:12 -0000 On Tue, Feb 25, 2020 at 5:05 PM Mark Millard via freebsd-arm wrote: > > On 2020-Feb-25, at 09:54, bob prohaska wrote: > > > There seem to be a handful of problems for -current on the RPI3 at > > the moment. Those I've noticed include not getting multicore operation, > > cpu_reset failing and OOMA kills with vm.pfault_oom_attempts="-1" set > > in /boot/loader.conf. > > 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. > However, for aarch64 RPi*'s, this is after -r356767 where the > kernel needs to be told to avoid touching all the armstub8-gic.bin > or armstub8.bin RAM. (Previously worked only by accident, i.e., > despite not being told to avoid all that RAM.) > > It is messy to make judgments about aarch64 RPi*'s on or after > -r356767 (until/unless all the armstub8*.bin is being reported to > the kernel as RAM to avoid): too much ends up messed up by the > kernel replacing part of armstub8*.bin's RAM content. > > The problem -r357253 fixed was for all platforms, not just aarch64, > much less being aarch64 RPi* specific. As far as I've seen, the > platforms that do not have problems at -r356767 are no longer > getting reports of vm.pfault_oom_attempts="-1" problems. > > 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. Thanks, Kyle Evans