Date: Sat, 17 Mar 2012 15:39:02 -0400 From: Richard Yao <ryao@cs.stonybrook.edu> To: <alc@freebsd.org> Cc: Alan Cox <alan.l.cox@gmail.com>, freebsd-stable@freebsd.org Subject: Re: AMD Erratum 383 crashes FreeBSD 9-Stable Message-ID: <4F64E856.3040303@cs.stonybrook.edu> In-Reply-To: <CAJUyCcME8YgJkCmfCodJba0noKyGr8RMnJwSMrT_fECj8U7d=Q@mail.gmail.com> References: <4F64C50F.70409@cs.stonybrook.edu> <4F64C57F.6040403@cs.stonybrook.edu> <CAJUyCcME8YgJkCmfCodJba0noKyGr8RMnJwSMrT_fECj8U7d=Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--------------enig8B8515371D323AED15CCA1CB
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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. Howeve=
r,
> because you are running within a virtual machine, the automatic detecti=
on
> may not be working. Alternatively, you may be using a newer processor
> revision that still suffers from the bug, but the kernel doesn't enable=
the
> workaround for. Can you tell us how the FreeBSD guest sees the underly=
ing
> processor, e.g., the first few lines of dmesg from the guest?
>=20
> 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.
# dmesg
Copyright (c) 1992-2012 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.=
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 Ste=
pping =3D 1
Features=3D0x783fbfd<FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA=
,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2>
Features2=3D0x80802001<SSE3,CX16,POPCNT,HV>
AMD Features=3D0xe0100800<SYSCALL,NX,LM,3DNow!+,3DNow!>
AMD Features2=3D0x1e7<LAHF,CMP,SVM,ABM,SSE4A,MAS,Prefetch>
--------------enig8B8515371D323AED15CCA1CB
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/
iQIcBAEBAgAGBQJPZOhbAAoJELFAT5FmjZuED6kQAIqNna6RCnUgZE3/SZ/Hxsfq
a0TxJhdmlyKWT8ilHaQhTMCMgVYTCxG8zEaYm7D+jHYXz4Na3pkScG4SHA4fSDRf
US+zB/0JAGPnJ1IZKRsd+D53SNtz942EAs4AeLl5L4tKeG4Fuans7mU568wSvtTj
6v8qtc4EtSgMEVUvCYwWRXpyk/HmhqJDM+FLNBXYB7V2rxs8cvb2+9kS5s4LrAcq
KHJsyoLeAIg+yKbO+fBKp8LQlY3u2SLOhMNR8EevxgF4+TuOUa/lkeceQN+j6bND
H7XiK+YQ4gdZezkZwXastjp631k9aoDucOXEAkEK9XfKEKEqE2DzkveN4Ir5BFyo
veKNHac6UINeeYK0qFmYBvU6Gy2srvHsgtfJWWaFkUqYFon5j6KOnT7bcxnhLBoY
Pcs0DLEcDx55Ptt9x+OjBl5iDN1MKR7CEclTfiVSAX8fRv2vv4bgp/hJeBSj4FK3
Zs3GV1ezxBqYxD7Sf8Xo0/tTJmpxInSb5Mhvj/SOjY2MN0o7whwxmf3n10XZp3YD
zo7cezy50GrvwANOxwPRt/2dk08eCDRS+1JZhTS6km0eS/h3dxR2011CWQ7YRTFj
KDK5gHTeUCLULU62gl6V30oL6S6JCm0PGlGh58CN2V8+YCY/O4NE5Y+qAfjMGOBD
ptQg4WNFyElUCAxnLLLC
=mLFN
-----END PGP SIGNATURE-----
--------------enig8B8515371D323AED15CCA1CB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F64E856.3040303>