[sheflug] Oops

[lesleyb <lesley.binks [at] xxxxxxxxx>]

Hi

I have some oop's occurring.  I have checked the logs and the first one 
occurred on 12th February ( http://pastebin.com/565290 ).

The next wave has occurred today (http://pastebin.com/565562) and there 
were quiet a few in one go.  I don't know what happened to Oops 0000 
[#2] it never got to the logs.

I then had a change of Oops to 0002 (http://pastebin.com/565569).

I'm finding it difficult to sort out what's wrong here so can anyone 
help translate the oops messages into something meaningful?

History:

I have been experiencing some CPU overheating problems.  I have an 
Athlon XP 2K Palomino on an Asus A7V333 motherboard and, ever since I 
built it I have never been able to run it stably at 1667MHz.  The board 
is *not* in jumperfree mode and so I can only choose between 1250 MHz 
and 1667MHz.  The board has a thermal cutout on it and if the CPU gets 
too hot the cutout trips and simply stops the system dead in its tracks. 
There is a message to go into the Hardware Monitor in the BIOS on 
reboot.  Typically the temps were in the 70s.

I bought some more RAM and some new case fans and CPU cooler.  The case 
fans arrived first and were fitted on Friday and I ran the machine for 
about 8 hours until I had a thermal cutout occur.  The CPU cooler and 1G 
Kingston RAM arrived and were fitted on Monday along with an LG DVD RAM.
I used 88% silver thermal paste when fitting the CPU cooler.

Previously I was using 2x 256Mb PC2700 Samsung sticks and I had a couple 
of oops when I tried to reboot after fitting the new RAM, DVD and CPU 
cooler.  These oops do not appear in the syslog.

I reduced the board down to the new 1G yesterday afternoon and had a 
system freeze today.  I rebooted and checked the CPU temperature which 
was in the 50's - not enough to cause a thermal cutout.  This freeze 
occurred before today's oops.

I suspect today's modprobe oops (http://pastebin.com/565562) occurred 
when I tried combining 1x1Gb Kingston RAM and 1x256Mb Samsung, both 
PC2700 DDR 333MHz.

I did run memtest against all the memory and it passes them all.

I don't entirely understand these oops but have read they may simply be 
bugs in the kernel and that some people get them all the time.  I did 
check my syslog.  The first oops (http://pastebin.com/565290) occurs on 
12th Feb and seems to be an alloc problem while in screensaver mode 
because the process is lisa.

The second oops (http://pastebin.com/565562) seems to have occurred at 
boot time because it's modprobe that's suffering here.

The last oops (http://pastebin.com/565569) is an alloc problem on khelper.

My syslog go back to Oct 1 2005 and there is no sign of any oops in any 
of the syslog before these events.

My problem is deciding which way to go on this to debug the problem.  I 
am now running on 1x 256Mb stick at 1250MHz.  It seems the Kingston RAM 
won't work with the Samsung RAM.  I am not sure the Kingston RAM is 
working ok at all but can anyone translate the logs into something more 
meaningful?

Regards

Lesley






___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.