From owner-freebsd-current@freebsd.org Thu Feb 25 00:50:16 2021 Return-Path: Delivered-To: freebsd-current@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 9360F550142 for ; Thu, 25 Feb 2021 00:50:16 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (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 (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DmDj35cpfz4tDY; Thu, 25 Feb 2021 00:50:15 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 11P0o843026139 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 24 Feb 2021 16:50:08 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 11P0o8jE026138; Wed, 24 Feb 2021 16:50:08 -0800 (PST) (envelope-from sgk) Date: Wed, 24 Feb 2021 16:50:08 -0800 From: Steve Kargl To: Glen Barber Cc: freebsd-current@freebsd.org Subject: Re: any images for freebsd-current? Message-ID: <20210225005008.GA26120@troutmask.apl.washington.edu> References: <20210206195927.GA45627@troutmask.apl.washington.edu> <20210208030310.GY77557@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210208030310.GY77557@FreeBSD.org> X-Rspamd-Queue-Id: 4DmDj35cpfz4tDY X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none); spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-2.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RBL_DBL_DONT_QUERY_IPS(0.00)[128.95.76.21:from]; SPAMHAUS_ZRD(0.00)[128.95.76.21:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2021 00:50:16 -0000 On Mon, Feb 08, 2021 at 03:03:10AM +0000, Glen Barber wrote: > On Sat, Feb 06, 2021 at 11:59:27AM -0800, Steve Kargl wrote: > > Any one aware of where images from freebsd-current? > > freebsd.org appears to offer no images. > > > > Some juggling needs to be done to the release build machines, which > I hope to have done this week before the weekly snapshots. > FYI. I downloaded the 20210218 memstick image for FreeBSD-14 amd64, and re-installed FreeBSD on the problematic laptop. So far, the laptop has been rock solid. Rebuilt 547 ports from source. I suspect that there is vm or ufs or clang/llvm bug(s) that make running FreeBSD i386 on this laptop a nightmare. From early Jan 2021 until this passed weekend, I was having daily (sometime multiple) panics. Panics pointed at issues with vm (but required drm-kmod to be loaded) and massively scrambled my SU ufs filesystems. I also know that clang miscompiles libm, so by extension it may be miscompiling others parts of FreeBSD (leading to the panics). YMMV. -- Steve