NetBSD Problem Report #57569

From www@netbsd.org  Sat Aug  5 14:43:48 2023
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 216CC1A923A
	for <gnats-bugs@gnats.NetBSD.org>; Sat,  5 Aug 2023 14:43:48 +0000 (UTC)
Message-Id: <20230805144346.925331A923B@mollari.NetBSD.org>
Date: Sat,  5 Aug 2023 14:43:46 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: ddb(4) should have a command to print stack traces for all CPUs
X-Send-Pr-Version: www-1.0

>Number:         57569
>Category:       kern
>Synopsis:       ddb(4) should have a command to print stack traces for all CPUs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Aug 05 14:45:00 +0000 2023
>Originator:     Taylor R Campbell
>Release:        current
>Organization:
The NetBStopped in pid 1497.273 (firefox) at    netbsd:breakpoint+0x5:  leave
>Environment:
having its hottest summer in history
>Description:
The trace (bt) command in ddb should have a way to print a stack trace for every CPU in the system, for diagnosis when something is wedged in, e.g., an interrupt handler or at high IPL with the kernel lock held.
>How-To-Repeat:
1. Put an infinite loop in a secretly chosen interrupt handler.
2. Try to find which interrupt handler it was when the system wedges.
>Fix:
Yes, please!

Home	PR Database Search