Date: Wed, 3 Jan 2007 10:05:55 -0200 From: Ricardo Nabinger Sanchez <rnsanchez@wait4.org> To: Randall Stewart <rrs@cisco.com> Cc: freebsd-current@freebsd.org Subject: Re: A stuck system 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 Dec 2006 05:48:34 -0500
Randall Stewart <rrs@cisco.com> 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 <rnsanchez@{gmail.com,wait4.org}>
Powered by FreeBSD
"Left to themselves, things tend to go from bad to worse."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070103100555.3611b41c.rnsanchez>