Date: Mon, 23 Jun 2014 09:39:46 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Adrian Chadd <adrian@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: [CURRENT]: weird memory/linker problem? Message-ID: <20140623093946.58d72dd1.ohartman@zedat.fu-berlin.de> In-Reply-To: <CAJ-Vmok0Oh6XGe62acXE-82pTmEaouibd1GqDT0pCo8P6x6Hog@mail.gmail.com> References: <20140622165639.17a1ba1e.ohartman@zedat.fu-berlin.de> <CAJ-Vmok0Oh6XGe62acXE-82pTmEaouibd1GqDT0pCo8P6x6Hog@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/.JMSt9T11=MSKjRiMnlZVfo Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sun, 22 Jun 2014 10:10:04 -0700 Adrian Chadd <adrian@freebsd.org> schrieb: > When they segfault, where do they segfault? >=20 >=20 >=20 > -a >=20 >=20 I have not investigated this issue so far, since I was convinced - in the f= irst place - it is triggered by a defetive memory system. So I rebooted immediately bein= g glad having found a "solution". I will check next time it happens again. oh > On 22 June 2014 07:56, O. Hartmann <ohartman@zedat.fu-berlin.de> wrote: > > > > Hello. > > > > I face a strange problem on a set of CURRENT driven boxes. The systems = in question are > > all the same version of CURRENT (more or less, a week or so discrepancy= ). > > > > The boxes affected have 8 GB of RAM and are old-style Core2Duo systems. > > > > The phenomenon: > > > > Starting up the box shows the operating system working. But sometimes i= t is > > impossible to start certain applications, like Firefox - they segfault.= More > > disturbing is the fail of the linker when building world. Sometimes I g= et strange > > messages like > > > > relocation truncated to fit: R_X86_64_PC32 against symbol `__error' def= ined in .text > > > > when compiling/linking. The funny thing is: rebooting the box and doing= exactly the > > same very often leaves the system then operable - starting applications= works, > > compiling works! > > > > First I thought this could be a indication of a dying system and so I c= hecked the > > memory for two days non-stop without any indication of anything wrong. = The boxes do > > not have ECC RAM - it's Intel. > > > > I see this problem on two C2D based boxes relatively often (one E8400 t= wo core, > > another Q6600 quadcore, both systems have 8 GB RAM). This phenomenon al= so occured two > > or three months ago on another machine with 32 GB RAM and a Core-i7 393= 0K, but it > > went away (it was the very same error as shown above). > > > > Another system, a i3-3220 with 16 GB RAM never showed the problem altho= ugh that system > > build world also on a regular basis very frequent as the C2D systems do. > > > > Well, I feel a bit confused. On the first view, the problem looks weird= and it > > indicates a kind of memory problem - but testing the memory didn't show= anything > > wrong. > > > > Today "windowmaker" stopped starting due to a malformed command in one = of > > windowmaker's library. I did reboot the box and everything was all righ= t. Then, also > > today, I tried compiling world and I got a weird error message about a = misspelled > > "Int__xxx", I can not remember exactly the text, I rebooted and everyth= ing was all > > right again. > > > > Those errors are frequent on 8GB, C2D based systems and at the moment n= ot present any > > more on more modern systems with more memory as described above. This c= ould be a > > coincidence, but it is strange anyway. > > > > I do not exclude dying hardware, but I'd like to ask whether there is s= omething > > strange going on with FreeBSD's memory management at the moment and whe= ther those > > problems could also be triggered by some nasty bug? I never see a crash= (which would > > also indicated faulty hardware), I mostly realise those strange behavio= ur either > > after a fresh boot or after I ran some memory disk i/o intensive jobs, = like updating > > the ports tree. > > > > By the way, FreeBSD CURRENT suffer from a tremendous performance cut th= ese days when > > compiling world and updating the ports tree and running portmaster. On = one box, on > > which ports reside on a UFS partion, it takes more than 8 minutes to pa= ss the > > portmaster -da, which is quick when not compiling world. On another sys= tem on > > which /usr/ports is residing on ZFS (the box has 16GB RAM!), it takes s= ometimes 30(!) > > minutes to perform a "svn update" while compiling world (that is the i3= -3220 with 16 > > GB RAM system), it takes 6 - 15 minutes when the box is relaxed and upd= ating the > > ports tree the first time (every subsequent update is much faster). > > > > Well, I know these reports of mine are a bit weird since I have no exac= t log of the > > problems, but I think if there is an issue not with the hardware, I rep= ort those in. > > > > Regards, > > > > oh --Sig_/.JMSt9T11=MSKjRiMnlZVfo Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJTp9nGAAoJEOgBcD7A/5N8j/AH/RE6y/5TsCz4Zes23B+sdRBQ NCOCcjlAc2d3kd3pgAlNxbBNooRtkFqdnUYQEOjAHkTtDcDydccy+6ZV2cBOGZy0 7PlT3qZrPwIsGw9T6E+RmJdYz85TO10jypS4bkQ60f/gju3UynrAoCfcNu96WhTs g3s7MZUBfbgvihwCIcT7FjfIcBHu1xY6yvSfOwc0KqrrcME8OuxHffAdpp7C8HO5 jqyexfT4Tpq8GB7UOdFQySUBIJI/mGefZo+eRd7OxwOc0/d/bdabgty3xNbCg1jW XZ8VUpqVX6m6CJzDwv0kV5QtxabOA82/YJlhMhx2YJ6gJHYwrCIeALZBseT2Ax8= =CnBg -----END PGP SIGNATURE----- --Sig_/.JMSt9T11=MSKjRiMnlZVfo--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140623093946.58d72dd1.ohartman>