On 2014-01-14 11:26,
joe@actionline.com wrote:
> I finally rebooted again, and saw a screen full of messages including
> "unable to handle kernel paging request"
> http://www.upquick.com/temp/z1.jpg
> http://www.upquick.com/temp/z2.jpg
> http://www.upquick.com/temp/z3.jpg
> http://www.upquick.com/temp/z4.jpg
>
> What in the world could the problem be and how can I resurrect my
> system?
> (PS: I'm writing this message from my laptop. Tried to ssh login to
> the
> failed system, but no joy.)
An OOPS at 33 seconds and then another OOPS at 52 seconds, both in
kernel code that should be reasonably stable (network drivers followed
by nouveau)? I am not certain, but I think there might be a hardware
problem somewhere in this machine.
You can attempt to diagnose the problem by booting from a rescue
system. If those things fail in a similar manner, it's almost certainly
a hardware problem. (If the rescue system works fine, then your Mint
install is borked, but that seems sort of unlikely.) Or if a rescue
system works fine except when you start up a GUI, it's a problem with
the graphics card. Or if it works fine until you try to start DHCP,
it's a problem with the NIC. The other thing to check is the case and
airflow--make sure there aren't any dust bunnies blocking the fans or
anything. If you suspect the RAM is the problem, the memtest86 option
on many rescue systems will probably say something if you had bad RAM.
The last 2 times I've had things like this happen to desktop systems,
it's been problems with the motherboard. This is annoying because the
motherboard is expensive and a pain to replace.
--
Crow202 Blog:
http://crow202.org/wordpress
There is no Darkness in Eternity
But only Light too dim for us to see.
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
%0A>%20%0A>%20An%20OOPS%20at%2033%20seconds%20and%20then%20another%20OOPS%20at%2052%20seconds,%20both%20in%20%0A>%20kernel%20code%20that%20should%20be%20reasonably%20stable%20(network%20drivers%20followed%20%0A>%20by%20nouveau)?%20%20I%20am%20not%20certain,%20but%20I%20think%20there%20might%20be%20a%20hardware%20%0A>%20problem%20somewhere%20in%20this%20machine.%0A>%20%0A>%20You%20can%20attempt%20to%20diagnose%20the%20problem%20by%20booting%20from%20a%20rescue%20%0A>%20system.%20%20If%20those%20things%20fail%20in%20a%20similar%20manner,%20it's%20almost%20certainly%20%0A>%20a%20hardware%20problem.%20%20(If%20the%20rescue%20system%20works%20fine,%20then%20your%20Mint%20%0A>%20install%20is%20borked,%20but%20that%20seems%20sort%20of%20unlikely.)%20%20Or%20if%20a%20rescue%20%0A>%20system%20works%20fine%20except%20when%20you%20start%20up%20a%20GUI,%20it's%20a%20problem%20with%20%0A>%20the%20graphics%20card.%20%20Or%20if%20it%20works%20fine%20until%20you%20try%20to%20start%20DHCP,%20%0A>%20it's%20a%20problem%20with%20the%20NIC.%20%20The%20other%20thing%20to%20check%20is%20the%20case%20and%20%0A>%20airflow--make%20sure%20there%20aren't%20any%20dust%20bunnies%20blocking%20the%20fans%20or%20%0A>%20anything.%20%20If%20you%20suspect%20the%20RAM%20is%20the%20problem,%20the%20memtest86%20option%20%0A>%20on%20many%20rescue%20systems%20will%20probably%20say%20something%20if%20you%20had%20bad%20RAM.%0A>%20%0A>%20The%20last%202%20times%20I've%20had%20things%20like%20this%20happen%20to%20desktop%20systems,%20%0A>%20it's%20been%20problems%20with%20the%20motherboard.%20%20This%20is%20annoying%20because%20the%20%0A>%20motherboard%20is%20expensive%20and%20a%20pain%20to%20replace.%0A>%20%0A>%20--%20%0A>%20Crow202%20Blog:%20http://crow202.org/wordpress%0A>%20There%20is%20no%20Darkness%20in%20Eternity%0A>%20But%20only%20Light%20too%20dim%20for%20us%20to%20see.%0A>%20---------------------------------------------------%0A>%20PLUG-discuss%20mailing%20list%20-%20PLUG-discuss@lists.phxlinux.org%0A>%20To%20subscribe,%20unsubscribe,%20or%20to%20change%20your%20mail%20settings:%0A>%20http://lists.phxlinux.org/mailman/listinfo/plug-discuss%0A>%20%0A>%20 "Reply to this message")
(text/plain)
