From owner-freebsd-bugs@freebsd.org  Tue Jul  4 14:10:56 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 BBEECD92C18
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue,  4 Jul 2017 14:10:56 +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 A6BA37C388
 for <freebsd-bugs@FreeBSD.org>; Tue,  4 Jul 2017 14:10:56 +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 v64EAu4K018649
 for <freebsd-bugs@FreeBSD.org>; Tue, 4 Jul 2017 14:10:56 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 220277] 11.1-BETA3 hangs on Dell Vostro V130 during boot
Date: Tue, 04 Jul 2017 14:10:56 +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: regression
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: 
Message-ID: <bug-220277-8-yVFXcI1a6p@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-220277-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-220277-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, 04 Jul 2017 14:10:56 -0000

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

--- Comment #15 from John Baldwin <jhb@FreeBSD.org> ---
(In reply to Mark Johnston from comment #12)
It's probably worth looking at the stacks of all the other threads to find
which one owns the lock and then determine why it isn't running.

Are there any other threads that are runnable?  It might be that we need to
have pause() on thread0 still not sleep via callouts, but perhaps it needs =
to
call mi_switch/sched_yield in a loop to give other runnable threads a chanc=
e in
conjunction with spinning.

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