From owner-freebsd-questions Tue Feb 25 5:50:37 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1B1E37B401 for ; Tue, 25 Feb 2003 05:50:35 -0800 (PST) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5981643F75 for ; Tue, 25 Feb 2003 05:50:35 -0800 (PST) (envelope-from ddolson@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Tue, 25 Feb 2003 08:50:34 -0500 Message-ID: From: Dave Dolson To: "'questions@freebsd.org'" Subject: kgdb and cpu number question Date: Tue, 25 Feb 2003 08:50:26 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG kgdb supposedly supports a "cpu N" command where the various CPUs can be selected. However when debugging a vmcore file, all CPUs show the same backtrace in the kernel. (kgdb) cpu 0 initial pcb at 34d920 #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:493 493 in /usr/src/sys/kern/kern_shutdown.c (kgdb) cpu 1 initial pcb at 34d920 #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:493 493 in /usr/src/sys/kern/kern_shutdown.c The backtraces are identical, a panic occuring from interrupt context. (I won't bore you with them.) This is a slightly modified version of 4.7, i386. The questions: 1. Is this expected kgdb behaviour? 2. Is there some other way to examine what each CPU was doing? 3. At a panic, are all CPUs not running in the kernel suspended? Thanks, David Dolson (ddolson@sandvine.com, www.sandvine.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message