From: Keith Owens <kaos@ocs.com.au>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-pre9: oopses on PPC
Date: Mon, 07 Oct 2002 00:27:30 +1000 [thread overview]
Message-ID: <31034.1033914450@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 05 Oct 2002 19:14:28 +0300." <Pine.GSO.4.44.0210051905030.20309-100000@math.ut.ee>
On Sat, 5 Oct 2002 19:14:28 +0300 (EEST),
Meelis Roos <mroos@linux.ee> wrote:
>Looks like PPC oops output does not contain code, so ksymoops complains.
>No idea though why it complains about sunrpc symbols.
Thanks to Meelis Roos for diagnostics off list.
>Warning (compare_maps): mismatch on symbol xchg_u32 , ksyms_base says c000b88c, System.map says c0006424.
Two functions called xchg_u32, one static, one global. ksyms contains
c000b88c, System.map contains both c0006424 (arch/ppc/kernel/misc.S,
global) and c000b88c (include/asm-ppc/system.h, static). Just to
confuse things even more, it is the static version that is exported to
modules.
Kernel coding error, having two functions with the same name but
different scope is just asking for trouble. Fix the ppc code.
>Warning (compare_maps): mismatch on symbol nlmsvc_ops
>Warning (compare_maps): mismatch on symbol nfs_debug
>Warning (compare_maps): mismatch on symbol nfsd_debug
>Warning (compare_maps): mismatch on symbol nlm_debug
>Warning (compare_maps): mismatch on symbol rpc_debug
>Warning (compare_maps): mismatch on symbol packet_socks_nr
>Warning (compare_maps): mismatch on symbol usb_devfs_handle
Exported symbols that are in sbss, rather than bss. Neither modutils
nor ksymoops handle sbss, they only handle bss. I will do new versions
of both packages to handle sbss.
prev parent reply other threads:[~2002-10-06 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 16:14 Meelis Roos
2002-10-06 14:27 ` 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=31034.1033914450@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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
all inboxes | Powered by JetHome®