From owner-freebsd-bugs@freebsd.org  Sun Nov  8 23:38:43 2015
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 5FD3CA2A651
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sun,  8 Nov 2015 23:38:43 +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 4CC1D1CF2
 for <freebsd-bugs@FreeBSD.org>; Sun,  8 Nov 2015 23:38:43 +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 tA8NchVY084721
 for <freebsd-bugs@FreeBSD.org>; Sun, 8 Nov 2015 23:38:43 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 204376] Cavium ThunderX system heavily loaded while at db> prompt
Date: Sun, 08 Nov 2015 23:38:43 +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-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: ngie@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-204376-8-9NElBrKWdX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204376-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-204376-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.20
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: Sun, 08 Nov 2015 23:38:43 -0000

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

NGie Cooper <ngie@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cem@freebsd.org,
                   |                            |ngie@FreeBSD.org

--- Comment #1 from NGie Cooper <ngie@FreeBSD.org> ---
It's not just arm64; amd64 does/did a horrible job at yielding when in the
debugger (part of the reason why we have a script which goes and suspends test
VMs at $work if/when they panic).

Conrad had a patch out for amd64 a few months ago which yielded in the debugger
a bit on amd64, but IIRC there were issues at the time. I'll let him comment on
it though.

It would be nice if dropping into the debugger didn't spin all the CPUs at
~100% though.

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