From owner-freebsd-current@FreeBSD.ORG Fri Dec 29 12:31:07 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 CE1A216A403; Fri, 29 Dec 2006 12:31:07 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mx1.freebsd.org (Postfix) with ESMTP id A59D213C4A0; Fri, 29 Dec 2006 12:31:07 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 29 Dec 2006 02:49:03 -0800 X-IronPort-AV: i="4.12,218,1165219200"; d="scan'208"; a="454127839:sNHT52756340" Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id kBTAn2b5009382; Fri, 29 Dec 2006 02:49:02 -0800 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kBTAmwPn021225; Fri, 29 Dec 2006 02:48:58 -0800 (PST) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Dec 2006 02:48:58 -0800 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Dec 2006 02:48:57 -0800 Message-ID: <4594F282.7080504@cisco.com> Date: Fri, 29 Dec 2006 05:48:34 -0500 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061029 FreeBSD/i386 SeaMonkey/1.0.6 MIME-Version: 1.0 To: John Baldwin References: <45891FE9.4020700@cisco.com> <58281AA0-3738-490C-9EA8-7766033713A2@siliconlandmark.com> <458960F2.9090703@cisco.com> <200612281756.29949.jhb@freebsd.org> In-Reply-To: <200612281756.29949.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Dec 2006 10:48:57.0205 (UTC) FILETIME=[F0D4BA50:01C72B36] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2611; t=1167389342; x=1168253342; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20Re=3A=20A=20stuck=20system |Sender:=20; bh=LYsyZdUiPEgB/2Du2xsNInKgzuG9M9ZMLM93VYXmh74=; b=DrnvLreYzzJeqH+pdTXQSXSvormhFxdQNouGNY4UAtHLqpMxgTa1u4EU7V/O/6Sx1kyp9QOZ vky+ZNN2uZ5FQD394LN1efsFbF88hKoJAfWZil8MJFuTklBBL8ONgNMI; Authentication-Results: sj-dkim-3; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim3002 verified; ); 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: Fri, 29 Dec 2006 12:31:07 -0000 John Baldwin wrote: > On Wednesday 20 December 2006 11:12, Randall Stewart wrote: >> Interesting.. I have actually been having >> this problem for a while... can't remember >> when I last updated.. its related to pounding >> the network.. at least mine seems to be... (I >> am pounding the loopback).. and it appears >> that everything just "freezes". >> >> Is your machine a Gig-a-Byte motherboard? > > Do you have a dual-port msk0 device? 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 R > >> R >> >> Andre Guibert de Bruet wrote: >>> >>> On Dec 20, 2006, at 8:49 AM, Randall Stewart wrote: >>> >>>> Ok, I was wrong on this... I recreated it.. hooked up >>>> my em0 card to my laptop (right now its isolated >>>> running the mpi tests and uses the loopback only). >>>> >>>> I do a ping >>>> >>>> And ta-da the system comes back to life after >>>> being hung for 15 minutes. >>>> >>>> This time I did not see any of the usual syslog messages >>>> either... of course it was only "stuck" for 15 minutes or >>>> so... >>>> >>>> I will leave the thing running and get it stuck again and >>>> validate that the msk and usb will also cause the machine >>>> to come back to life.. >>>> >>>> Is there any way this could be a lost interupt type problem (remember >>>> the scheduler is appearing to "stop" scheduling things). OR >>>> is this a problem with my hardware... somehow failing to >>>> deliver interupts maybe??? >>> >>> I am seeing something similar on my dual Xeon system. It appears that a >>> kernel from December 13th did not exhibit this behavior whereas one >>> from the 16th does. I am able to "revive" the machine by pushing traf >>> on the msk0 interface. >>> >>> Kernel config: http://bling.properkernel.com/freebsd/BLING >>> >>> Andy >>> >>> /* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */ >>> /* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */ >>> /* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e 0000 */ >>> /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ >>> >>> >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>> >> > -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell)