public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: dann frazier <dannf@hp.com>
To: Peter Chubb <peterc@gelato.unsw.edu.au>
Cc: linux-ia64@vger.kernel.org, tony.luck@intel.com,
	dmosberger@gmail.com, linux-kernel@vger.kernel.org
Subject: RE: ip_contrack refuses to load if built UP as a module on IA64
Date: Thu, 22 Sep 2005 22:04:59 +0000	[thread overview]
Message-ID: <1127426700.25159.63.camel@krebs.dannf> (raw)
In-Reply-To: <17174.35525.283392.703723@berry.gelato.unsw.EDU.AU>

On Thu, 2005-09-01 at 14:59 +1000, Peter Chubb wrote:
> 
> This patch makes UP and SMP do the same thing as far as module per-cpu
> data go.
> 
> Unfortunately it affects core code.

It causes 2.6.13/x86 to fail to link:
kernel/built-in.o: In function `load_module':
: undefined reference to `percpu_modcopy'
make: *** [.tmp_vmlinux1] Error 1

fyi, this is a problem we're seeing in the Debian UP packages:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug25070


  reply	other threads:[~2005-09-22 22:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29  2:41 ip_contrack module refuses to load Peter Chubb
2005-08-29  4:09 ` Luck, Tony
2005-08-29  7:29 ` Peter Chubb
2005-08-30  1:35 ` Peter Chubb
2005-08-30 16:17 ` Luck, Tony
2005-08-30 18:38 ` david mosberger
2005-08-30 19:22 ` Luck, Tony
2005-08-30 19:29 ` david mosberger
2005-08-30 21:52 ` Peter Chubb
2005-08-30 22:01 ` david mosberger
2005-09-01  4:59   ` ip_contrack refuses to load if built UP as a module on IA64 Peter Chubb
2005-09-22 22:04     ` dann frazier [this message]
2005-12-19 21:07       ` Luck, Tony
2006-01-10 21:21         ` dann frazier
2006-01-22 19:31           ` dann frazier
2005-09-02  3:37 ` ip_contrack module refuses to load Herbert Poetzl
2005-09-02  3:45 ` Luck, Tony

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=1127426700.25159.63.camel@krebs.dannf \
    --to=dannf@hp.com \
    --cc=dmosberger@gmail.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterc@gelato.unsw.edu.au \
    --cc=tony.luck@intel.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