From owner-freebsd-questions@freebsd.org Sun Jan 6 06:13:01 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45850143894A for ; Sun, 6 Jan 2019 06:13:01 +0000 (UTC) (envelope-from freebsd@pki2.com) Received: from btw.pki2.com (unknown [IPv6:2603:3023:16d:1001::c0a8:1701]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0864A8B396 for ; Sun, 6 Jan 2019 06:12:58 +0000 (UTC) (envelope-from freebsd@pki2.com) Received: from localhost (localhost [127.0.0.1]) by btw.pki2.com (8.15.2/8.15.2) with ESMTP id x066Co7S095011; Sat, 5 Jan 2019 22:12:50 -0800 (PST) (envelope-from freebsd@pki2.com) Message-ID: <27e76d8f1a18cc2ef9e9be04fdc86dd701e71ec0.camel@pki2.com> Subject: Re: 12-RELEASE + Storage woes From: Dennis Glatting To: Bob Healey , freebsd-questions@FreeBSD.ORG Date: Sat, 05 Jan 2019 22:12:49 -0800 In-Reply-To: <5e14feab-efc2-863d-98d0-fe9e01c5fd59@rpi.edu> References: <5e14feab-efc2-863d-98d0-fe9e01c5fd59@rpi.edu> X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner-ID: x066Co7S095011 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: freebsd@pki2.com X-Spam-Status: No X-Rspamd-Queue-Id: 0864A8B396 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dmarc=pass (policy=none) header.from=pki2.com; spf=pass (mx1.freebsd.org: domain of freebsd@pki2.com designates 2603:3023:16d:1001::c0a8:1701 as permitted sender) smtp.mailfrom=freebsd@pki2.com X-Spamd-Result: default: False [4.02 / 15.00]; ARC_NA(0.00)[]; RDNS_NONE(1.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; NEURAL_SPAM_MEDIUM(0.19)[0.187,0]; NEURAL_SPAM_SHORT(0.62)[0.617,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[btw.pki2.com]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[pki2.com,none]; NEURAL_SPAM_LONG(0.19)[0.194,0]; IP_SCORE(-0.17)[asn: 7922(-0.75), country: US(-0.08)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:7922, ipnet:2603:3000::/24, country:US]; HFILTER_HOSTNAME_UNKNOWN(2.50)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2019 06:13:01 -0000 On Sat, 2019-01-05 at 20:39 -0500, Bob Healey wrote: > I've been updating my 11.2 systems to 12 via freebsd-update. It has > not > been a smooth process at all. The virtual machines I did before the > start of the new year had no issues. I posted the other day about > issues with a C2000 Atom and the BTX loader hanging. > > Today I've run into 2 different problems. The first is a host that > hard > resets with a hypertransport error and bad dimm when something tries > to > write to drives connected to the onboard SATA controller. The second > is > when updating ports on a different system between the two post reboot > freebsd-update installs, fetch is broken due to SSL problems. > > I was able to work past that via pkg-static list > pkg.lst && pkg- > static > delete -f \*, doing the second install, and reinstalling all packages > from scratch, but it was very frustrating and annoying to have to > work > through. 12.0 really feels like a late stage beta or release > candidate > with all the incompatibilities and work arounds required. > > Is anyone else having similar issues, or have I just been > extraordinarily unlucky? > I had ZFS problems with Beta, solved by reverting back to 11.2 (I pretested in a virtual instance without ZFS and without trouble). I am presently running 12.0 in one virtual instance and on one consumer-grade bare metal, which has a known memory problem. 12.0 is working in those two cases. Bare metal: FreeBSD 12.0-STABLE r342776 GENERIC amd64 FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LVM 6.0.1) VT(vga): resolution 640x480 CPU: AMD FX(tm)-9590 Eight-Core Processor (4721.76-MHz K8- class CPU) Origin="AuthenticAMD" Id=0x600f20 Family=0x15 Model=0x2 Stepping=0 Features=0x178bfbff Features2=0x3e98320b AMD Features=0x2e500800 AMD Features2=0x1ebbfff Structured Extended Features=0x8 SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=65536 TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 33319538688 (31775 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 8 core(s)