All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Cotte-Barrot <Christian.Cotte-Barrot@bull.net>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Some Modules fail w/ unresolved cpu_info__per_cpu
Date: Wed, 19 Feb 2003 11:55:54 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805871@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805176@msgid-missing>

"Lee, Jung-Ik" wrote:
> 
> On 2.5.39,
> it fails to insmod some modules that refers to "cpu_info__per_cpu".
> That global IS DEFINE_PER_CPU'd, DECLARE_PER_CPU'd and is in System.map but
> for some reason it fails to resolve.
> Have you guys seen this ?
> 
> thanks
> J.I.
> 

That's an old story but we met the "unresolved symbol cpu_info__per_cpu"
problem again with e100.o and e1000.o modules on a 2.4.45 release.
Looks like the EXPORT_SYMBOL macro has problem to generate the
checksum for symbols defined with *PER_CPU* macros.
The kernel exports the wrong cpu_info__per_cpu_R__ver_cpu_info__per_cpu
symbol where "__ver_cpu_info__per_cpu" should be a checksum ?
Found a cleaner patch than in the past, just replaced
    EXPORT_SYMBOL(cpu_info__per_cpu);
  with
    EXPORT_SYMBOL_NOVERS(cpu_info__per_cpu);
  in
    ./arch/ia64/kernel/ia64_ksyms.c

CCB.


      parent reply	other threads:[~2003-02-19 11:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17  1:08 [Linux-ia64] Some Modules fail w/ unresolved cpu_info__per_cpu Lee, Jung-Ik
2002-10-17  7:45 ` Christian Cotte-Barrot
2002-10-17  8:19 ` Keith Owens
2002-10-17 10:31 ` Christian Cotte-Barrot
2003-02-19 11:55 ` Christian Cotte-Barrot [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=marc-linux-ia64-105590709805871@msgid-missing \
    --to=christian.cotte-barrot@bull.net \
    --cc=linux-ia64@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 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.