All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Peter Jay Salzman <p@dirac.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Two oops reports
Date: Mon, 09 May 2005 13:37:00 -0400	[thread overview]
Message-ID: <1115660221.8156.2.camel@mindpipe> (raw)
In-Reply-To: <20050509172435.GA6826@dirac.org>

On Mon, 2005-05-09 at 13:24 -0400, Peter Jay Salzman wrote:
> I've never sent in an oops report before.  From oops-tracing.txt, man
> ksymoops and the ksymoops output, I need /proc/ksyms, but it appears that
> file has disappeared from the kernel.  However, judging by the actual text
> of the oops report, it appears that the object translation was performed
> automatically.  I'm seeing things that look like function names, so perhaps
> the man page, oops-tracing.txt, and ksymoops output are all out of date?

Yes, they are.  I finally posted a patch which corrects the docs, post
2.6.11.

Anyway these two traces appear to have nothing to do with one another.
Random Oopses like this usually indicate failing hardware.  Try memtest.

Lee


      reply	other threads:[~2005-05-09 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 17:24 Two oops reports Peter Jay Salzman
2005-05-09 17:37 ` Lee Revell [this message]

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=1115660221.8156.2.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p@dirac.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.