| Summary: | geode-aes: Module cannot be used in conjunction with strongswan. | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Michael Tremer <michael.tremer> |
| Component: | --- | Assignee: | Michael Tremer <michael.tremer> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | - Unknown - | ||
| Priority: | - Unknown - | CC: | arne.fitzenreiter, michael.tremer, stefan.schantl |
| Version: | 2 | ||
| Hardware: | unspecified | ||
| OS: | Unspecified | ||
> [ 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.
|
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)