From: gshan <gshan@alcatel-lucent.com>
To: linux-kernel@vger.kernel.org
Subject: ipv6: disagrees about version of symbol struct_module
Date: Tue, 04 Nov 2008 13:32:07 +0800 [thread overview]
Message-ID: <490FDE57.3070104@alcatel-lucent.com> (raw)
I'm using 2.6.21 kernel. When it boots from target board, it always
complained that "ipv6: disagrees about version of symbol struct_module".
It seems the modules on target didn't matches the running kernel. I
probably need to compile all modules together with the kernel and copy
them to target board. However, I'm not sure there has any way to change
.config to resolve such kind of problems?
INIT: version 2.86 booting
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...done.
Activating swap...done.
Remounting root filesystem...EXT3 FS on hdc5, internal journal
done.
/sbin/hotplug is not symlinked to /sbin/uSDE/uSDE-hotplug!
Calculating module dependencies
Loading modules:
Checking all file systems: fsck
fsck 1.40 (29-Jun-2007)
Mounting local filesystems: mount nothing was mounted
Checking SELinux contexts: selinux-basics.
Setting up networking ....
Starting network interfaces: done.
Starting hotplug subsystem:
pci
pci [success]
usb
usb [success]
isapnp
isapnp [success]
ide
ide [success]
input
input [success]
scsi
scsi [success]
done.
Starting portmap daemon....
Cleaning: /tmp /var/lock /var/run find: paths must precede expression
Usage: find [-H] [-L] [-P] [path...] [expression]
done.
Setting pseudo-terminal access permissions...done.
Updating /etc/motd...done.
INIT: Entering runlevel: 3
Starting irqbalance.
Starting system log daemon: syslogdipv6: disagrees about version of
symbol struct_module
klogd.
Starting auditd:
Starting NFS common utilities: statd.
Starting internet superserver: inetd.
Starting OpenBSD Secure Shell server: sshdipv6: disagrees about version
of symbol struct_module
ipv6: disagrees about version of symbol struct_module
.
reply other threads:[~2008-11-04 5:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=490FDE57.3070104@alcatel-lucent.com \
--to=gshan@alcatel-lucent.com \
--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