From nobody Thu Jul 21 14:55:40 2022 X-Original-To: freebsd-arm@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 4LpbGD4CFxz4WpYB; Thu, 21 Jul 2022 14:55:16 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LpbGD3LSPz47PR; Thu, 21 Jul 2022 14:55:16 +0000 (UTC) (envelope-from kevans@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1658415316; 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: in-reply-to:in-reply-to:references:references; bh=vKIRwXH+XsX4Mm18O/A4JgKg8cWA3KTTJbw+EtwS6lg=; b=lUX8SGW3ypCdAiKm6FRfOQ0WVhG+n0+4OMsCJu+ySyn1yd7fdJ90xk/S13RU7Ve2cj+t2H x4xT/DL61aICpRH8pdi50232U0h4uIyxJn44bouIO2d+IC5Dw7KfDKQJ45+Y4DbkB4Cc/Z 8ETdU+G8lCMgcQ75dxl2NlUWlfpbyXActTtlnoyQ0HZjjOps6TMknPV+Jr5Jrv5Cc2+OjU jOGTOMzv+EJLBO2qNfXwDquZnv8A03V3iIR/B+RwL1KD8oQAkInEIZs9LJzwDhDrtIXLw6 kDNJQvm7IGJZTSyPCzqsdskZu/Ur6c0bloq9bIGAemwHaGpO06jHQ7vtjDgEwg== Received: from mail-ej1-f49.google.com (mail-ej1-f49.google.com [209.85.218.49]) (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 "GTS CA 1D4" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 4LpbGD2K1WzWbL; Thu, 21 Jul 2022 14:55:16 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-ej1-f49.google.com with SMTP id j22so3638748ejs.2; Thu, 21 Jul 2022 07:55:16 -0700 (PDT) X-Gm-Message-State: AJIora98WTikC+BHbO1PWu2gZdu9g8vKEj/gP4+4QDZ6ED9l3mOiOb9G WnNfvtvqYm12nPi9jt8ot1Uz6EbjKNyl7BKbedw= X-Google-Smtp-Source: AGRyM1vVdehzEhUfSmXn6KbnvM7QYo4vPIa4tllRX0pOlgMtVKXGIZ3Vxk72CMhm5wnORIWHd0ICbZafH2rXv9ug39I= X-Received: by 2002:a17:907:2c74:b0:72b:5ba7:d96f with SMTP id ib20-20020a1709072c7400b0072b5ba7d96fmr41772076ejc.33.1658415315304; Thu, 21 Jul 2022 07:55:15 -0700 (PDT) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: <16906DFD-286B-4D59-9438-CA9CD9026C55@yahoo.com> <202207171708.26HH81bA062303@gndrsh.dnsmgr.net> <20220719204245.GL30607@FreeBSD.org> In-Reply-To: From: Kyle Evans Date: Thu, 21 Jul 2022 07:55:40 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: git: 1dfcff294e44 - main - release: increase IMAGE_SIZE for arm, arm64, riscv [odd alignment for SBC images] To: Mark Millard Cc: Warner Losh , Glen Barber , Ed Maste , "Rodney W. Grimes" , dev-commits-src-main@freebsd.org, "Dr. Rolf Jansen" , freebsd-arm Content-Type: text/plain; charset="UTF-8" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1658415316; 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: in-reply-to:in-reply-to:references:references; bh=vKIRwXH+XsX4Mm18O/A4JgKg8cWA3KTTJbw+EtwS6lg=; b=X3x6xb1YCwiSqqQQNKVKjlywkx0N/driblgHszKyBHrBBMWGf54VejcJWEvgPlVBaa2901 72wVUsznjuQshBGkghHAKZaf/7T38QFaKEaEyKIgcGbX8Pog4HcqJrSiCXCb2qnvp6j9xt b1qMby/P5Pk8AV7Ci88z2LWb7SpOTyVtL4JhUDDVZm7VLnGdAKQkD+j7srAG9AHDBrUUro hBrZoTJ+PSHucCtMYw7VyRqrZtL6Lv5P5xD4dvjtSkxn7iSh8SoEL7fzRF0b4qI4QunX7h 2AaSrT5oJgRM9l7ykV9KqnV+kNxSil23EiWhEC5Tfimpzc2gGSXMS2djUQqPzA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1658415316; a=rsa-sha256; cv=none; b=eTxVHEUYCn42/4QWy3u2FQz7+2OhRVdZTvqwqxlY2bLdKhBHpt3sT8lmApXViAa4p7ZaJK 6H1By0QPK0SaeRZZYeNwBK7hE6Qn8Xdi39CdpIlcFC/H2O3b7/8jOkq+58QGqhJuibZbjP uUByNX99WajVpquQatQoj1K5AyP6xq8OYUvPI8mK44oOe8JAhnqJlSl6Y2eHX5MsqeW4vZ pCRGqXCjIn19WbyREQd202mm+96ctHtRjGD1wtMEO8t8lk3T+Qm/98GwyRcVi9OLT8ZUY+ dGJB0sM+lhXFB13FaIj3rsX5k2gHajV4ubebjEFvGo3RGsKgKEOqPn7HDu1RnQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Wed, Jul 20, 2022 at 10:08 AM Mark Millard wrote: > > On 2022-Jul-19, at 15:45, Warner Losh wrote: > > > On Tue, Jul 19, 2022, 2:42 PM Glen Barber wrote: > >>> . . . > >> > >> My concern with this is kern.geom.part.mbr.enforce_chs is always '1' on > >> the builders, which effectively means all arm builds will fail every > >> time. I think we need to get to the actual root of the problem here, > >> versus applying band-aids to a shark bite. > > > > I think this is the actual problem. While such pedantry can be useful for ancient picky BIOSes, these days only the LBA fields of the MBR are used. And the fake BIOS geometry is crazy weird. We can likely tweak it to be more friendly. > > > > Why is it == 1 on the builder? If people want things aligned gpart has an option for years iirc to do that. And we want that off for the builds. > > Would it seem appropriate to use a week (this week?) to do all > the snapshot builds with the builders all set to have > kern.geom.part.mbr.enforce_chs=0 and see what breaks, if anything? > (Sort of a snapshot exp run.) > https://svnweb.freebsd.org/base?view=revision&revision=332731 says: Note: In addition to this merge, kern.geom.part.mbr.enforce_chs has been enabled on the build machine to mitigate against the issue in the PR referenced. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226536 ("glabel/partition mixup on sdcard images")