From owner-freebsd-current@FreeBSD.ORG Wed Dec 20 12:16:30 2006 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 17FD516A494 for ; Wed, 20 Dec 2006 12:16:30 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4704443CA2 for ; Wed, 20 Dec 2006 12:16:03 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id kBKC1pDB089023; Wed, 20 Dec 2006 04:01:51 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id kBKC1pqi089022; Wed, 20 Dec 2006 04:01:51 -0800 (PST) (envelope-from rizzo) Date: Wed, 20 Dec 2006 04:01:51 -0800 From: Luigi Rizzo To: Randall Stewart Message-ID: <20061220040151.B88849@xorpc.icir.org> References: <45891FE9.4020700@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <45891FE9.4020700@cisco.com>; from rrs@cisco.com on Wed, Dec 20, 2006 at 06:35:05AM -0500 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, 20 Dec 2006 12:16:30 -0000 On Wed, Dec 20, 2006 at 06:35:05AM -0500, Randall Stewart wrote: > All: > > Ok my P4D machine is sitting hung... its in that > state I mentioned previously. > > It will not respond to network input on the em0 card... i.e. > it won't answer pings.. > > I have not tried the new msk0 device... its not configured up :-( > > Now, I know from past experience if I hit any key... it will > start up again.. give out various warnings and timeouts.. sometimes > a "clock ran backwards".. possibly.. and then > start working fine again.. > > Is there anything I can try to get some information so we can > figure whats going on... > > It could be a hardware problem... don't know... but > it might not be.. it does look like a lost interupt... but > thats just a stab in the dark guess.. could you try putting a second network card in the box ? if you suspect it is only the 'em' card that is stuck a second one might give you some hints on what is going on. or plug in some usb device and see if there is any daemon responding to the event, etc. cheers luigi