Tuc at T-B-O-H wrote:
I assume there are no other messages obvious errors in /var/log/messages?
Nope, I have debug turned all the way up... And just out of the blue
on the 9th at 3am I see :
Jul 9 03:01:30 himinbjorg kernel: pid 49967 (mailwrapper), uid 0: exited on sig
nal 11
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.
If the problem is intermittent then I would suspect the hardware (I
know, everyone always says that, but I really have used a brand new
server which segfaulted randomly and it really was a memory problem).
Try building a memtest86 CD from the ports (from a different machine
perhaps) and
Tuc at T-B-O-H wrote:
*If* there are intermittent memory errors, then it could be that SETI
always happens to get them in the data it is dealing with, in which case
it might run perfectly happily but just produce the wrong results.
Memtest is dull, and stops you using your PC, but like
I did the standard tests for 24 hours (21 passes) and it didn't fail.
I ran the 90 minute fading one for 24 hours (8 runs) and it too didn't fail.
It's almost a shame when a test like this passes. It's much easier to
just replace some memory and get on with things than be stuck with an
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.
On Tuesday 21 June 2005 08:34, Tuc at T-B-O-H wrote:
If you have upgraded to 5.3-RELEASE-p15 why not just upgrade to
5.4-RELEASE-p*?
I'm always nervous going up a release due to my NVIDIA card
Thanks, Tuc
I use the nvidia-driver port with xorg for my nvidia card
Yes. I have a 2 part process I run :
[process elided]
I guess I could re-run it and see if it continues.
I took the plunge and am now at 5.4-RELEASE-p2 I
upgraded my Nvidia driver too.
So far I saw :
Jun 21 01:24:17 himinbjorg kernel: pid 5693 (javac), uid 0:
Tuc at T-B-O-H wrote:
Yes. I have a 2 part process I run :
[process elided]
I guess I could re-run it and see if it continues.
I took the plunge and am now at 5.4-RELEASE-p2 I
upgraded my Nvidia driver too.
So far I saw :
Jun 21 01:24:17 himinbjorg
On 6/17/05, Tuc at T-B-O-H [EMAIL PROTECTED] wrote:
Hi,
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no run-time
On 6/17/05, Tuc at T-B-O-H [EMAIL PROTECTED] wrote:
Hi,
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no
Tuc at T-B-O-H wrote:
On 6/17/05, Tuc at T-B-O-H [EMAIL PROTECTED] wrote:
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no
On 6/17/05, Tuc at T-B-O-H [EMAIL PROTECTED] wrote:
Hi,
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no run-time
On 6/17/05, Tuc at T-B-O-H [EMAIL PROTECTED] wrote:
Hi,
Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into
problems... All of a sudden, anything I do results in a Segfault. Sometimes
I'll get :
/libexec/ld-elf.so.1: top: Shared object has no run-time symbol
14 matches
Mail list logo
