From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 12:36:28 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 699B916A4A0; Wed, 3 Jan 2007 12:36:28 +0000 (UTC) (envelope-from rnsanchez@wait4.org) Received: from sumo.dreamhost.com (sumo.dreamhost.com [66.33.216.29]) by mx1.freebsd.org (Postfix) with ESMTP id 52A9513C468; Wed, 3 Jan 2007 12:36:28 +0000 (UTC) (envelope-from rnsanchez@wait4.org) Received: from spunkymail-a6.dreamhost.com (sd-green-bigip-66.dreamhost.com [208.97.132.66]) by sumo.dreamhost.com (Postfix) with ESMTP id 0C3BE178C95; Wed, 3 Jan 2007 04:06:01 -0800 (PST) Received: from sauron.lan.box (unknown [200.180.187.117]) by spunkymail-a6.dreamhost.com (Postfix) with ESMTP id E1CF8109F2F; Wed, 3 Jan 2007 04:05:56 -0800 (PST) Date: Wed, 3 Jan 2007 10:05:55 -0200 From: Ricardo Nabinger Sanchez To: Randall Stewart Message-Id: <20070103100555.3611b41c.rnsanchez@wait4.org> In-Reply-To: <4594F282.7080504@cisco.com> References: <45891FE9.4020700@cisco.com> <58281AA0-3738-490C-9EA8-7766033713A2@siliconlandmark.com> <458960F2.9090703@cisco.com> <200612281756.29949.jhb@freebsd.org> <4594F282.7080504@cisco.com> Organization: SYS_WAIT4 X-Mailer: Sylpheed 2.3.0beta7 (GTK+ 2.10.6; i386-unknown-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: A stuck system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2007 12:36:28 -0000 On Fri, 29 Dec 2006 05:48:34 -0500 Randall Stewart wrote: > Nope... its just a single port, on-motherboard msk0. > > It does wake up though if I ping any interface... > > I suspect it might be a hardware problem.. not sure > yet :-0 How about installing a ping trap in the device driver to generate a dump? What I mean is to, whenever the device driver receives a packet, it checks if the packet is a special ping packet (with some specific data, like "dumpdump..." in the data field), and if so, forces a dump so you can check (luckily) where the system came from. It's a long shot, but perhaps it gives a hint. Does this behavior happens on IA-64 boxes? If so, the kernel could set up the processor to save performance data (specifically the branch history), and the special ping (or something else) could be used to print the branch buffer history, instead of dumping a core. Debugging symbols would be a must, I believe. -- Ricardo Nabinger Sanchez Powered by FreeBSD "Left to themselves, things tend to go from bad to worse."