From nobody Mon Sep 09 08:28:25 2024 X-Original-To: freebsd-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 4X2Kk965qKz5W8R9 for ; Mon, 09 Sep 2024 08:29:05 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [IPv6:2001:1640:5::8:31]) (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 4X2Kk84l25z4bL8; Mon, 9 Sep 2024 08:29:04 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=tOiUQs7S; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@walstatt-de.de designates 2001:1640:5::8:31 as permitted sender) smtp.mailfrom=freebsd@walstatt-de.de Received: from hub2.goneo.de (hub2.goneo.de [IPv6:2001:1640:5::8:53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id 10206240535; Mon, 9 Sep 2024 10:28:55 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 49D6424030E; Mon, 9 Sep 2024 10:28:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1725870534; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9ddgnoVJsoAoadaLjMIX8EQPg292I+tmhSIhXgPX9fc=; b=tOiUQs7Sw7gogPdtLubwRPNxf7levqYw/9CwHRcrmoVNQaSQjsIZXyBXPctiEMe1gyex65 nUB2xHGuVAf3K55DCazOPFXaO5iSl/4NtBevJpHnoYv7YddZGV1fBtZoT7ZC64ddc4GbDb 8w4ZI1rvKpe+Fo1gHfs9nVtNRUEAyTTd6bwyZQn6HTdOdc75fOH6l7XNjHIfmdwPGJ1cxf 9ScY6+/ctpMfFlDneJXRIzqArJYA1CwBST2IZvHIriW+nUQ7rTi6gQjBdT43XcZiBG8DnB CPXB6fpPAf5gsDpFXU2hm4YgxpVPufbikUINhs5mJ/Z2PR69thV5nPmCyHzhAw== Received: from thor.intern.walstatt.dynvpn.de (dynamic-078-054-167-035.78.54.pool.telefonica.de [78.54.167.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id 4D322240621; Mon, 9 Sep 2024 10:28:53 +0200 (CEST) Date: Mon, 9 Sep 2024 10:28:25 +0200 From: FreeBSD User To: Warner Losh Cc: Gordon Bergling , FreeBSD Current Subject: Re: buildworld error Message-ID: <20240909102852.582f1362@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: Organization: walstatt-de.de 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-UID: 4b762c X-Rspamd-UID: e2701a X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; R_SPF_ALLOW(-0.20)[+ip6:2001:1640:5::8:0/112]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; MIME_GOOD(-0.10)[text/plain]; HAS_ORG_HEADER(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[walstatt-de.de:+] X-Rspamd-Queue-Id: 4X2Kk84l25z4bL8 Am Sat, 24 Aug 2024 15:21:16 -0600 Warner Losh schrieb: > On Sat, Aug 24, 2024 at 1:39=E2=80=AFPM Gordon Bergling = wrote: >=20 > > Hi Warner, > > > > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote: =20 > > > On Sat, Aug 24, 2024, 1:14=E2=80=AFPM Gordon Bergling wrote: =20 > > > > I got the following buildworld error a recent -CURRENT > > > > =20 > > > > =3D=3D=3D> stand/i386/pxeldr (all) =20 > > > > `kldstat.o' is up to date. > > > > -14152 bytes available > > > > > > > > The same happens on stable/14: > > > > =20 > > > > =3D=3D=3D> stand/i386/pxeldr (all) =20 > > > > -22344 bytes available =20 > > > > =3D=3D=3D> share/misc (all) =20 > > > > --- loader --- > > > > *** [loader] Error code 1 > > > > > > > > make[5]: stopped in /storage/freebsd/src/stable/14/stand/i386/pxeldr > > > > 1 error > > > > > > > > src.conf looks like the following: > > > > WITH_BEARSSL=3D1 > > > > WITH_RETPOLINE=3D1 > > > > WITHOUT_CLEAN=3D1 > > > > > > > > I remove the whole obj directories and tried several full builds, b= ut =20 > > the =20 > > > > error persists for a while. > > > > > > > > Has any one a clue how to solve this? =20 > > > > > > Either disable pxe, raise the pxe limit (though it may not work), or = =20 > > select =20 > > > the 4th loader for pxeboot. > > > > > > The loader is too big on BIOS to enable all the options. =20 > > > > I looked at src.conf(5), but didn't found a switch to disable pxe. What= I > > am > > wondering about is that no one is facing the problem, since this it is a > > pretty clean build without and special modifications, despite the ones > > mention > > above in the src.conf. > > > > Did you have a hint on how to disable pxe? > > =20 >=20 > I was sure that I'd documented everything, but it seems not: >=20 > =3Dt > PXEBOOT_DEFAULT_INTERP=3D4th > PXEBOOTSIZE?=3D525000 >=20 > I'll look to make sure I don't have a commit stuck in a branch somewhere.= ... >=20 > Warner After the introduction of WITHOUT_LOADER_PXEBOOT and setting this knob to true in /etc/src.conf has mitigated for me the pro= blem reported above (it appears reproduceable when setting WITH_BEARSSL for me). But the proble= m mentione reappeared recently (a week or two on CURRENT, building on testboxes almost= daily ...) again. Just for the record =20 Kind regards, oh --=20 O. Hartmann