From owner-freebsd-current@FreeBSD.ORG Thu Jun 18 10:46:45 2015 Return-Path: Delivered-To: freebsd-current@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4297C9FD; Thu, 18 Jun 2015 10:46:45 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA00CB27; Thu, 18 Jun 2015 10:46:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t5IAOiDv039919 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 18 Jun 2015 13:24:44 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t5IAOiDv039919 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t5IAOiVx039918; Thu, 18 Jun 2015 13:24:44 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 18 Jun 2015 13:24:44 +0300 From: Konstantin Belousov To: Jonathan Anderson Cc: freebsd-current@freebsd.org Subject: Re: Boot hang: Sony VAIO Message-ID: <20150618102444.GF2080@kib.kiev.ua> References: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D91173F-3E62-4BD6-8D08-AB23C81EB359@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jun 2015 10:46:45 -0000 On Wed, Jun 17, 2015 at 03:09:16PM -0230, Jonathan Anderson wrote: > > On Jun 17, 2015, at 2:39 PM, Konstantin Belousov 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.