Date: Wed, 11 Feb 2015 00:43:39 +0000 (GMT) From: Rui Paulo <rpaulo@me.com> To: Konstantin Belousov <kib@FreeBSD.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: =?utf-8?B?UmU6IHN2biBjb21taXQ6IHIyNzg0NzMgLSBpbiBoZWFkL3N5czogYW1kNjQv?= =?utf-8?B?YW1kNjQgYW1kNjQvaW5jbHVkZSBhbWQ2NC92bW0gY29udHJpYi9kZXYvYWNw?= =?utf-8?B?aWNhL2luY2x1ZGUgaTM4Ni9pMzg2IGkzODYvaW5jbHVkZSB4ODYvYWNwaWNh?= =?utf-8?B?IHg4Ni9pbmNsdWRlIHg4Ni94ODYgeDg2L3hlbg==?= Message-ID: <bbbead6b-64da-4f0d-8821-98d79319aecf@me.com>
next in thread | raw e-mail | index | archive | help
On Feb 09, 2015, at 01:01 PM, Konstantin Belousov <kib@FreeBSD.org> wrote: Author: kib Date: Mon Feb 9 21:00:56 2015 New Revision: 278473 URL: https://svnweb.freebsd.org/changeset/base/278473 Log: Add x2APIC support. Enable it by default if CPU is capable. The hw.x2apic_enable tunable allows disabling it from the loader prompt. This breaks VMware Fusion when the host CPU has x2APIC support. In my case, mpt(4) was unable to receive interrupts and USB was similarly broken. It's possible that this is a VMware bug, but you might want to avoid turning this on when running under the VMware hypervisor.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bbbead6b-64da-4f0d-8821-98d79319aecf>