From nobody Sun Aug 25 22:16:31 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 4WsSp40yWlz5TfPD for ; Sun, 25 Aug 2024 22:16:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WsSp36Fd5z4XR9 for ; Sun, 25 Aug 2024 22:16:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-76cb5b6b3e4so2274786a12.1 for ; Sun, 25 Aug 2024 15:16:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1724624202; x=1725229002; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hwCqgq2a2XXpYTMj4uwBGJlgYkGXDhOxbO81LBzAczo=; b=mN2oYf+fgzyUX29EjbOtLiaUNi6vMBqBx5QmLOSnsVcf+fm+S/s88KwS6tM0C54pWU gjZyM1/rXkAzObzxQ3cpA0uChbg9jVyHmZRcXBe7IVwHoKvJzaxDnp46KIMZEGJs1zFF 7x29OvZkgUZ3RiOBGtQjjIunjMSE/RS/kuzwy91t1UjNdrW/eTGl+n9nKJXKzM2bDJh0 nVfImpHTtjWcpvKRtndLsJexe9AmjOyzKggPSWIgWGzaJXqrxgWo37wnJVXpe4Sa+Ndp KqjNdvohK+V+66oCFeMv0Cd3MfsVG8KzqhBBU2cIu5Wo1e0Gj81a2zKiV1UEKIRhsyj6 lOiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724624202; x=1725229002; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hwCqgq2a2XXpYTMj4uwBGJlgYkGXDhOxbO81LBzAczo=; b=EKtu0FK1F71HjKgoEE73JIx7pw5Ly8I3If9HLPrIddLLw5NbCYm79W+50tVXuQRLsd pqVJq6EhbV3jSvGNtn6iJkI2Wan89PvqCx/i1Zp9erK7IdXS1GnMcLG8tPEXnoaeM5dL WdPZufdr0Cf0UAL1YIHXJnevuoHa87OcMRFNxCUEM873zgkriqB98EUpKr4pixhUWyul 9JNRGjaaIGIVfLPiFEduHp4lk1e4mAHxWWK/SnuxgabU6c/qgEJD880/a1aK+OclTFKS 0UfSoyiKnRANNzBOVQjZ0nocPjomuWGcK0dRzpL7EUul7vBpmEq9q67P/ykbUDXc3uLo eb8w== X-Gm-Message-State: AOJu0YxjhSu7NofSIbt4YocLHDn/2ZD/hiRhJ4hfmZdgJoTtno/Arm8p Gj1jtR/fDO+cCQApuKGGHHNSh6aJHJHn16MMs0jDpUeB9DhlPUvyO4/9SgQqauHx4sGlEobSDhR HGwYLDx3CovGRtrpkNemnWl1Lu1wfQdob+r8gCvAmRLap82bl X-Google-Smtp-Source: AGHT+IHGuOwFZXbB76gLvfLwM8jnC6KBWFEt7nkfYH5pLT6SfKDR5UW1KfDPp/CeeaWT2sZXqHEGlHlM6AkZ9ohopj8= X-Received: by 2002:a17:90b:2e83:b0:2d3:c05c:c51 with SMTP id 98e67ed59e1d1-2d64671d976mr7402646a91.0.1724624202172; Sun, 25 Aug 2024 15:16:42 -0700 (PDT) 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 References: In-Reply-To: From: Warner Losh Date: Sun, 25 Aug 2024 16:16:31 -0600 Message-ID: Subject: Re: buildworld error To: Gordon Bergling Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000f128410620895cae" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WsSp36Fd5z4XR9 --000000000000f128410620895cae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Aug 25, 2024 at 4:23=E2=80=AFAM Gordon Bergling w= rote: > Hi Warner, > > On Sat, Aug 24, 2024 at 03:21:16PM -0600, Warner Losh wrote: > > On Sat, Aug 24, 2024 at 1:39=E2=80=AFPM Gordon Bergling wrote: > > > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote: > > > > On Sat, Aug 24, 2024, 1:14=E2=80=AFPM Gordon Bergling > wrote: > > > > > I got the following buildworld error a recent -CURRENT > > > > > > > > > > =3D=3D=3D> stand/i386/pxeldr (all) > > > > > `kldstat.o' is up to date. > > > > > -14152 bytes available > > > > > > > > > > The same happens on stable/14: > > > > > > > > > > =3D=3D=3D> stand/i386/pxeldr (all) > > > > > -22344 bytes available > > > > > =3D=3D=3D> share/misc (all) > > > > > --- 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, > but > > > the > > > > > error persists for a while. > > > > > > > > > > Has any one a clue how to solve this? > > > > > > > > Either disable pxe, raise the pxe limit (though it may not work), o= r > > > select > > > > the 4th loader for pxeboot. > > > > > > > > The loader is too big on BIOS to enable all the options. > > > > > > 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 i= s > a > > > pretty clean build without and special modifications, despite the one= s > > > mention > > > above in the src.conf. > > > > > > Did you have a hint on how to disable pxe? > > > > > > > I was sure that I'd documented everything, but it seems not: > > > > WITHOUT_LOADER_PXEBOOT=3Dt > > PXEBOOT_DEFAULT_INTERP=3D4th > > PXEBOOTSIZE?=3D525000 > > > > I'll look to make sure I don't have a commit stuck in a branch > somewhere.... > > with this values in the src.conf(5) the build finally finished. But I > wonder > why I am the only person, who hits that problem since it is a very plain > -CURRENT build on a Hyper-V instance. > > Should these values be default values? > You've enabled some big ticket items. It's not at all clear what the defaul= t should be when people grow the loader too big. These options exist because PXEBOOT larger than about 500k is know to be flakey, though there's no universally known good upper limit since it depends a lot on the BIOS, what it does, etc. So upping that limit is off the table (though one can if one tests it and finds that works). Some other people don't use PXE at all, so for them, disabling it makes the most sense. Still others can't up the PXE limit high enough, and for them, using the 4th loader is a good path forward. The other option is for someone to go through /boot/loader and shaving some additional space. I've found all the easy, low-hanging fruit, plus turning off all the esoteric filesystems got us down to almost fitting. Warner --000000000000f128410620895cae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Aug 25, 2024 at 4:23=E2=80=AF= AM Gordon Bergling <gbe@freebsd.org> wrote:
Hi= Warner,

On Sat, Aug 24, 2024 at 03:21:16PM -0600, Warner Losh wrote:
> On Sat, Aug 24, 2024 at 1:39=E2=80=AFPM Gordon Bergling <gbe@freebsd.org> wrote: > > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote:
> > > On Sat, Aug 24, 2024, 1:14=E2=80=AFPM Gordon Bergling <gbe@freebsd.org> = wrote:
> > > > I got the following buildworld error a recent -CURRENT<= br> > > > >
> > > > =3D=3D=3D> stand/i386/pxeldr (all)
> > > > `kldstat.o' is up to date.
> > > > -14152 bytes available
> > > >
> > > > The same happens on stable/14:
> > > >
> > > > =3D=3D=3D> stand/i386/pxeldr (all)
> > > > -22344 bytes available
> > > > =3D=3D=3D> share/misc (all)
> > > > --- loader ---
> > > > *** [loader] Error code 1
> > > >
> > > > make[5]: stopped in /storage/freebsd/src/stable/14/stan= d/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 fu= ll builds, but
> > the
> > > > error persists for a while.
> > > >
> > > > Has any one a clue how to solve this?
> > >
> > > Either disable pxe, raise the pxe limit (though it may not w= ork), or
> > select
> > > the 4th loader for pxeboot.
> > >
> > > The loader is too big on BIOS to enable all the options.
> >
> > 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?
> >
>
> I was sure that I'd documented everything, but it seems not:
>
> WITHOUT_LOADER_PXEBOOT=3Dt
> PXEBOOT_DEFAULT_INTERP=3D4th
> PXEBOOTSIZE?=3D525000
>
> I'll look to make sure I don't have a commit stuck in a branch= somewhere....

with this values in the src.conf(5) the build finally finished. But I wonde= r
why I am the only person, who hits that problem since it is a very plain -CURRENT build on a Hyper-V instance.

Should these values be default values?

= You've enabled some big ticket items. It's not at all clear what th= e default
should be when people grow the loader too big. These op= tions exist because
PXEBOOT=C2=A0larger than about 500k is know t= o be flakey, though there's no
universally known good upper l= imit since it depends a lot on the BIOS, what
it does, etc. So up= ping that limit is off the table (though one can if one tests
it = and finds that works). Some other people don't use PXE at all, so for
them, disabling it makes the most sense. Still others can't up= the PXE
limit high enough, and for them, using the 4th loader is= a good path
forward.

The other option i= s for someone to go through /boot/loader and shaving
some additio= nal space. I've found all the easy, low-hanging fruit, plus
t= urning off all the esoteric filesystems got us down to almost fitting.

Warner
--000000000000f128410620895cae--