public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: cranium2003 <cranium2003@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: how to debug and capture Oops mesage?
Date: Thu, 6 Jan 2005 00:33:39 -0800 (PST)	[thread overview]
Message-ID: <20050106083340.71293.qmail@web41404.mail.yahoo.com> (raw)

Hello,
             I have two machines with RedHat linux 9
with serially connected to each other. While doing
some kernel programming i am getting frequently Oops
messages. I am learning network stack. How can i
capture those oops message and which utility can help
me to solve oops problem. I heard about lkcd which is
on lkcd.sourceforge.net. Can it be suitable utility to
check kernel crash dump. I have yet not used it and
require advice from kernel developers.
Please kindly help me.
Thanks in advance.
regards,
cranium


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250

             reply	other threads:[~2005-01-06  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06  8:33 cranium2003 [this message]
2005-01-06  7:54 ` how to debug and capture Oops mesage? Gerald Stuhrberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050106083340.71293.qmail@web41404.mail.yahoo.com \
    --to=cranium2003@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox