Words by nate [Mon, Jan 27, 2003 at 04:47:34PM -0800]:
> Sudhakar said:
> > Hi,
> > I'd appreciate if someone can point me to a link or resource which a
> > detailed explanation on Oops analysis for Redhat Linux.
> 

man ksymoops

> trying to decode an oops won't do you much good unless you understand
> linux kernel internals. even less useful if you aren't a good
> programmer(which I am not).
> 
> Your best bet is to post the entire oops to a mailing list(such as this
> one), maybe someone has seen it before. or paste part of it into google
> and see what comes up.
> 

Oopses are usually unique.

" Reporting a kernel Oops is meaningless on its  own
  because  other people do not know what your kernel looks like,
  you need to feed the Oops text through ksymoops then send the
  ksymoops output as part of your bug report."

see the above.

> The most common oops' I've seen are due to bad memory. If your having

I've got a lot of them related to dead cpu fans. The cpu temperature got
to unthinkable levels and unpredictable Oopses occured.

Now that I speak about this, it has been a long time since the last
defunct fan. Good.

> trouble capturing the oops, configure your system for a serial console,
> and use a null modem cable connected to another machine with a terminal
> emulator which logs to a file, so you can get the oops.
> 

I've used the pen and paper technique once and also a digital camera :)

-- 
Jose Celestino | http://xpto.org/~japc/files/japc-pgpkey.asc
----------------------------------------------------------------
"Don't summarize. Don't abbreviate. Don't interpret." -- djb



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to