From owner-freebsd-stable@freebsd.org Tue Feb 18 17:44:29 2020 Return-Path: Delivered-To: freebsd-stable@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 27BB124165D for ; Tue, 18 Feb 2020 17:44:29 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [31.24.6.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48MSsS0vpVz3Q70 for ; Tue, 18 Feb 2020 17:44:27 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [2001:470:6cc4:1:225:ff:fe46:71cf] (helo=foula.drayhouse.twisted.org.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.3:TLS_AES_128_GCM_SHA256:128) (Exim 4.92.3 (FreeBSD)) (envelope-from ) id 1j46ux-000HY8-U3 for freebsd-stable@freebsd.org; Tue, 18 Feb 2020 17:44:19 +0000 Subject: Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life To: freebsd-stable@freebsd.org References: <20200217231452.717FA1E820@freefall.freebsd.org> From: Pete French Message-ID: <0407fca5-6f46-b8bb-bc65-5a22f83a5644@ingresso.co.uk> Date: Tue, 18 Feb 2020 17:44:19 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 48MSsS0vpVz3Q70 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=ingresso.co.uk; spf=pass (mx1.freebsd.org: domain of petefrench@ingresso.co.uk designates 31.24.6.74 as permitted sender) smtp.mailfrom=petefrench@ingresso.co.uk X-Spamd-Result: default: False [-6.12 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:31.24.6.74]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-3.32)[ip: (-9.81), ipnet: 31.24.0.0/21(-4.91), asn: 16082(-1.80), country: GB(-0.07)]; DMARC_POLICY_ALLOW(-0.50)[ingresso.co.uk,none]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16082, ipnet:31.24.0.0/21, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Feb 2020 17:44:29 -0000 On 18/Feb/2020 17:19, Tomasz CEDRO wrot> But also as this DRM user (for Intel and AMD) I have experienced the > related hiccups, problems, and problems solutions. It does not look > like a FreeBSD way, but more like Linux way. I never noticed anything > like this before. Sure, I can see this only as the end-user, maybe > tester, I did no commits, so in theory I cannot complain, but it seems > like more experienced kernel people could take part in this kind of > solution architecture and design right from start in order to prevent > avalanche of future problems and problematic solutions that will > generate more problems. > > Another problem is the VirtualBox virtualization that is not really > usable anymore. I am aware of closed-source VBox Guest Additions > problem. My VM works fine for a first minute or two but then it stops > when I start working on it. With DRM and Framebuffer X11 drivers so it > does not seem related. Both the DRM issue and VirtualBox are fixed by making sure you recompile and install the kernel modules from the source in /usr/ports when you upgrade the OS, or if 'pkg upgrade' overwrites them. Its a bit annnoying, but hardly a showstopper I find. VirtualBox done this way is perfectly stable for me, as is DRM these days. cheers, -pete. PS; If you are running VirtualBox on top of ZFS then make sure you have the approrpiate AIO tunings in sysctl.conf though.