From owner-freebsd-amd64@freebsd.org  Tue Jan 19 08:04:54 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C792AA88EC6
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Tue, 19 Jan 2016 08:04:54 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B83991E86
 for <freebsd-amd64@FreeBSD.org>; Tue, 19 Jan 2016 08:04:54 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0J84sW1048897
 for <freebsd-amd64@FreeBSD.org>; Tue, 19 Jan 2016 08:04:54 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 206370] amd64 fpu not fully initialized
Date: Tue, 19 Jan 2016 08:04:54 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: commit-hook@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-206370-6-ZQKRC9iWax@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-206370-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-206370-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 19 Jan 2016 12:42:39 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2016 08:04:54 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206370

--- Comment #1 from commit-hook@freebsd.org ---
A commit references this bug:

Author: kib
Date: Tue Jan 19 08:04:02 UTC 2016
New revision: 294311
URL: https://svnweb.freebsd.org/changeset/base/294311

Log:
  Clear whole XMM register file instead of only XMM0.  Also clear x87
  registers.  This brings amd64 on par with i386, providing consistent
  initial FPU state.

  Note that we do not clear any extended state, at least because kernel
  does not understand extended state structure and consequences of zero
  overwrite after fninit()/fpusave().

  Submitted by: joss.upton@yahoo.com
  PR:   206370
  MFC after:    2 weeks

Changes:
  head/sys/amd64/amd64/fpu.c

--=20
You are receiving this mail because:
You are on the CC list for the bug.=