From owner-freebsd-stable@FreeBSD.ORG Sat Jun 6 14:51:57 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 906E6106568C for ; Sat, 6 Jun 2009 14:51:57 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 55FA38FC19 for ; Sat, 6 Jun 2009 14:51:57 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MCxFN-000Agn-4q; Sat, 06 Jun 2009 15:51:49 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MCxFN-000BzM-3b; Sat, 06 Jun 2009 15:51:49 +0100 To: freebsd-stable@FreeBSD.ORG, nakaji@jp.freebsd.org In-Reply-To: <86d49h300c.fsf@ra333.heimat.gr.jp> Message-Id: From: Pete French Date: Sat, 06 Jun 2009 15:51:49 +0100 Cc: Subject: Re: Big problem still remains with 7.2-STABLE locking up X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jun 2009 14:51:58 -0000 > My story is very similar to Pete's. > http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047487.html My problem, which you link to there, tturrned out to be due to ICMP redirects, and is most definitely fixed in 7.2. So, your problem is not the same as mine, but some of the tips given there may help you ddebug it. > I followed some instructions in the list thread. But unfortunately, the > big problem still remains. 7.2-STABLE server locks up frequently. Are you using the latest STABLE ? I am rolling out the one from a few days ago with the bce fixes, and that works fine. > The kernel configuration is: ... > options BREAK_TO_DEBUGGER When the box locks up, can you actyually break to the debugger ? This is how we eventually tracked down my problem. -pete.