From owner-freebsd-bugs@freebsd.org  Tue Jun 13 16:13:24 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 CEA22BF87C1
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue, 13 Jun 2017 16:13:24 +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 B188381A22
 for <freebsd-bugs@FreeBSD.org>; Tue, 13 Jun 2017 16:13:24 +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 v5DGDOt1034711
 for <freebsd-bugs@FreeBSD.org>; Tue, 13 Jun 2017 16:13:24 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 219882] [SMP][patch] 11.1-PRERELEASE panics at CPU detection on
 a single CPU i386 machine
Date: Tue, 13 Jun 2017 16:13:24 +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: 11.0-STABLE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: jhb@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: attachments.created
Message-ID: <bug-219882-8-XtaqhJc44U@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-219882-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-219882-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: Tue, 13 Jun 2017 16:13:24 -0000

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

--- Comment #3 from John Baldwin <jhb@FreeBSD.org> ---
Created attachment 183451
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D183451&action=
=3Dedit
noassign_on_up.patch

Please try this patch instead.  In the !EARLY_AP_STARTUP case, the 'assign_=
cpu'
variable is never set on a UP system, so it results in never trying to assi=
gn
CPUs.  This patch restores that by checking for an SMP system explicitly be=
fore
trying to assign a CPU.  I think the panic in the atpic method is still a g=
ood
canary for ensuring the calling code is doing the right thing.

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