All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Zed Pobre <zed@resonant.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: invalid operand 0000 (2.4.19-pre2, P2-266 SMP)
Date: Fri, 29 Mar 2002 20:10:30 +1100	[thread overview]
Message-ID: <29376.1017393030@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 29 Mar 2002 02:03:05 MDT." <20020329080305.GA16625@resonant.org>

On Fri, 29 Mar 2002 02:03:05 -0600, 
Zed Pobre <zed@resonant.org> wrote:
>[5.] ksymoops was run on the same machine with no options set shortly
>     after the crash, but it still issued warnings.  I'm not sure why, or
>     if I need to do something different.
>
>ksymoops 2.4.3 on i686 2.4.19-pre2.  Options used
>     -V (default)
>     -k /proc/ksyms (default)
>     -l /proc/modules (default)
>     -o /lib/modules/2.4.19-pre2/ (default)
>     -m /boot/System.map-2.4.19-pre2 (default)
>
>Warning: You did not tell me where to find symbol information.  I will
>assume that the log matches the kernel and modules that are running
>right now and I'll use the default options above for symbol resolution.
>If the current kernel and/or modules do not match the log, you can get
>more accurate output by telling me the kernel version and where to find
>map, modules, ksyms etc.  ksymoops -h explains the options.

Standard warning that you are using the default values which may or may
not be sensible for your machine.

>Warning (compare_maps): mismatch on symbol partition_name  , ksyms_base say=
>s c0239040, System.map says c015a890.  Ignoring ksyms_base entry

Kernel has two symbols called partition_name.  Corrected in 2.4.19-pre4.


      reply	other threads:[~2002-03-29  9:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-29  8:03 PROBLEM: invalid operand 0000 (2.4.19-pre2, P2-266 SMP) Zed Pobre
2002-03-29  9:10 ` Keith Owens [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=29376.1017393030@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zed@resonant.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.