Re: cryptsetup failed to access temporary keystore device

[Alex Hornung <ahornung@xxxxxxxxx>]

The issue, as far as I can tell, is with the usb stack. The
contigmalloc_map failures in dmesg just after creating the dm volume
probably come from somewhere there.

I'm not sure how to work around this, you could probably try on a
freshly rebooted system or without ehci.

Regards,
Alex


On 04/06/11 18:52, Pierre Abbat wrote:
> On Saturday 04 June 2011 06:37:28 Alex Hornung wrote:
>> It would be helpful if you could provide some more information,
>> specifically:
>>
>> a) dmesg (up to the moment when this happens)
>> b) kldstat
>> c) dmsetup ls
> 
> # dmsetup ls
> crypt   (255, 504430599)
> # kldstat
> Id Refs Address    Size     Name
>  1   17 0xc0100000 88a9d4   kernel
>  2    1 0xc098b000 26ce4    linux.ko
>  3    1 0xc09b2000 78d04    acpi.ko
>  4    1 0xc0a2b000 134cc    ahci.ko
>  5    1 0xc0a3f000 97cc     ehci.ko
>  6    2 0xc0a49000 b9f8     dm.ko
>  7    1 0xcc74d000 a000     linprocfs.ko
>  8    1 0xccf44000 9000     i915.ko
>  9    1 0xccf4d000 13000    drm.ko
> 10    1 0xcd260000 18000    dm_target_crypt.ko
> 11    1 0xd2e80000 12000    ext2fs.ko
> 
> dmesg is attached.
> 
> Pierre
>