Date: Mon, 16 Feb 2015 15:21:04 +0100 From: Koop Mast <kwm@rainbow-runner.nl> To: Konstantin Belousov <kib@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r278473 - in head/sys: amd64/amd64 amd64/include amd64/vmm contrib/dev/acpica/include i386/i386 i386/include x86/acpica x86/include x86/x86 x86/xen Message-ID: <54E1FCD0.6000500@rainbow-runner.nl> In-Reply-To: <201502092100.t19L0vsv010944@svn.freebsd.org> References: <201502092100.t19L0vsv010944@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9-2-2015 22:00, Konstantin Belousov 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. Hi Konstantin, This commit broke my Sandybridge laptop. If x2APIC is enabled the kernel freezes after the "ACPI APIC Table: <_ASUS_ NoteBook>" line is printed. I can't get much information out of it since I couldn't get into the kernel debugger nor has the machine a serial cable. I did notice that "x2APIC" is listed in the CPU Features2 list, but for the cpu's it reports "x2APIC: 0". I don't know if this has to do with disabled x2APIC or some hardware/bios issue? -Koop Verbose dmesg with x2APIC disabled: https://people.freebsd.org/~kwm/dmesg-x2apic.txt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54E1FCD0.6000500>