Hi,
Using ixp4xx_crypto hardware acceleration i have the panic below, only
when doing a ping MTU or any other packet MTU.
The basic setup is 802.1Q VLAN -- ixp4xx_eth -- IPSec Tunnel
a ping -s 1800 to a host on the other side of the tunnel will
produce the kernel panic..
Doing
The latest thing i found is kernel BUG at lib/scatterlist.c:26!
ping -s 1800 host in a IPSec tunnel. Setup is 802.1Q VLAN --
ixp4xx_eth -- IPSec Tunnel
trace with some debug printk's i added.printk(%s:%d
values,__func__, __LINE__);
[42949542.17] esp_output:142
Christian Hohnstaedt wrote:
On Tue, Feb 24, 2009 at 02:19:54PM +0100, Karl Hiramoto wrote:
The latest thing i found is kernel BUG at lib/scatterlist.c:26!
ping -s 1800 host in a IPSec tunnel. Setup is 802.1Q VLAN --
ixp4xx_eth -- IPSec Tunnel
trace with some debug printk's
Herbert Xu wrote:
Russell King - ARM Linux li...@arm.linux.org.uk wrote:
We can't merge this until _all_ of ARM has been fixed for walking
scatterlist chains.
Right, this is definitely not the way to fix this bug. Because
even if ARM completely supported chaining, you still have to
timenhhf wrote:
hi,
i read your mail list on net about ixp4xx_crypto panic.
i'm using linux kernel 2.6.28.9, but i can't make the IXP425 NPEs work
all right.
the steps i've done as followed:
(1) download ixp4xx-microcode_2.4.orig.tar.gz through the URL:
correctly.
--
--
Karl Hiramoto http://karl.hiramoto.org/
--
To unsubscribe from this list: send the line unsubscribe linux-crypto in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Geert,
Was wondering if there are any patches for pcomp lzma. it it just a matter of
adding crypto/lzma to make the calls to lib/decompress_unlzma.c ?
I just started looking at this, my end goal is to use your pcomp patch for
squashfs and get lzma squahsfs.
Thanks,
karl.
--
To
[c004bc7c] (kthread+0x58/0x90)
r4:c2e38000
[c004bc24] (kthread+0x0/0x90) from [c0039ed4] (do_exit+0x0/0x6d0)
r6: r5: r4:
Note this is somewhat hard to reproduce, but can be reproduced under memory
pressure when you first initialize ixp4xx_crypto.
Signed-off-by: Karl
Hi,
I'm using the HW crypto drivers at drivers/crypto/atmel-{sha,aes}.c
When I startup a ipsec tunnel (strongswan) /proc/crypto shows:
authenc(hmac(sha1-generic),atmel-cbc-aes)
I can tell the SHA hardware is not being used now as sha_transform is
at the top of the list with oprofile, and
