From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 15:23:26 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 85E1A633; Tue, 1 Jul 2014 15:23:26 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2DE572CC1; Tue, 1 Jul 2014 15:23:25 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 764FB1534C0; Tue, 1 Jul 2014 17:23:17 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10Mod62FMcuw; Tue, 1 Jul 2014 17:23:15 +0200 (CEST) Received: from [IPv6:2001:4cb8:3:1:49f0:83be:af19:5ffb] (unknown [IPv6:2001:4cb8:3:1:49f0:83be:af19:5ffb]) by smtp.digiware.nl (Postfix) with ESMTP id 2CC56153448; Tue, 1 Jul 2014 17:23:15 +0200 (CEST) Message-ID: <53B2D262.2040502@digiware.nl> Date: Tue, 01 Jul 2014 17:23:14 +0200 From: Willem Jan Withagen Organization: Digiware Management b.v. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "Rang, Anton" , "O. Hartmann" , Dimitry Andric Subject: Re: [CURRENT]: weird memory/linker problem? References: <20140622165639.17a1ba1e.ohartman@zedat.fu-berlin.de> <20140623163115.03bdd675.ohartman@zedat.fu-berlin.de> <20140701150755.548ed6b9.ohartman@zedat.fu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Tue, 01 Jul 2014 15:23:26 -0000 On 2014-07-01 16:48, Rang, Anton wrote: > DOT => DOD > > 444F54 => 444F44 > > That's a single-bit flip. Bad memory, perhaps? Very likely, especially if the system does not have ECC.... It just happens on rare occasions that a alpha particle, power cycle, or any things else disruptive damages a memory cell. And it could be that it requires a special pattern of accesses to actually exhibit the error. In the past (199x's) 'make buildworld' used to be a rather good memory tester. But nowadays look at http://www.memtest.org/ This tool has found all of the bad memory in all the systems I used and or build for others... Note that it might take a few runs and some more heat to actually trigger the faulty cell, but memtest86 will usually find it. Note that on big systems with lots of memory it can take a loooooong time to run just one full testset to completion. --WjW > > Anton > > -----Original Message----- > From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of O. Hartmann > Sent: Tuesday, July 01, 2014 8:08 AM > To: Dimitry Andric > Cc: Adrian Chadd; FreeBSD CURRENT > Subject: Re: [CURRENT]: weird memory/linker problem? > > Am Mon, 23 Jun 2014 17:22:25 +0200 > Dimitry Andric schrieb: > >> On 23 Jun 2014, at 16:31, O. Hartmann wrote: >>> Am Sun, 22 Jun 2014 10:10:04 -0700 >>> Adrian Chadd schrieb: >>>> When they segfault, where do they segfault? >> ... >>> GIMP, LaTeX work, nothing special, but a bit memory consuming >>> regrading GIMP) I tried updating the ports tree and surprisingly the >>> tree is left over in a unclean condition while /usr/bin/svn segfault >>> (on console: pid 18013 (svn), uid 0: exited on signal 11 (core dumped)). >>> >>> Using /usr/local/bin/svn, which is from the devel/subversion port, >>> performs well, while FreeBSD 11's svn contribution dies as described. It did not hours ago! >> >> I think what Adrian meant was: can you run svn (or another crashing >> program) in gdb, and post a backtrace? Or maybe run ktrace, and see >> where it dies? >> >> Alternatively, put a core dump and the executable (with debug info) in >> a tarball, and upload it somewhere, so somebody else can analyze it. >> >> -Dimitry >> > > It's me again, with the same weird story. > > After a couple of days silence, the mysterious entity in my computer is back. This time it is again a weird compiler message of failure (trying to buildworld): > > [...] > c++ -O2 -pipe -O3 -O3 > c++ -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. > -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include > -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd11.0\" > -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd11.0\" -DDEFAULT_SYSROOT=\"\" > -Qunused-arguments -I/usr/obj/usr/src/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -Wno-c++11-extensions -c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Host.cpp -o Host.o > --- GraphWriter.o --- In file included > from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/GraphWriter.cpp:14: /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Support/GraphWriter.h:269:10: > error: use of undeclared identifier 'DOD'; did you mean 'DOT'? O << DOD::EscapeString(Label); ^~~ DOT /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Support/GraphWriter.h:35:11: > note: 'DOT' declared here namespace DOT { // Private functions... ^ 1 error generated. > *** [GraphWriter.o] Error code 1 > > > Well, in the past I saw many of those messages, especially not found labels of routines in shared objects/libraries or even those "funny" misspelled messages shown above. > > I can not reproduce them after a reboot, but as long as the system is running with this error occured, it is sticky. So in order to compile the OS successfully, I reboot. > > Does anyone have an idea what this could be? Since it affects at the moment only one machine (the other CoreDuo has been retired in the meanwhile), it feels a bit like a miscompilation on a certain type of CPU. > > Thanks for your patience, > > Oliver > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >