public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Willy Tarreau <willy@w.ods.org>
Cc: George Nychis <gnychis@cmu.edu>, linux-kernel@vger.kernel.org
Subject: Re: cannot load *any* modules with 2.4 kernel
Date: Mon, 22 May 2006 11:53:29 +1000	[thread overview]
Message-ID: <6366.1148262809@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 21 May 2006 10:40:55 +0200." <20060521084055.GA14593@w.ods.org>

Willy Tarreau (on Sun, 21 May 2006 10:40:55 +0200) wrote:
>On Sun, May 21, 2006 at 03:00:39AM -0400, George Nychis wrote:
>> Grepping 2 or 3:
>> [root@emu-5 net]# grep enable_irq /proc/ksyms
>> c010a5e0 enable_irq_R__ver_enable_irq
>> c0343610 matroxfb_enable_irq_R__ver_matroxfb_enable_irq
>> [root@emu-5 net]# grep printk /proc/ksyms
>> c011aee0 printk_R__ver_printk
>> [root@emu-5 net]# grep kmalloc /proc/ksyms
>> c0132c60 kmalloc_R__ver_kmalloc
>> c03c07e0 sock_kmalloc_R__ver_sock_kmalloc
>                        ^^^^^^^^^^^^^^^^^^^
>
>There should be and 'R' followed by 8 hex digits here. I remember I
>already came across this once, but unfortunately I don't remember how
>nor how I fixed it.

Broken kernel build system in 2.4.  It does not always build the module
version data correctly.  Save your 2.4 .config, make mrproper
(critical), restore your .config then
  make oldconfig
  make dep
  make bzImage modules
  make modules_install
  install


  reply	other threads:[~2006-05-22  1:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-20 16:10 cannot load *any* modules with 2.4 kernel George Nychis
2006-05-20 16:25 ` Willy Tarreau
2006-05-21  0:05   ` George Nychis
2006-05-21  5:48     ` Willy Tarreau
2006-05-21  7:00       ` George Nychis
2006-05-21  8:40         ` Willy Tarreau
2006-05-22  1:53           ` Keith Owens [this message]
2006-05-22 13:21           ` George Nychis
2006-05-21  7:32     ` Nick Warne
2006-05-21 14:43       ` George Nychis
2006-05-21 15:34         ` Nick Warne

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=6366.1148262809@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=gnychis@cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@w.ods.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox