From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 1 18:02:50 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 443BC106568B for ; Tue, 1 Sep 2009 18:02:50 +0000 (UTC) (envelope-from news@citylink.dinoex.sub.org) Received: from uucp.dinoex.sub.de (uucp.dinoex.sub.de [194.45.71.2]) by mx1.freebsd.org (Postfix) with ESMTP id A89B98FC1E for ; Tue, 1 Sep 2009 18:02:49 +0000 (UTC) Received: from uucp.dinoex.sub.de (uucp@uucp.dinoex.sub.de [194.45.71.2] (may be forged)) by uucp.dinoex.sub.de (8.14.3/8.14.2) with ESMTP id n81I2RZx094488 for ; Tue, 1 Sep 2009 20:02:27 +0200 (CEST) (envelope-from news@citylink.dinoex.sub.org) X-MDaemon-Deliver-To: Received: from citylink.dinoex.sub.org (uucp@localhost) by uucp.dinoex.sub.de (8.14.3/8.14.2/Submit) with UUCP id n81I2RKS094487 for freebsd-hackers@FreeBSD.ORG; Tue, 1 Sep 2009 20:02:27 +0200 (CEST) (envelope-from news@citylink.dinoex.sub.org) Received: from gate.oper.dinoex.org (gate-e [192.168.98.2]) by citylink.dinoex.sub.de (8.14.3/8.14.3) with ESMTP id n81Ht9Q8097532 for ; Tue, 1 Sep 2009 19:55:09 +0200 (CEST) (envelope-from news@gate.oper.dinoex.org) Received: from gate.oper.dinoex.org (gate-e [192.168.98.2]) by gate.oper.dinoex.org (8.14.3/8.14.3) with ESMTP id n81Hs2b5097281 for ; Tue, 1 Sep 2009 19:54:02 +0200 (CEST) (envelope-from news@gate.oper.dinoex.org) Received: (from news@localhost) by gate.oper.dinoex.org (8.14.3/8.14.3/Submit) id n81Hs2Ki097273 for freebsd-hackers@FreeBSD.ORG; Tue, 1 Sep 2009 19:54:02 +0200 (CEST) (envelope-from news) From: peter@citylink.dinoex.sub.org (Peter Much) Message-ID: Date: Tue, 1 Sep 2009 17:45:44 GMT Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Mime-Version: 1.0 Organization: some more stinking socks X-Newsreader: trn 4.0-test76 (Apr 2, 2001) Sender: li-fbsd@citylink.dinoex.sub.org To: freebsd-hackers@FreeBSD.ORG X-Milter: Spamilter (Reciever: uucp.dinoex.sub.de; Sender-ip: 194.45.71.2; Sender-helo: uucp.dinoex.sub.de; ) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (uucp.dinoex.sub.de [194.45.71.2]); Tue, 01 Sep 2009 20:02:28 +0200 (CEST) Cc: Subject: crashdump "watchdog timeout" - Howto get useful information? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2009 18:02:50 -0000 Dear all, could anybody share some insight (or pointers to docs) on how to approach an analysis of a "watchdog timeout" crashdump? I hopefully have the necessities in place (that is, I can load the dump into ddd and actually see things). But I have no real idea about where to start looking for interesting things - some structure from where to unroll what the system was doing (or not doing). The "developers handbook" mainly explains about figuring the cause of the crash - but in my case this is obvious, it is the watchdog I have configured. Since this is a reproducible issue, ideas on things that could be configured beforehand could also be useful. rgds, PMc