Dirk Thierbach wrote:
> On Tue, Mar 24, 2009 at 10:44:30AM +0100, Milan Broz wrote:
> strace says it hangs on "iotcl(3, DM_TABLE_LOAD".
>
> This is on a Samsung NC20 with VIA VX880 chipset. Is it possible that
> some sort of hardware crypto support ("VIA Padlock" looks like that)
> is causing the problem? Can I disable that in the kernel without
> recompiling it? (Compiling my own kernel is next on the TODO list,
> but it would be nice if I could actually use my home volume before that,
> and it would also make testing faster).
This seems like problem with crypto module, possibly for your hw (padlock).
You can probably try to disable padlock by unloading the module
an loading generic ones (like sha256_generic, aes_i586 etc, depends on arch
and mode)
(or simply temporarily rename the padlock module or blaclist it and reboot, so
the system will not initialize padlock and use another aes implementation.
Of course modules must be compiled there.)
(Also try upgrade to vanilla kernel 2.6.28.9 too, there is a bugfix
for async crypto in dm-crypt.)
Milan
--
mbroz@xxxxxxxxxx
---------------------------------------------------------------------
dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx
