From owner-freebsd-bugs@FreeBSD.ORG  Mon Apr  5 14:15:14 2010
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C4A26106566C;
	Mon,  5 Apr 2010 14:15:14 +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 7A88E8FC1A;
	Mon,  5 Apr 2010 14:15:13 +0000 (UTC)
Received: by darkthrone.kvedulv.de (Postfix, from userid 666)
	id 8B1241CC75; Mon,  5 Apr 2010 16:15:08 +0200 (CEST)
Date: Mon, 5 Apr 2010 16:15:08 +0200
From: Michael Moll <kvedulv@kvedulv.de>
To: freebsd-bugs@freebsd.org
Message-ID: <20100405141508.GC7513@darkthrone.kvedulv.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: kib@freebsd.org
Subject: Re: amd64/135014: [padlock] Using padlock(4) in 8-current triggers
 "fpudna in kernel mode!" warnings
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2010 14:15:14 -0000

Hi,

the patch from
http://people.freebsd.org/~kib/misc/kern_fpu.2.patch
fixes this problem for me.

Regards
-- 
Michael Moll