Date: Thu, 18 Jun 2015 13:24:44 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Jonathan Anderson <jonathan@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: Boot hang: Sony VAIO Message-ID: <20150618102444.GF2080@kib.kiev.ua> In-Reply-To: <4D91173F-3E62-4BD6-8D08-AB23C81EB359@FreeBSD.org> References: <F37E1325-76ED-4533-9146-26E14F63FC12@FreeBSD.org> <20150617143049.GZ2080@kib.kiev.ua> <633BF6AA-D201-4647-8F14-401911DABCBE@FreeBSD.org> <20150617165456.GB2080@kib.kiev.ua> <176EBAFD-0EEF-4D6B-9136-0006C994FDFF@FreeBSD.org> <20150617170916.GC2080@kib.kiev.ua> <4D91173F-3E62-4BD6-8D08-AB23C81EB359@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 17, 2015 at 03:09:16PM -0230, Jonathan Anderson wrote: > > On Jun 17, 2015, at 2:39 PM, Konstantin Belousov <kostikbel@gmail.com> wrote: > > > > On Wed, Jun 17, 2015 at 02:32:16PM -0230, Jonathan Anderson wrote: > >> The system boots the 11-CURRENT kernel in "safe mode" (not sure if it???s the kern.mp.disabled or kern.eventtimer.periodic that???s causing that), after which `dmesg -a` produces the following output: > >> > >> https://people.freebsd.org/~jonathan/vaio-acpi-dmar.txt > > > > Try a loader tunable hw.x2apic_enable=0. > > Your UP boot was successfull with x2APIC mode enabled and set, but there > > are rumors that some SandyBridge BIOSes are buggy. > > That seems to fix it... thanks! > > Is there a Wiki page somewhere for people to document these kinds of workarounds for particular configurations? > The issue with x2APIC and _some_ Sandy Bridge laptop is known for long time, but I am unable to find and reliable commons in the set of machines which have trouble. I might end up disabling x2APIC on mobile Sandys at all.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150618102444.GF2080>