LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Angelo Dell'Aera" <buffer@antifork.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.6-mm4 - unknown symbol __log_start_commit
Date: Thu, 20 May 2004 12:30:16 +0200 [thread overview]
Message-ID: <20040520123016.0bd36f95.buffer@antifork.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I saw it few minutes ago while compiling kernel 2.6.6-mm4.
root@mintaka:/usr/src/linux-2.6.6-mm4# depmod -ae -F System.map 2.6.6-mm4
WARNING: /lib/modules/2.6.6-mm4/kernel/fs/ext3/ext3.ko needs unknown symbol __log_start_commit
root@mintaka:~# modprobe ext3
FATAL: Error inserting ext3 (/lib/modules/2.6.6-mm4/kernel/fs/ext3/ext3.ko): Unknown symbol in module, or unknown parameter (see dmesg)
root@mintaka:~# dmesg | tail -n 1
ext3: Unknown symbol __log_start_commit
root@mintaka:~# lsmod | grep jbd
jbd 52760 0
root@mintaka:/proc# grep __log_start_commit /proc/kallsyms
dfcb9170 t __log_start_commit [jbd]
.config relevant section is reported below
#
# File systems
#
CONFIG_EXT2_FS=m
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=m
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
Note : this doesn't happen on kernel 2.6.6-mm3.
Regards.
- --
Angelo Dell'Aera 'buffer'
Antifork Research, Inc. http://buffer.antifork.org
PGP information in e-mail header
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFArIi4pONIzxnBXKIRAlJAAJ9gDRqciQtk8pdI3w6QKMDKi9XIKQCgufkZ
lJeiDgjRzROrQwfw2P43XtQ=
=tckk
-----END PGP SIGNATURE-----
reply other threads:[~2004-05-20 10:28 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=20040520123016.0bd36f95.buffer@antifork.org \
--to=buffer@antifork.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: 2.6.6-mm4 - unknown symbol __log_start_commit' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).