On Wed, Jun 17, 2015 at 03:09:16PM -0230, Jonathan Anderson wrote: > > On Jun 17, 2015, at 2:39 PM, Konstantin Belousov <kostik...@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. _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"