On Mon, 23 Apr 2001, Mikkel L. Ellertson wrote:
>
> First, use rpm -Va and make sure the files are what they should be.
> If the files are ok, then run memtest86 To check your memory.
I did rpm -Va yesterday. I don't recall if it was done before or after
reboot, but I was very surprised that it actually almost finished (it only
failed to check the XFree86-libs). Anyway, the output from rpm -Va shows
no sign of my system being compromised.
> also check that your cooling fans are working, and that the case vents
> are not clogged. I suspect a cooling problem, but that should show up
> in windows more then Linux, or a memory problem. Memory problems tend
> to show up more in Linux then in windows because Linux tends to use all
> memory.
I looked at the recently redhat kernel update package (released last
week, 2.2.19). It said it fixes minor problem in virtual memory. I wonder
if this means that my kernel (2.2.17, also from redhat updated) is having
this virtual memory problem that causes any program to segmentation fault
randomly.
Here is the gdb -c core output. As far as I remember it doesn't matter
what program segmentation fault, the output of gdb -c core is always
(I have checked at least more than 50 of them).
Core was generated by `lynx'.
Program terminated with signal 11, Segmentation fault.
#0 0x4000964f in ?? ()
Thanks
Jimmy
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
