Date: Fri, 5 May 2017 16:52:48 -0700 From: Ngie Cooper <yaneurabeya@gmail.com> To: Cy Schubert <Cy.Schubert@komquats.com> Cc: Andrey Fesenko <f0andrey@gmail.com>, Kyle Evans <kevans91@ksu.edu>, Alastair Hogge <agh@fastmail.fm>, Vladimir Zakharov <zakharov.vv@gmail.com>, Ed Maste <emaste@freebsd.org>, freebsd-current <freebsd-current@freebsd.org>, Dimitry Andric <dim@freebsd.org> Subject: Re: make buildworld broken at r317821 (libsysdecode) Message-ID: <CAGHfRMD=TCdQkJ54rKquDMj9z2jLOAK71p%2BthWg22Rb1K%2B-W0Q@mail.gmail.com> In-Reply-To: <201705052343.v45Nhsxq082981@slippy.cwsent.com> References: <f0andrey@gmail.com> <CA%2BK5SrNDL=LKRJm0PEgyme8VTHZeAry8XN_W4AMOkycDC_jUNw@mail.gmail.com> <201705052343.v45Nhsxq082981@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 5, 2017 at 4:43 PM, Cy Schubert <Cy.Schubert@komquats.com> wrote: ... > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGHfRMD=TCdQkJ54rKquDMj9z2jLOAK71p%2BthWg22Rb1K%2B-W0Q>