From nobody Fri May 20 17:19:58 2022 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 918981B35DDC for ; Fri, 20 May 2022 17:20:10 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-zteg10021301.me.com (pv50p00im-zteg10021301.me.com [17.58.6.46]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4L4YQ15TZSz4kQB for ; Fri, 20 May 2022 17:20:09 +0000 (UTC) (envelope-from tsoome@me.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1653067203; bh=aLUyr0yczOHpWtV7WpuIdhF2YGlwk/Wx0UlmxBKrn6I=; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:To; b=qet6qCL2puN0mhukUKz31HsSB4UPUUkgk+aKjOqQZLgeMuaKTB9cALi7mmUp7I0+A GgPXDHfRbUMJdzWeyspaFft0Gg+M/NeliApahJsLceevey/d6a20yLMecxuX+yG7wb KHV8EQnAP03ykmwo6TZtlPstgp0ISBH6HG8PD1AP15uWKwsSTtgX+jvCqH44AkT22o jFcQ/myBSDkNHvpEqxTRQSZ4rkRzVic+dv1SgqFY3SW8/IynCnCvJvo4pdgJkU35lJ KBl23UBUGJTKeOubUIn8rlFMvytbjbWyb269vduxDcb0ARucz0RGPun35no7tEdJxH ugp88iSJHoXHw== Received: from smtpclient.apple (pv50p00im-dlb-asmtp-mailmevip.me.com [17.56.9.10]) by pv50p00im-zteg10021301.me.com (Postfix) with ESMTPSA id 8E2075004DB; Fri, 20 May 2022 17:20:01 +0000 (UTC) From: Toomas Soome Message-Id: <1BA529E5-064B-46A8-A412-3D7A66AD6D2F@me.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_0C16D237-30DE-4FDC-BEB8-60E2C5F0ED0C" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\)) Subject: Re: loader_4th.efi broke? Date: Fri, 20 May 2022 20:19:58 +0300 In-Reply-To: Cc: current@freebsd.org To: "Bjoern A. Zeeb" References: <71D61E79-B3A5-49FA-9B9E-26E124A5B4EF@me.com> X-Mailer: Apple Mail (2.3696.80.82.1.1) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.486,18.0.874 definitions=2022-05-20_05:2022-05-20,2022-05-20 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2009150000 definitions=main-2205200112 X-Rspamd-Queue-Id: 4L4YQ15TZSz4kQB X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=me.com header.s=1a1hai header.b=qet6qCL2; dmarc=pass (policy=quarantine) header.from=me.com; spf=pass (mx1.freebsd.org: domain of tsoome@me.com designates 17.58.6.46 as permitted sender) smtp.mailfrom=tsoome@me.com X-Spamd-Result: default: False [-2.14 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; NEURAL_HAM_SHORT(-0.54)[-0.545]; RCVD_IN_DNSWL_LOW(-0.10)[17.58.6.46:from]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[me.com]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[me.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FREEFALL_USER(0.00)[tsoome]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[17.56.9.10:received]; MLMMJ_DEST(0.00)[current]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_0C16D237-30DE-4FDC-BEB8-60E2C5F0ED0C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 20. May 2022, at 20:11, Bjoern A. Zeeb = wrote: >=20 > On Fri, 20 May 2022, Toomas Soome wrote: >=20 >>> On 20. May 2022, at 20:00, Bjoern A. Zeeb = wrote: >>>=20 >>> Hi, >>>=20 >>> something between >>> 255692.f70de61e567df59bceb2d18c8bc1b54943a7466b and >>> 255723.b3fa36efe797445cb0b4fd26d79226836db2a2b3 >>> made loader_4th.efi go all >>> "failed to allocate staging area: 9" >>>=20 >>> I am netbooting booting, no ZFS involved. >>> One other data point: the base system compile may have changed in = that time. >>>=20 >>> I haven't dug into yet. Is anyone else seeing this? >>>=20 >>=20 >> staging area will be allocated very early, so for some reason either = the memory map is fragmented or there is just too low memory. >>=20 >> 9 is EFI_OUT_OF_RESOURCES. >=20 > The UEFI hasn't changed; 64GB of memory haven't changed. Power > cycling didn't make a difference. Going back to the old one > immediately worked again. I saw no changes in stand/ relevant. >=20 > Is there a way to debug this or should we simply "stop" if this fails > rather than endlessly fill the console with it? >=20 um, ok 64GB should be plenty;) of course, if the firmware is squashing = low memory map to small chunks, then there is problem (we are asking to = use low 4GB because of buggy firmwares=E2=80=A6), but you can try = loader_lua.efi. The other cause could be grown kernel modules - we try = to allocate 64MB staging area first, if it is not enough, then we try to = get larger chunk=E2=80=A6. Of course, screen spamming is bug, that should not happen.=20 rgds, toomas= --Apple-Mail=_0C16D237-30DE-4FDC-BEB8-60E2C5F0ED0C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On 20. May 2022, at 20:11, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote:

On Fri, 20 May 2022, Toomas Soome wrote:

On 20. May 2022, at = 20:00, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote:
Hi,

something between
= 255692.f70de61e567df59bceb2d18c8bc1b54943a7466b and
= 255723.b3fa36efe797445cb0b4fd26d79226836db2a2b3
made = loader_4th.efi go all
"failed to allocate staging area: = 9"

I am netbooting booting, no ZFS = involved.
One other data point: the base system compile = may have changed in that time.

I haven't = dug into yet. Is anyone else seeing this?


staging area will be allocated = very early, so for some reason either the memory map is fragmented or = there is just too low memory.

9 is = EFI_OUT_OF_RESOURCES.

The UEFI hasn't changed; 64GB of memory haven't changed. = Power
cycling = didn't make a difference. Going back to the old one
immediately = worked again. I saw no changes in stand/ relevant.

Is there a = way to debug this or should we simply "stop" if this fails
rather than = endlessly fill the console with it?


um, = ok 64GB should be plenty;) of course, if the firmware is squashing low = memory map to small chunks, then there is problem (we are asking to use = low 4GB because of buggy firmwares=E2=80=A6), but you can try = loader_lua.efi. The other cause could be grown kernel modules - we try = to allocate 64MB staging area first, if it is not enough, then we try to = get larger chunk=E2=80=A6.

Of = course, screen spamming is bug, that should not = happen. 

rgds,
toomas
= --Apple-Mail=_0C16D237-30DE-4FDC-BEB8-60E2C5F0ED0C--