From owner-freebsd-current@FreeBSD.ORG  Wed Jun 17 17:09:26 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 676E2888;
 Wed, 17 Jun 2015 17:09:26 +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 EA76F63C;
 Wed, 17 Jun 2015 17:09:25 +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 t5HH9G8Y080100
 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
 Wed, 17 Jun 2015 20:09:16 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t5HH9G8Y080100
Received: (from kostik@localhost)
 by tom.home (8.14.9/8.14.9/Submit) id t5HH9GBL080099;
 Wed, 17 Jun 2015 20:09:16 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Wed, 17 Jun 2015 20:09:16 +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: <20150617170916.GC2080@kib.kiev.ua>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <176EBAFD-0EEF-4D6B-9136-0006C994FDFF@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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2015 17:09:26 -0000

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.