mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Nicholas Fechner <fechner@ponton-consulting.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Module bridge not loading in 2.6.13-rc6
Date: Tue, 16 Aug 2005 13:44:18 -0700	[thread overview]
Message-ID: <20050816134418.5d7b8791@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <43019C3D.4060705@ponton-consulting.de>

On Tue, 16 Aug 2005 09:56:45 +0200
Nicholas Fechner <fechner@ponton-consulting.de> wrote:

> Please CC to fechner@ponton-consulting.de, since I am not subscribed to
> linux-kernel. Thanks.
> 
> Hi,
> I tried the current -rc6 Release on one of our test machines. It is a
> mirror of our gateway, hence the iptable modules. It also runs OpenVPN
> using a bridge configuration. After the kernel build and reboot I tried
> to "modprobe bridge", resulting in:
> 
> FATAL: Error inserting bridge
> (/lib/modules/2.6.13-rc6/kernel/net/bridge/bridge.ko): Unknown symbol in
> module, or unknown parameter (see dmesg)
> 
>
> bridge: disagrees about version of symbol dev_set_mtu
> bridge: Unknown symbol dev_set_mtu
> bridge: disagrees about version of symbol dev_queue_xmit
> bridge: Unknown symbol dev_queue_xmit
> bridge: Unknown symbol br_handle_frame_hook

You rebuilt the kernel (or bridge module), but did not install the updated
modules.  The module versioning code checks that any module loaded was
built from the same source as the kernel itself. In your case the bridge
module does not correspond to the running kernel.  If you are doing
your own kernel builds, you need to do:
	make modules_install
	make install

      reply	other threads:[~2005-08-16 20:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16  7:56 Nicholas Fechner
2005-08-16 20:44 ` Stephen Hemminger [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=20050816134418.5d7b8791@dxpl.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=fechner@ponton-consulting.de \
    --cc=linux-kernel@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 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®