Neil Jolly said: > > Yeah it looks pretty nasty. I tried plugging in the error message into > google, and came up with a huge variety of issues. Most were minor non > fatal errors, but this one seems fatal. After questioning the guy who > monitors all the mail meaages I found this as well: > > /etc/cron.weekly/makewhatis.cron: > > /usr/sbin/makewhatis: line 352: 24727 Broken pipe find . > -name > '*' $findarg -print > 24728 Segmentation fault | $AWK ' > That message coincidently was sent shortly before the kernel errors > started appearing. Might have to join the kernel mailing list...
Hope you have lots of room for email if you join that mailing list :) It's pretty busy. You might want to try testing your RAM (http://www.memtest86.com/). Segmentation faults in processes and kernel panics are signs of possible buggy software, however in my experience it is more often then not a sign of dying or dead hardware.... bad RAM, faulty CPU, motherboard, etc. Sometimes it is hard to pin down which one but I would definitely try testing the RAM. You could also try a compile of a kernel (With a .config you know works) and see if it seg faults, if it does try it again and see if it seg faults again in the same place or different place. If you are able to test the box for a while (Ie, you can have it offline for the day), then you can try the kernel compile thing using a loop and let it compile the kernel over and over again for a few hours. Sometimes faulty CPUs only show signs of faultiness if they are really pushed for extended periods of time (Ie, they get too hot). A good howto on testing RAM and CPU can be found here: http://www-106.ibm.com/developerworks/library/l-hw1/ Cheers, -- Trevor Lauder Web: http://www.thelauders.net E-Mail: [EMAIL PROTECTED] Resume: http://www.thelauders.net/resume/ Gentoo Powered "Any intelligent fool can make things bigger and more complex... It takes a touch of genius -- and a lot of courage to move in the opposite direction." -- Albert Einstein
