From owner-svn-src-head@freebsd.org Fri Mar 3 14:17:36 2017 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A068CF5288; Fri, 3 Mar 2017 14:17:36 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 25AC415AD; Fri, 3 Mar 2017 14:17:35 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v23EHXpl070032; Fri, 3 Mar 2017 06:17:33 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v23EHX59070031; Fri, 3 Mar 2017 06:17:33 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201703031417.v23EHX59070031@pdx.rh.CN85.dnsmgr.net> Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] In-Reply-To: <8D803761-644A-4E72-928F-2E96525A1A11@dsl-only.net> To: Mark Millard Date: Fri, 3 Mar 2017 06:17:33 -0800 (PST) CC: sgk@troutmask.apl.washington.edu, Mateusz Guzik , svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 14:17:36 -0000 > On 2017-Mar-2, at 7:19 AM, Steve Kargl wrote: > > On Thu, Mar 02, 2017 at 01:10:21PM +0100, Mateusz Guzik wrote: > > On Wed, Mar 01, 2017 at 09:45:07AM -0800, Mark Millard wrote: > >> > >>> Summary of the transition interval: > >>> > >>> So for powerpc64 (and powerpc?) It is a good > >>> idea to avoid anything that is after -r313254 > >>> and before -r314474 in head. (Would this be > >>> appropriate for a UPDATING notice given its > >>> span?) > >>> > >>> There may be other architectures that might have > >>> a similar status(?): the last fixes involved were > >>> not in Machine Dependent code. (Some architectures > >>> are apparently insensitive to the errors, such as > >>> amd64). > >>> > >> > >> When following current you are expected to be on the newest revision, > >> so I don't think mentioning interim broken releases makes much sense. > >> > > > > Documenting the range may aid those bisecting src/ to find a bug. > > How is one to know that anything in the range that Mark points > > out should be skipped on powerpc64? > > > > -- > > Steve > > I have tested with a TARGET_ARCH=powerpc -r314473 build and > its kernel version has locking problems like > TARGET_ARCH=powerpc64 does for that version. > > [Note: This was run on a PowerMac G5 so-called "Quad Core" > so most of the memory was ignored.] > > Both TARGET_ARCH=powerpc64 and TARGET_ARCH=powerpc need -r314474 > or later as of the new locking. > > I've not explicitly tested other architectures. As I remember > armv6/v7 are classified as having some from of a weak memory > model compared to the likes of amd64. If so armv6/v7 might be > candidates for having problems. There might be other candidates. I also had locking issues on amd64 around this build time that sent me down a week long rabbit hole chasing what I thought was a bug in the new AMD/IOMMU code. IMHO if we can at least flag prior snapshot builds as "Broken for reason X" it might save someone some time and time is a one way depleting resource usually worth saving if possible. If needed I can dig out the specifc build. Oh, nvm, let me just do that, it was r309302. This revision I beleive is a november snapshot. It has kernel panics due to spinlock timeout and sparatic deadlock that is undetected. -- Rod Grimes rgrimes@freebsd.org