From: Lee Revell <rlrevell@joe-job.com>
To: Peter Van <plst@ws.sbcoxmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to debug an Oops on FC4 2.6 Kernel
Date: Tue, 04 Apr 2006 21:16:42 -0400 [thread overview]
Message-ID: <1144199803.8122.13.camel@mindpipe> (raw)
In-Reply-To: <009b01c65431$939c9100$2801010a@Dolphin>
On Thu, 2006-03-30 at 11:38 -0800, Peter Van wrote:
> /var/log/messages has an Oops log but I don't know how to use the
> Oops log to
> determine the cause of the problem. According to some posts,
> ksymoops can't be
> used
> on a 2.6 kernel.
Yes, and as you can see this Oops already has the symbols resolved in
it. So there's no need to run ksymoops at all - posting the Oops as you
did is fine.
If you don't get a resolution to your problem please open a kernel
bugzilla report.
Lee
next prev parent reply other threads:[~2006-04-05 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 19:38 How to debug an Oops on FC4 2.6 Kernel Peter Van
2006-04-05 1:16 ` Lee Revell [this message]
[not found] <5WbMU-6U1-67@gated-at.bofh.it>
2006-03-31 1:09 ` Robert Hancock
2006-03-31 1:35 ` Peter Van
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=1144199803.8122.13.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plst@ws.sbcoxmail.com \
/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