From owner-freebsd-current@FreeBSD.ORG  Sun May 17 17:34:05 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7117F106566B
	for <freebsd-current@freebsd.org>; Sun, 17 May 2009 17:34:05 +0000 (UTC)
	(envelope-from mmoll@darkthrone.kvedulv.de)
Received: from darkthrone.kvedulv.de (darkthrone.kvedulv.de
	[IPv6:2001:1578:400:101::2])
	by mx1.freebsd.org (Postfix) with ESMTP id DCA278FC19
	for <freebsd-current@freebsd.org>; Sun, 17 May 2009 17:34:04 +0000 (UTC)
	(envelope-from mmoll@darkthrone.kvedulv.de)
Received: by darkthrone.kvedulv.de (Postfix, from userid 666)
	id 8852C1CC31; Sun, 17 May 2009 19:34:02 +0200 (CEST)
Date: Sun, 17 May 2009 19:34:02 +0200
From: Michael Moll <kvedulv@kvedulv.de>
To: freebsd-current@freebsd.org
Message-ID: <20090517173402.GI89114@darkthrone.kvedulv.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.19 (2009-01-05)
Subject: padlock on amd64 does not work
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 17 May 2009 17:34:05 -0000

Hi All,

after migrating from i386 to amd64 on a VIA Nano, padlock is not working
anymore. I use it to encrypt disks via GELI, this works fine when done
in software:

# /etc/rc.d/geli start
Configuring Disk Encryption for ad4s1f.
Enter passphrase:
GEOM_ELI: Device ad4s1f.eli created.
GEOM_ELI: Encryption: AES-CBC 256
GEOM_ELI:     Crypto: software

Now the same with the padlock module loaded:

# kldload padlock
padlock0: <AES-CBC,SHA1,SHA256> on motherboard
# 
# /etc/rc.d/geli start
Configuring Disk Encryption for ad4s1f.
Enter passphrase:
GEOM_ELI: Device ad4s1f.eli created.
GEOM_ELI: Encryption: AES-CBC 256
GEOM_ELI:     Crypto: hardware
fpudna in kernel mode!
fpudna in kernel mode!
fpudna in kernel mode!

This message repeats forever. Any ideas on this one?

Kind Regards
-- 
Michael Moll