From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 Description of problem: I upgraded my kernel to 2.4.18-26.8.0. I boot into runlevel 3, after which I start kde by running startx. The machine was up for about three days when I saw an output on my console about an error message in kernel. I checked out /var/log/kern, and there were details about the kernel bug. I attach the relevant portion as the attachment. Also interesting to note is that at that point of time, I did a `top' and saw that 245M of the 255M RAM that I have was being used, and when I did a `startx', the machine hanged, and I had to reboot. After rebooting the machine seems to work fine. Version-Release number of selected component (if applicable): kernel-2.4.18-26.8.0 How reproducible: Didn't try Steps to Reproduce: Since this is a kernel error message I have no hooks to reproduce it. Additional info:
Created attachment 90553 [details] Relevant portion of my /var/log/kern
this kind of bug sometimes points to bad memory; could you do a testrun of the memtest86 program to test your memory?
Memtest86 Standard test took 4 hours and * minutes. Cached=256M, RsvdMem=136K, MemMap=e820-Std, Cache=On, ECC=Off, Test=Std Pass=5, Errors=67688, ECC Errs=0 Error Summary = Test 5: 2131 Errors, Test 6: 1 Errors. After this the test came back to test number 1, so I stopped this and booted Linux. I am guessing lots of errors in testing RAM, so my RAM is at fault. I don't know what steps to take so that Linux leaves these bad RAM blocks alone and doesn't use them. -V
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/