From owner-freebsd-hackers@FreeBSD.ORG  Sun Dec 19 01:39:02 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4621816A4CE
	for <freebsd-hackers@freebsd.org>;
	Sun, 19 Dec 2004 01:39:01 +0000 (GMT)
Received: from wattres.watt.com (wattres.watt.com [66.93.133.130])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0504C43D48
	for <freebsd-hackers@freebsd.org>;
	Sun, 19 Dec 2004 01:39:01 +0000 (GMT)	(envelope-from steve@Watt.COM)
Received: from wattres.watt.com (localhost.watt.com [127.0.0.1])
	by wattres.watt.com (8.13.1/8.13.1) with ESMTP id iBJ1d0Cv028208
	for <freebsd-hackers@freebsd.org>;
	Sat, 18 Dec 2004 17:39:00 -0800 (PST)
	(envelope-from steve@wattres.watt.com)
Received: (from steve@localhost)
	by wattres.watt.com (8.13.1/8.13.1/Submit) id iBJ1d0EL028207
	for freebsd-hackers@freebsd.org; Sat, 18 Dec 2004 17:39:00 -0800 (PST)
	(envelope-from steve)
Message-Id: <200412190139.iBJ1d0EL028207@wattres.watt.com>
From: steve@Watt.COM (Steve Watt)
Date: Sat, 18 Dec 2004 17:39:00 -0800
X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98)
To: freebsd-hackers@freebsd.org
X-Archived: 1103420340.836441352@wattres.Watt.COM
Subject: snapshots and innds
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Dec 2004 01:39:02 -0000

I'm getting a strong hunch that snapshots and inn don't get along
well, presumably having something to do with inn's extensive use
of mmap().

Just for an example, my system panic()ed earlier today (different
problem) and during the reboot, I'm stuck with an fsck_ufs on wchan
"ufs" and innd on wchan "suspfs", and neither of them responding
in any way.

Unfortunately, my attempts to figure out *where* exactly everyone's
hung is being hampered by my not having any idea how to cause kgdb
to attach to the desired thread, or how to determine what thread
number (100xx) is related to what entry in ps -H.

For that matter, when I try to do a "print *(struct proc *)0x{blah}"
in kgdb for an address I got out of ps -o pid,uprocp,wchan,command,
it doesn't seem to believe that there is a struct proc.

Is there an up-to-date (i.e. covers 5.3) place that talks about
kernel debugging?

-- 
Steve Watt KD6GGD  PP-ASEL-IA          ICBM: 121W 56' 57.8" / 37N 20' 14.9"
 Internet: steve @ Watt.COM                         Whois: SW32
   Free time?  There's no such thing.  It just comes in varying prices...