>From what you've told us there is no way to diagnose the problem. When the kernel freezes you have to look at the logs to tell what is happening.
If you want a better answer log in as root, use an editor to look at the file /var/log/dmesg, look for the time stamp that is close to the time your computer locked up. There should be something that is out of the ordinary. You may see the text "kernel panic", "Oops", signal 11 or something like that. BTW signal 11 comes up when the RAM has delivered an exception to the system meaning either your motherboard needs cleaning or your RAM has an error somewhere. Your processor or your RAM can overheat if it the dust gets a chance to build up on it. I have had this happen on older computers when I get lazy. Often putting the kernel message into google will give you some indication of what is wrong. If you can't find anything, then wait until the system locks up again and the first thing after you boot look at the file for the last thing the system put in the log before you boot. That will have the information that will tell you what is happening. Alternately, if you can't isolate what is happening then arrange with someone to examine the file for you. I'm sure some gracious person will help you with this. > Using Debian Squeeze. > I've had a kernel Failure the last couple of days. What do I need to do > about this. How would I fix this or change the Kernel? I can still boot > up, but everytime it gives me the message and it froze on me yesterday. > > Thanks for help > > _______________________________________________ > clug-talk mailing list > clug-talk@clug.ca > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying > _______________________________________________ clug-talk mailing list clug-talk@clug.ca http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
