Re: Problems since 5.3-RELEASE-p15
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 (core dumped) SMART overall-health self-assessment test result: PASSED Sorry, I think I'm fresh out of ideas. Since no-one else is chiming in, it might be worth trying a fresh message with a fresh subject and just try and summarise the problems. Someone out there must have more experience of finding hardware faults than I do. (I still think it must be hardware. The intermittent faults in a variety of bits of software just scream that. The combination of core dumps and the ld.so error are interesting and should be a clue, but I don't know how to interpret it). Best, --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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. Imagine if it makes no sense to you how *I* must be feeling! 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 (core dumped) Jul 9 03:01:30 himinbjorg kernel: Jul 9 03:01:30 himinbjorg kernel: pid 49967 (mailwrapper), uid 0: exited on signal 11 (core dumped) and then goes down hill from there : Jul 9 03:01:31 himinbjorg kernel: pid 49969 (sendmail), uid 25: exited on signa l 11 Jul 9 03:01:31 himinbjorg kernel: Jul 9 03:01:31 himinbjorg kernel: pid 49969 (sendmail), uid 25: exited on signal 11 Jul 9 03:10:02 himinbjorg kernel: pid 50135 (rmail), uid 66: exited on signal 1 1 (core dumped) Jul 9 03:10:02 himinbjorg kernel: Jul 9 03:10:02 himinbjorg kernel: pid 50135 (rmail), uid 66: exited on signal 11 (core dumped) Jul 9 03:10:04 himinbjorg kernel: pid 50151 (uuxqt), uid 66: exited on signal 1 1 Jul 9 03:10:04 himinbjorg kernel: Jul 9 03:10:04 himinbjorg kernel: pid 50151 (uuxqt), uid 66: exited on signal 11 Jul 9 03:10:05 himinbjorg kernel: pid 50152 (sh), uid 0: exited on signal 11 (c ore dumped) Jul 9 03:10:05 himinbjorg kernel: Jul 9 03:10:05 himinbjorg kernel: pid 50152 (sh), uid 0: exited on signal 11 (core dumped) Jul 9 03:12:01 himinbjorg kernel: pid 50191 (sleep), uid 0: exited on signal 11 (core dumped) Jul 9 03:12:01 himinbjorg kernel: pid 50192 (mailwrapper), uid 0: exited on sig nal 11 (core dumped) Jul 9 03:12:01 himinbjorg kernel: pid 50193 (stunnel), uid 0: exited on signal 11 (core dumped) Jul 9 03:12:01 himinbjorg kernel: pid 50194 (uuxqt), uid 66: exited on signal 1 1 Jul 9 03:12:01 himinbjorg kernel: Jul 9 03:12:01 himinbjorg kernel: pid 50191 (sleep), uid 0: exited on signal 11 (core dumped) Jul 9 03:12:01 himinbjorg kernel: Jul 9 03:12:01 himinbjorg kernel: pid 50192 (mailwrapper), uid 0: exited on signal 11 (core dumped) Jul 9 03:12:01 himinbjorg kernel: Jul 9 03:12:01 himinbjorg kernel: pid 50193 (stunnel), uid 0: exited on signal 11 (core dumped) Jul 9 03:12:01 himinbjorg kernel: Jul 9 03:12:01 himinbjorg kernel: pid 50194 (uuxqt), uid 66: exited on signal 11 Jul 9 03:12:01 himinbjorg kernel: pid 50195 (sleep), uid 0: exited on signal 11 (core dumped) Jul 9 03:12:01 himinbjorg kernel: pid 50196 (mailwrapper), uid 0: exited on sig nal 11 (core dumped) Jul 9 03:12:01 himinbjorg kernel: Jul 9 03:12:01 himinbjorg kernel: pid 50195 (sleep), uid 0: exited on signal 11 (core dumped) Jul 9 03:12:01 himinbjorg kernel: Jul 9 03:12:01 himinbjorg kernel: pid 50196 (mailwrapper), uid 0: exited on signal 11 (core dumped) Jul 9 03:15:04 himinbjorg kernel: pid 50229 (sendmail), uid 0: exited on signal 11 and happens until... Jul 9 03:55:00 himinbjorg kernel: Jul 9 03:55:00 himinbjorg kernel: pid 50481 (sh), uid 0: exited on signal 11 (core dumped) Jul 9 03:55:00 himinbjorg kernel: Jul 9 03:55:00 himinbjorg kernel: pid 50482 (sh), uid 0: exited on signal 11 (core dumped) Jul 9 03:57:00 himinbjorg kernel: pid 50484 (sh), uid 0: exited on signal 11 (c ore dumped) Jul 9 03:57:00 himinbjorg kernel: Jul 9 03:57:00 himinbjorg kernel: pid 50484 (sh), uid 0: exited on signal 11 (core dumped) and then everything is fine again. I hadn't been home since the morning of the 8th, and if I'm up at 3am its NOT a good thing usually So wasn't like I was here doing anything at the time. 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. Already had that installed smartctl version 5.33 [i386-portbld-freebsd5.3] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: FUJITSU MHT2060AH Serial Number:NP0DT512J16R Firmware Version: 006C User Capacity:60,011,642,880 bytes Device is:In smartctl database [for details use: -P show] ATA Version is: 6 ATA Standard is: ATA/ATAPI-6 T13 1410D revision 3a Local Time is:Tue Jul 12 13:14:56 2005 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto
Re: Problems since 5.3-RELEASE-p15
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 running it for at least several hours, though it might not take that long. Your BIOS might also support extended memory tests (try disabling quick POST) though they are supposed to be less effective than memtest86. Ok, will try that. I run SETI so I think I'm constantly stressing the machine. But I'll give it a try. *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 Windows virus scans, it seems like a necessary evil in this case. 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. Tuc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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 Windows virus scans, it seems like a necessary evil in this case. 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 intermittent problem. Could something be overheating? Are you still getting random segfaults? Is there *any* pattern you can see? --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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 intermittent problem. Understood. This is a Dell Laptop that JUST went out of 3 year warranty in May. Its still in pretty great condition, but if I had to start screwing around with it, I might just get something else... Could something be overheating? I replaced the fans 6 months ago because it seemed a bearing was going. (And we found SO MUCH dust inside it that it wasn't cooling properly. Now that its clean, the fans even turn off at times!) Its happened on my lap, its happened on a glass table. Are you still getting random segfaults? Is there *any* pattern you can see? 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. 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 Thanks, Tuc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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 and it doesn't cause problems when upgrading the base system. The only trouble I ever have is when X is upgraded. After upgrading X, I also have to re-build my nvidia drver. That's not a drama though, you just do do a portupgrade -f nvidia-driver and it's fine. My current system started as 5.2.1-Release is now on 5.4-p1. Even the change from XFree86 to X.org didn't cause problems with the driver. Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc pgpm8KrY79TkZ.pgp Description: PGP signature
Re: Problems since 5.3-RELEASE-p15
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: exited on signal 11 (core dumped) Jun 21 01:24:17 himinbjorg kernel: Jun 21 01:24:17 himinbjorg kernel: pid 5693 (javac), uid 0: exited on signal 11 (core dumped) Jun 21 01:25:28 himinbjorg kernel: pid 14996 (javac), uid 0: exited on signal 11 (core dumped) Jun 21 01:25:28 himinbjorg kernel: Jun 21 01:25:28 himinbjorg kernel: pid 14996 (javac), uid 0: exited on signal 11 (core dumped) Jun 21 01:25:29 himinbjorg kernel: pid 15016 (java), uid 0: exited on signal 11 (core dumped) Jun 21 01:25:29 himinbjorg kernel: Jun 21 01:25:29 himinbjorg kernel: pid 15016 (java), uid 0: exited on signal 11 (core dumped) Which I don't understand because I don't know what I was doing that needed java. I think it might have been part of upgrading the nvidia driver. 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 running it for at least several hours, though it might not take that long. Your BIOS might also support extended memory tests (try disabling quick POST) though they are supposed to be less effective than memtest86. Ok, will try that. I run SETI so I think I'm constantly stressing the machine. But I'll give it a try. However, if this *is* a hardware problem then I would worry about that first. The upgrade to 5.3-p15 (presumably from 5.3-p-something else) could be pure coincidence. I mean, you have to be doing *something* before getting a hardware fault! Such is true.. Thanks, Tuc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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 kernel: pid 5693 (javac), uid 0: exited on signal 11 (core dumped) Jun 21 01:24:17 himinbjorg kernel: Jun 21 01:24:17 himinbjorg kernel: pid 5693 (javac), uid 0: exited on signal 11 (core dumped) Jun 21 01:25:28 himinbjorg kernel: pid 14996 (javac), uid 0: exited on signal 11 (core dumped) Jun 21 01:25:28 himinbjorg kernel: Jun 21 01:25:28 himinbjorg kernel: pid 14996 (javac), uid 0: exited on signal 11 (core dumped) Jun 21 01:25:29 himinbjorg kernel: pid 15016 (java), uid 0: exited on signal 11 (core dumped) Jun 21 01:25:29 himinbjorg kernel: Jun 21 01:25:29 himinbjorg kernel: pid 15016 (java), uid 0: exited on signal 11 (core dumped) Which I don't understand because I don't know what I was doing that needed java. I think it might have been part of upgrading the nvidia driver. I wouldn't have thought so. If I do: % cd /usr/ports/x11/nvidia-driver % make pretty-print-build-depends-list % make pretty-print-run-depends-list This port requires package(s) gettext-0.14.5 libiconv-1.9.2_1 linux-XFree86-libs-4.3.99.902_3 linux-expat-1.95.5_3 linux-fontconfig-2.1_3 linux_base-8-8.0_6 popt-1.7 rpm-3.0.6_10 to run. There's no mention of java. I wouldn't say it definitively rules it out though. Are you sure that java wasn't left over from 4.X? One thing to try is: % pkg_info | egrep -i java javavmwrapper-2.0_4 Wrapper script for various Java Virtual Machines jdk-1.4.2p7_1 Java Development Kit 1.4.2 linux-sun-jdk-1.4.2.08_2 Sun Java Development Kit 1.4 for Linux vnc-4.1.1 Display X and Win32 desktops on remote X/Win32/Java display % pkg_info -R jdk-1.4.2p7_1 Information for jdk-1.4.2p7_1: % pkg_info -R linux-sun-jdk-1.4.2.08_2 Information for linux-sun-jdk-1.4.2.08_2: Which shows that nothing on my system positively requires java (though mozilla et al. use it). I doubt it's a browser as javac is the compiler rather than the runtime environment (which has always seemed to crash at irregular intervals for me). 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 running it for at least several hours, though it might not take that long. Your BIOS might also support extended memory tests (try disabling quick POST) though they are supposed to be less effective than memtest86. Ok, will try that. I run SETI so I think I'm constantly stressing the machine. But I'll give it a try. *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 Windows virus scans, it seems like a necessary evil in this case. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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 table Are you sure you rebuilt and re-installed both your kernel and your world? If they are out of sync, that can cause unusual problems. Yes. I have a 2 part process I run : STEP 1: cvsup -g -L 2 ./stable-supfile (cd /usr/src;make buildworld) (cd /usr/src;make buildkernel KERNCONF=HIMINBJORG53) echo Press ENTER to install kernel read c (cd /usr/src;make installkernel KERNCONF=HIMINBJORG53) echo Need to reboot STEP 2: echo Press ENTER to mergemaster read a mergemaster -p echo Press ENTER to installworld read b (cd /usr/src;make installworld) echo Press ENTER to mergemaster read c mergemaster echo REBOOT I guess I could re-run it and see if it continues. 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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 table Is there a more or less reliable way to reproduce this? What should I run to try to reproduce this? Thats the thing. I can't force it to happen. It just does. Infact, when looking at my logs, it happened at 1am this morning and I didn't even realize it (And wasn't anywhere near the machine). I can't do any debugging once it starts since EVERYTHING cores that I try to run. This isn't a production server so I'm not dying for a solution, but it would be nice to not have this problem. Thanks, Tuc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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 run-time symbol table Are you sure you rebuilt and re-installed both your kernel and your world? If they are out of sync, that can cause unusual problems. Yes. I have a 2 part process I run : [process elided] I guess I could re-run it and see if it continues. 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 running it for at least several hours, though it might not take that long. Your BIOS might also support extended memory tests (try disabling quick POST) though they are supposed to be less effective than memtest86. 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 I've never used any fancy features of my NVidia under FreeBSD (never need them!) and the stock Xorg Nvidia driver works just fine on my aging GeForce2, so I can't really comment on that. But there have been many comments on this list that 5.4 is a real improvement over 5.3 (went straight from 4.11 myself). However, if this *is* a hardware problem then I would worry about that first. The upgrade to 5.3-p15 (presumably from 5.3-p-something else) could be pure coincidence. I mean, you have to be doing *something* before getting a hardware fault! --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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 table Is there a more or less reliable way to reproduce this? What should I run to try to reproduce this? -- Dmitry We live less by imagination than despite it - Rockwell Kent, N by E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems since 5.3-RELEASE-p15
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 table Are you sure you rebuilt and re-installed both your kernel and your world? If they are out of sync, that can cause unusual problems. If you have upgraded to 5.3-RELEASE-p15 why not just upgrade to 5.4-RELEASE-p*? --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
