Re: alg: cipher: Test 1 failed on encryption for aes-asm

2009-01-02 Thread Herbert Xu
On Fri, Jan 02, 2009 at 10:24:27PM +0100, Sebastian Andrzej Siewior wrote: > > No matter what you pick as your final solution, should I send a > 's/module_init/subsys_initcall/' patch for cryptomgr & algapi? cryptomgr already uses subsys_initcall and algapi doesn't need it yet because it only reg

Re: alg: cipher: Test 1 failed on encryption for aes-asm

2009-01-02 Thread Sebastian Andrzej Siewior
* Herbert Xu | 2008-12-24 15:48:51 [+1100]: >On Wed, Dec 24, 2008 at 09:43:41AM +0800, Huang Ying wrote: >> >> I think that is not easy. Not all architecture follow the same directory >> structure arch//crypto. And arch/x86/crypto is used by user mode >> linux too. > >Right, relying on link order

Re: alg: cipher: Test 1 failed on encryption for aes-asm

2008-12-23 Thread Herbert Xu
On Wed, Dec 24, 2008 at 09:43:41AM +0800, Huang Ying wrote: > > I think that is not easy. Not all architecture follow the same directory > structure arch//crypto. And arch/x86/crypto is used by user mode > linux too. Right, relying on link order is hazardous. However, since the table isn't that l

Re: alg: cipher: Test 1 failed on encryption for aes-asm

2008-12-23 Thread Huang Ying
On Tue, 2008-12-23 at 21:01 +0800, Sebastian Andrzej Siewior wrote: > * Huang Ying | 2008-12-23 16:49:26 [+0800]: > > >If aes_x86_64 and aes_generic are compiled as builtin, the > >initialization order is undetermined. That is, aes_x86_64 may be > >initilized before aes_generic is initilized, but

Re: alg: cipher: Test 1 failed on encryption for aes-asm

2008-12-23 Thread Sebastian Andrzej Siewior
* Huang Ying | 2008-12-23 16:49:26 [+0800]: >If aes_x86_64 and aes_generic are compiled as builtin, the >initialization order is undetermined. That is, aes_x86_64 may be >initilized before aes_generic is initilized, but aes_x86_64 depends on >tables generated in aes_generic initialization code. ae

Re: alg: cipher: Test 1 failed on encryption for aes-asm

2008-12-23 Thread Huang Ying
aes_x86_64 depends on tables generated in aes_generic initialization code. aes_x86_64 can not work before aes_generic is initialized, so that cause register time testing failed with following error message: [0.657034] alg: cipher: Test 1 failed on encryption for aes-asm [0.65711

Re: alg: cipher: Test 1 failed on encryption for aes-asm

2008-12-19 Thread Herbert Xu
On Fri, Dec 19, 2008 at 08:26:03PM +, Christoph Hellwig wrote: > On my new thinkpad with a Intel Core2 Duo T9600 I reproducibly get > this message during boot: > > [ 0.657034] alg: cipher: Test 1 failed on encryption for aes-asm > [0.657111] : 00 01 02 03 04 05

Re: alg: cipher: Test 1 failed on encryption for aes-asm

2008-12-19 Thread Christoph Hellwig
On Sat, Dec 20, 2008 at 07:55:10AM +1100, Herbert Xu wrote: > You forgot to list the kernel version :) 2.6.28-rc9, aka Linus' git as of today. -- 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 ht

Re: alg: cipher: Test 1 failed on encryption for aes-asm

2008-12-19 Thread Herbert Xu
Christoph Hellwig wrote: > On my new thinkpad with a Intel Core2 Duo T9600 I reproducibly get > this message during boot: > > [ 0.657034] alg: cipher: Test 1 failed on encryption for aes-asm > [0.657111] : 00 01 02 03 04 05 06 07 08 08 08 08 08 08 08 08 > >

alg: cipher: Test 1 failed on encryption for aes-asm

2008-12-19 Thread Christoph Hellwig
On my new thinkpad with a Intel Core2 Duo T9600 I reproducibly get this message during boot: [0.657034] alg: cipher: Test 1 failed on encryption for aes-asm [0.657111] : 00 01 02 03 04 05 06 07 08 08 08 08 08 08 08 08 I'd assume it's not a hardware but, so my the ass