[PLUG] Re: RAM Upgrade problems

[Kevin Falcone <kevinfal@seas.upenn.edu>]

>>>>> "GL" == Greg Lopp <lopp@earthlink.net> writes:

  [snip explanation of gpf]

  GL> Is OOPS an acronym, or is it really just "oops" like "that's not
  GL> supposed to happen"?

in the linux sense, oops == gpf.  As in oops, oh f#ck.  Some are
recoverable, some aren't.  I used to get them for my pcmcia card, they
would log and the kernel would self correct and move on.  However,
sometimes the kernel can't self correct and it is stuck just printing
the current state and dying/hanging depending on what died.

  GL> I read /usr/src/linux/Documentation/oops-tracing.txt, so I've
  GL> added that to my list of things to try after work....

If you are familiar with NT, it is like a blue screen of death in that
you get a hex dump of the current state of the machine.  Running the
dump through ksymoops translates it into symbols which tell you what
died and where.  You may have to enable SysRQ support if it hangs,
because with that you can force a reboot or force an oops.

There is a section in the linux-kernel faq on how to generate an oops
and how to turn it into something useful.  /usr/src/linux/scripts/ksymoops

However, if you aren't making it past the lilo prompt, and at least
getting the kernel to try and boot, then this is moot as it is almost
certainly a RAM/BIOS/Motherboard interaction issue (And those are real fun)

-kevin

PS: I can't post to clug, so I'm dropping your CC

-- 
"ATM the ATM is off the ATM, and ATM is as b0rken as usual" 
	--Matt McLeod


______________________________________________________________________
Philadelphia Linux Users Group       -      http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion  -  http://lists.phillylinux.org/mail/listinfo/plug