From owner-freebsd-bugs@freebsd.org  Wed Mar 22 15:28:47 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07878D187C4
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 22 Mar 2017 15:28:47 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id EB67216AC
 for <freebsd-bugs@FreeBSD.org>; Wed, 22 Mar 2017 15:28:46 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2MFSjJs092266
 for <freebsd-bugs@FreeBSD.org>; Wed, 22 Mar 2017 15:28:46 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 217994] Kernel panic in native_lapic_setup with 12-CURRENT on
 EC2 machine
Date: Wed, 22 Mar 2017 15:28:46 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: sylvain@sylvaingarrigues.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217994-8-Q3Hu7XdEtX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217994-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-217994-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2017 15:28:47 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217994

--- Comment #16 from Sylvain Garrigues <sylvain@sylvaingarrigues.com> ---
Guys, I recompiled without CPUTYPE and now the kernel boots. I am so ashame=
d to
have disturbed you for this.

Though, my CPU *is* Haswell:
# sysctl -a | egrep -i 'hw.machine|hw.ncpu|hw.model'
hw.machine: amd64
hw.model: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
hw.ncpu: 1
hw.machine_arch: amd64

So I'm pissed I can't use CPUTYPE here. Don't know if I should blame KVM or
Amazon. I have another older EC2 machine where CPUTYPE=3Divybridge works BT=
W.

Nevertheless, thanks so much for quick and accurate feedback, you guys are =
the
reason I wouldn't dream of using any other OS than FreeBSD. THANKS!

Bug can be closed.

--=20
You are receiving this mail because:
You are the assignee for the bug.=