From owner-freebsd-amd64@freebsd.org  Wed Aug  3 18:35:22 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 CDB1FBAE6E3
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed,  3 Aug 2016 18:35:22 +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 B99D31764
 for <freebsd-amd64@FreeBSD.org>; Wed,  3 Aug 2016 18:35:22 +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 u73IZMsG043234
 for <freebsd-amd64@FreeBSD.org>; Wed, 3 Aug 2016 18:35:22 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 211548] [mps] Activating X2Apic Mode in BIOS results in
 "io_cmds_active is out of sync errors", won't boot
Date: Wed, 03 Aug 2016 18:35:22 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-BETA3
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: kib@FreeBSD.org
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: cc
Message-ID: <bug-211548-6-fsfc8e2kJ7@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211548-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-211548-6@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-Mailman-Approved-At: Wed, 03 Aug 2016 18:58:59 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 18:35:22 -0000

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

Konstantin Belousov <kib@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kib@FreeBSD.org

--- Comment #1 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Benedict Reuschling from comment #0)
What exactly the statement 'won't boot' mean ?  Does the machine enters
infinite
loop with the messages ?

I would like to see the verbose dmesg with the x2APIC option turned off and=
 on
(can you capture using serial console ?).

Can you compile and boot kernel without mps(4) ?  You probably would be not
able to mount local root, but I need messages and not the operational syste=
m.

I do not think IPIs are ever used at the device probe stage, so it might be
some pecularity in the BIOS resources allocation triggered by the option.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=