From owner-freebsd-current@freebsd.org Sun May 7 20:35:53 2017 Return-Path: Delivered-To: freebsd-current@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 AA9ECD533CB for ; Sun, 7 May 2017 20:35:53 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4456716D4; Sun, 7 May 2017 20:35:52 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with SMTP id 7Su8d3m7Vyd2D7Su9drLIA; Sun, 07 May 2017 14:35:45 -0600 X-Authority-Analysis: v=2.2 cv=F5wnTupN c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=kj9zAlcOel0A:10 a=tJ8p9aeEuA8A:10 a=pGLkceISAAAA:8 a=BWvPGDcYAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=LFLN1YyAq9_VXxo-fdAA:9 a=CjuIK1q_8ugA:10 a=1rTF-VXdzdgA:10 a=6kGIvZw6iX1k4Y-7sg4_:22 a=pxhY87DP9d2VeQe4joPk:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 2479D10ED; Sun, 7 May 2017 13:35:44 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id v47KZgBY066233; Sun, 7 May 2017 13:35:42 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201705072035.v47KZgBY066233@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Andrey Fesenko cc: Ngie Cooper , Cy Schubert , Kyle Evans , Alastair Hogge , Vladimir Zakharov , Ed Maste , freebsd-current , Dimitry Andric Subject: Re: make buildworld broken at r317821 (libsysdecode) In-Reply-To: Message from Andrey Fesenko of "Sun, 07 May 2017 05:55:08 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 May 2017 13:35:42 -0700 X-CMAE-Envelope: MS4wfMyvHUeAhwo2A73DGh8OL2hLVF3GAJ4F/a7dd3rbRb4TeArmEh+Y/PRj5aU3Sh1LhiEx35fQvTP+YRSqPcIdxQlWGqUsyRJMKBFBoJrtoOiPftB7w1Ox 58TzpAPj7h4stINP5HEs1c5CYHg5/iSyEHGKC7xXLkSoqqQA+JMqIeqFiwTGZNOVbEM4fUEkGcnutJsvEXwwQd3bMkgAsDN8Z4VIqdnuD4tKrdnNSvzqLwJj 65QHNqbzWR2at5KuV7XjaTydACnqhuFb8mPAtVZxlzBDMOCP7K560XZKOEhGs/rjy9oV0WRvszUwBVQk3aW7bLsda/poQTfDgBN+FqCjsBsGAGphd72o09FS l9IKz17YI6CuDv65HUwv5znG4qMuOwWN7Lgj4c/0SJe6dUWxRug= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 07 May 2017 20:35:53 -0000 In message , Andrey Fesenko writes: > On Sat, May 6, 2017 at 2:52 AM, Ngie Cooper wrote: > > On Fri, May 5, 2017 at 4:43 PM, Cy Schubert wrot > e: > > > > ... > > > >> You have a bad DIMM. I had this same problem on my laptop but not on my > >> servers downstairs. That suggested that since all four machines were > >> running the same software the difference between them was hardware. > >> Replacing the memory in my laptop made this problem go away. > >> > >> I have a question for you. Do you use ZFS? ZFS exercises memory quite > >> aggressively. I also had this problem when I replaced my UFS filesystems > >> with ZFS on my testbed many moons ago. It even suffered random kernel > >> panics. Here again, replacing the memory resolved the issue. > > > > We need more information first before saying "bad hardware" -- in > > particular, was the machine overtaxed, were the input files proper, > > etc? > > > > I'm asking because clang has a number of bugs in bugzilla where the > > host ran out of memory trying to compile things and clang didn't fail > > gracefully when allocating memory, handling inputs, etc. > > > > Thanks, > > -Ngie > > Sorry, really my root ZFS pool is corrupt :( That was another symptom of the problem I had on my testbed when it suffered random kernel panics due to marginal RAM. It was OK with UFS but inadequate for ZFS. My zpools became so horribly corrupt that nothing could correct them and at one point I couldn't even retrieve anything from one of the zpools. (Good thing it was testbed and that the data was replicated on my prod machine.) It was at that point I ran some RAM tests using memtest86+ from ports. It found no bad RAM. Not trusting it, I replaced all the RAM in that machine anyway. That was a few years ago and I haven't had a problem since. There is a reason it is recommended that one use ECC corrected memory with ZFS. ZFS error correction is only as good as the installed RAM. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.