From: a.othieno@bluewin.ch (Arthur Othieno)
To: Matt LaPlante <laplam@rpi.edu>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: Unknown symbol in crc32c in 2.6.13.1
Date: Tue, 20 Sep 2005 20:03:41 -0400 [thread overview]
Message-ID: <20050921000341.GA2527@mars> (raw)
In-Reply-To: <200509200507.j8K57kY6006302@ms-smtp-03-eri0.southeast.rr.com>
On Tue, Sep 20, 2005 at 01:07:42AM -0400, Matt LaPlante wrote:
> Hi All,
> I see this error repeatedly. Running Debian latest stable branch w/
> custom 2.6.13.1 kernel. I've got the racoon package installed and I'm
> running IPSec between two such gateways. On both ends, when I start Racoon
> for my IPSec link I always get the following error:
>
> ###################################################
> firewall:~# /etc/init.d/racoon restart
> Stopping IKE (ISAKMP/Oakley) server: racoon.
> Flushing SAD and SPD...
> SAD and SPD flushed.
> Unloading IPSEC/crypto modules...
> IPSEC/crypto modules unloaded.
> Loading IPSEC/crypto modules...
>
> insmod: error inserting
> '/lib/modules/2.6.13.1-firewall/kernel/crypto/crc32c.ko': -1 Unknown symbol
> in module
>
>
> IPSEC/crypto modules loaded.
> Starting IKE (ISAKMP/Oakley) server: racoon.
> Flushing SAD and SPD...
> SAD and SPD flushed.
> Loading SAD and SPD...
> SAD and SPD loaded.
> Configuring racoon...done.
> ###################################################
>
> It doesn't seem to be fatal, but I figured I'd report it since it seems to
> be continuous. Syslog gives only the following:
>
> Sep 20 00:58:53 localhost kernel: crc32c: Unknown symbol crc32c_le
Hmmm.
> I hope this problem isn't considered too trivial to report...sorry if I'm
> wasting your time with it.
Could you please post a copy of your .config and /etc/init.d/racoon.
Thanks.
Arthur
next prev parent reply other threads:[~2005-09-21 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 5:07 Unknown symbol in crc32c in 2.6.13.1 Matt LaPlante
2005-09-21 0:03 ` Arthur Othieno [this message]
2005-09-21 1:21 ` Matt LaPlante
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=20050921000341.GA2527@mars \
--to=a.othieno@bluewin.ch \
--cc=laplam@rpi.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.