On Wed, Jun 15, 2011 at 12:50:10PM +0200, Voty wrote: > Kernel 2.6.32-5-xen-686 running as DOM0 under XEN hypervisor-4.0 on > VIA C7 when padlock_aes is used, until I blaclisted padlock_aes and > padlock_sha in /etc/modules... kernel oops-ed when I try to use > cryptsetup to create and use encrypted block device. Sometimes > oops-ed, sometimes hard-freezed after few seconds of using crypto > block device.
Please show such an oops. The module seems to do something not allowed under the Xen hypervisor. > I have tried to "upgrade" to testing and use XEN hypervisor-4.1, but > the result unchanged. Please test the _kernel_ from unstable (2.6.39) and experimental (3.0-rcX). They don't need a new hypervisor. Bastian -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110615115806.ga23...@wavehammer.waldi.eu.org
