Bug 10123 - geode-aes: Module cannot be used in conjunction with strongswan.
Summary: geode-aes: Module cannot be used in conjunction with strongswan.
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - - Unknown -
Assignee: Michael Tremer
QA Contact:
Depends on:
Reported: 2012-05-07 21:53 UTC by Michael Tremer
Modified: 2014-05-10 17:21 UTC (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Michael Tremer 2012-05-07 21:53:39 UTC
As a lot of sources told me, the geode-aes crypto kernel module cannot be loaded when strongswan is started. There is a huge delay in starting up the service and the following message is shown on the kernel log:

> alg: hash: Test 1 failed for xcbc(geode-aes)
Comment 1 Michael Tremer 2014-01-29 15:47:29 UTC
> [ 1247.555478] geode-aes: GEODE AES engine enabled.
> [ 1247.556879] gpio-keys-polled gpio-keys-polled.1: unable to claim gpio 24, err=-517
> [ 1247.556916] platform gpio-keys-polled.1: Driver gpio-keys-polled requests probe deferral

With kernel "Linux ipfire 3.10.26-ipfire #1 SMP Tue Jan 14 10:24:30 GMT 2014 i586 i586 i386 GNU/Linux" from IPFire 2.15, pre-beta 1, the Geode AES module is working.

Tested with an ALIX board.