From owner-freebsd-stable@FreeBSD.ORG Sat Mar 17 20:02:08 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D1545106564A; Sat, 17 Mar 2012 20:02:08 +0000 (UTC) (envelope-from ryao@cs.stonybrook.edu) Received: from edge2.cs.stonybrook.edu (edge2.cs.stonybrook.edu [130.245.9.211]) by mx1.freebsd.org (Postfix) with ESMTP id 751968FC18; Sat, 17 Mar 2012 20:02:08 +0000 (UTC) Received: from HUBCAS1.cs.stonybrook.edu (130.245.9.206) by edge2.cs.stonybrook.edu (130.245.9.211) with Microsoft SMTP Server (TLS) id 14.1.355.2; Sat, 17 Mar 2012 16:02:05 -0400 Received: from [192.168.1.2] (72.89.250.133) by hubcas1.cs.stonybrook.edu (130.245.9.212) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 17 Mar 2012 16:02:06 -0400 Message-ID: <4F64ED4F.1020803@cs.stonybrook.edu> Date: Sat, 17 Mar 2012 16:00:15 -0400 From: Richard Yao User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120301 Thunderbird/10.0.1 MIME-Version: 1.0 To: References: <4F64C50F.70409@cs.stonybrook.edu> <4F64C57F.6040403@cs.stonybrook.edu> <4F64E856.3040303@cs.stonybrook.edu> In-Reply-To: <4F64E856.3040303@cs.stonybrook.edu> X-Enigmail-Version: 1.3.5 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC909810FF4A687C8F386C0B3" X-Originating-IP: [72.89.250.133] Cc: Alan Cox , freebsd-stable@freebsd.org Subject: Re: AMD Erratum 383 crashes FreeBSD 9-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2012 20:02:08 -0000 --------------enigC909810FF4A687C8F386C0B3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Alan, thanks for the information. This is a definitely libvirtd bug. Passing '-cpu host' fixes the problem. I replaced libvirtd with Gentoo's kvm-tools, which makes it easy to specify this, so problem solved. I would send a report to the libvirt developers, but I have encountered more problems in libvirt than I have time to describe, so that will not happen right away. On 03/17/12 15:39, Richard Yao wrote: > On 03/17/12 15:21, Alan Cox wrote: >> When the FreeBSD kernel detects that it is running on an affected >> processor, it automatically enables the recommended workaround. Howev= er, >> because you are running within a virtual machine, the automatic detect= ion >> may not be working. Alternatively, you may be using a newer processor= >> revision that still suffers from the bug, but the kernel doesn't enabl= e the >> workaround for. Can you tell us how the FreeBSD guest sees the underl= ying >> processor, e.g., the first few lines of dmesg from the guest? >> >> Alan >> >=20 > I am currently passing "-cpu > Opteron_G3,+3dnowext,+3dnow,+3dnowprefetch,+cmp_legacy" to KVM at > libvirtd's suggestion. I assume this is why the workaround is not being= > triggered. >=20 > # dmesg > Copyright (c) 1992-2012 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 199= 4 > The Regents of the University of California. All rights reserve= d. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.0-RELEASE #0: Sun Jan 15 22:48:55 UTC 2012 > root@zfsguru:/usr/obj/usr/src/sys/OFED amd64 > module_register: module pci/mps already exists! > Module pci/mps failed to register: 17 > CPU: AMD Opteron 23xx (Gen 3 Class Opteron) (3210.85-MHz K8-class CPU) > Origin =3D "AuthenticAMD" Id =3D 0xf61 Family =3D f Model =3D 6 S= tepping =3D 1 >=20 > Features=3D0x783fbfd > Features2=3D0x80802001 > AMD Features=3D0xe0100800 > AMD Features2=3D0x1e7 >=20 --------------enigC909810FF4A687C8F386C0B3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPZO1SAAoJELFAT5FmjZuE8UsQAMWsraKH5s6GzDMixW2kxwfU C5xPugnZ+4cv6EZQZPFOyGC/CBRKFmSLGM5RASMXG4ca10y1oq3M/hJaNz18zmsa REQndNm+Z8IsVxL4m5Aj77xIU6g0q8zaeA00OvavtC8/u1dO0XpxPNV0jAZhkOI6 JP9W0QdIJc8BDeuEBptNCeZCYPCjQTxqSDGI+pJP4ymMtpsT7PLB90ObkZfJe3BX b/A7pLRbmGEnf7zXQxNJ4WlQ9ec6eagSu/wQHyPJEOIOdmVK4VwkSo5QyFBMVs2o nbBxu9oXFH0+r+03YrCaMLrnXiEhKXuF9B9KlAR63rdy9A2Aj4pLJotg3GW0wN4z fDvxXIVHsdgC7pE6AZY5a/lwfR9mGnpNxd7WTziWqN172EcMhrBinGT5MUJJW5vH +/tJiVl6WYW+tKrVtzOEdfcusRDmWYiNZlBnDS+VuH7kR8Pke9Tz61eP83KYluEX GJ6h4gxxlMD95Wiv3r5haDOnhM1jjSPhKMELWtMqiKBG+gj6Kg6bWeccxsnev6SD B5ZXK6B96WaHSlvfDytsKy6e9q/qfIBquN+B1/XSpuPtNO3srSm4CAX8C4UnR+PR bvW5EAwXtSe9zhDKp9RLBQuo7LOnc+zQQq14HJUmY+0XAPFQvQ17Pad85nf1mWJt aCdJxQESM7nQS2Q+zNyj =fh1e -----END PGP SIGNATURE----- --------------enigC909810FF4A687C8F386C0B3--