I agree, hardware issue with mobo, or proc (since north bridge memory
controllers are usually built in here now). Seems more like a south
bridge issue (where pci bus liives), but could be memory corrupting
things as well.
Remove any external pci card you can, including usb devices. I had a
western digital drive housing cause some very weird kernel issues when
plugged in even.
-mb
On 01/14/2014 11:59 AM, Matt Graham wrote:
> 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.
>
---------------------------------------------------
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
.%20%20Seems%20more%20like%20a%20south%20%0A>%20bridge%20issue%20(where%20pci%20bus%20liives),%20but%20could%20be%20memory%20corrupting%20%0A>%20things%20as%20well.%0A>%20%0A>%20Remove%20any%20external%20pci%20card%20you%20can,%20including%20usb%20devices.%20%20I%20had%20a%20%0A>%20western%20digital%20drive%20housing%20cause%20some%20very%20weird%20kernel%20issues%20when%20%0A>%20plugged%20in%20even.%0A>%20%0A>%20-mb%0A>%20%0A>%20%0A>%20On%2001/14/2014%2011:59%20AM,%20Matt%20Graham%20wrote:%0A>%20>%20On%202014-01-14%2011:26,%20joe@actionline.com%20wrote:%0A>%20>>%20I%20finally%20rebooted%20again,%20and%20saw%20a%20screen%20full%20of%20messages%20including%0A>%20>>%20%22unable%20to%20handle%20kernel%20paging%20request%22%0A>%20>>%20http://www.upquick.com/temp/z1.jpg%0A>%20>>%20http://www.upquick.com/temp/z2.jpg%0A>%20>>%20http://www.upquick.com/temp/z3.jpg%0A>%20>>%20http://www.upquick.com/temp/z4.jpg%0A>%20>>%0A>%20>>%20What%20in%20the%20world%20could%20the%20problem%20be%20and%20how%20can%20I%20resurrect%20my%20%0A>%20>>%20system?%0A>%20>>%20(PS:%20I'm%20writing%20this%20message%20from%20my%20laptop.%20Tried%20to%20ssh%20login%20to%20the%0A>%20>>%20failed%20system,%20but%20no%20joy.)%0A>%20>%0A>%20>%20An%20OOPS%20at%2033%20seconds%20and%20then%20another%20OOPS%20at%2052%20seconds,%20both%20in%20%0A>%20>%20kernel%20code%20that%20should%20be%20reasonably%20stable%20(network%20drivers%20followed%20%0A>%20>%20by%20nouveau)?%20%20I%20am%20not%20certain,%20but%20I%20think%20there%20might%20be%20a%20hardware%20%0A>%20>%20problem%20somewhere%20in%20this%20machine.%0A>%20>%0A>%20>%20You%20can%20attempt%20to%20diagnose%20the%20problem%20by%20booting%20from%20a%20rescue%20%0A>%20>%20system.%20%20If%20those%20things%20fail%20in%20a%20similar%20manner,%20it's%20almost%20%0A>%20>%20certainly%20a%20hardware%20problem.%20%20(If%20the%20rescue%20system%20works%20fine,%20then%20%0A>%20>%20your%20Mint%20install%20is%20borked,%20but%20that%20seems%20sort%20of%20unlikely.)%20%20Or%20if%20%0A>%20>%20a%20rescue%20system%20works%20fine%20except%20when%20you%20start%20up%20a%20GUI,%20it's%20a%20%0A>%20>%20problem%20with%20the%20graphics%20card.%20%20Or%20if%20it%20works%20fine%20until%20you%20try%20to%20%0A>%20>%20start%20DHCP,%20it's%20a%20problem%20with%20the%20NIC.%20The%20other%20thing%20to%20check%20is%20%0A>%20>%20the%20case%20and%20airflow--make%20sure%20there%20aren't%20any%20dust%20bunnies%20blocking%20%0A>%20>%20the%20fans%20or%20anything.%20%20If%20you%20suspect%20the%20RAM%20is%20the%20problem,%20the%20%0A>%20>%20memtest86%20option%20on%20many%20rescue%20systems%20will%20probably%20say%20something%20if%20%0A>%20>%20you%20had%20bad%20RAM.%0A>%20>%0A>%20>%20The%20last%202%20times%20I've%20had%20things%20like%20this%20happen%20to%20desktop%20systems,%20%0A>%20>%20it's%20been%20problems%20with%20the%20motherboard.%20%20This%20is%20annoying%20because%20the%20%0A>%20>%20motherboard%20is%20expensive%20and%20a%20pain%20to%20replace.%0A>%20>%0A>%20%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)
