From owner-freebsd-questions@FreeBSD.ORG Fri Jul 8 00:13:25 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 841EA16A41C for ; Fri, 8 Jul 2005 00:13:25 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A17F43D49 for ; Fri, 8 Jul 2005 00:13:24 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.37.55] ([82.41.37.55]) by smtp-out3.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Fri, 8 Jul 2005 01:14:06 +0100 Message-ID: <42CDC522.5010309@dial.pipex.com> Date: Fri, 08 Jul 2005 01:13:22 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.8) Gecko/20050530 X-Accept-Language: en, en-us, pl MIME-Version: 1.0 To: Tuc at T-B-O-H References: <200507072314.j67NENDG020566@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <200507072314.j67NENDG020566@himinbjorg.tucs-beachin-obx-house.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 08 Jul 2005 00:14:06.0366 (UTC) FILETIME=[F444B3E0:01C58351] Cc: freebsd-questions@freebsd.org Subject: Re: Problems since 5.3-RELEASE-p15 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2005 00:13:25 -0000 Tuc at T-B-O-H wrote: >The only pattern I see is that it starts all of a sudden, goes for >a little while, EVERYTHING you try to do fails, I get the >/libexec/ld-elf.so.1: top: Shared object has no run-time symbol table >type errors, and then all of a sudden it goes about its merry way. > > I'm not sure what a "run-time symbol table" is, and if it gets >rebuilt at any time, or is something thats part of the program, or what.... >But its not like one time it behaves one way, then another time it behaves >another. > My description would be hazy at best, so hopefully someone more au fait will chime in. But I can definitively state that, no it isn't something that gets rebuilt every so often. However, if you run ktrace on a simple program like ls: ktrace ls then do a kdump | less, you will see that after finding ls, /libexec/ld-elf.so.1 is the first thing accessed. So, when things start working again, /libexec/ld-elf.so.1 is magically fixed, which just makes no sense. I assume there are no other messages obvious errors in /var/log/messages? One final thought is that it could be the disk. You could try installing smartmontools and see if the disk thinks it is OK -- though of course it could be the controller. But in such a case I might expect other errors. >I'd think if it was a memory issue, it'd be something other than >the same "Shared object..." thing each time. One time it'd be a bus error, >another time a "this isn't executable", etc.... > > The classic bad memory symptoms are periodic reboots, and random segmentation faults. The latter is particular to bad memory, I would say. The fomer can have other causes. It's the intermittent nature of the fault that really makes me think hardware. Am I right in remembering that you upgraded to 5.4 and still had the same problems? --Alex