From owner-freebsd-stable@FreeBSD.ORG Sat Dec 11 17:08:48 2010 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 5A40B1065780 for ; Sat, 11 Dec 2010 17:08:48 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A116D8FC12 for ; Sat, 11 Dec 2010 17:08:47 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA23117; Sat, 11 Dec 2010 19:06:10 +0200 (EET) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1PRSte-0008Fd-94; Sat, 11 Dec 2010 19:06:10 +0200 Message-ID: <4D03AF81.7010401@freebsd.org> Date: Sat, 11 Dec 2010 19:06:09 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101029 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: "Eugene M. Zheganin" References: <4D037934.6080401@norma.perm.ru> In-Reply-To: <4D037934.6080401@norma.perm.ru> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: 8.1 livelock/hangup: possible actions 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, 11 Dec 2010 17:08:48 -0000 on 11/12/2010 15:14 Eugene M. Zheganin said the following: > Hi. > > I'm having problems with 8.1-REL/zfs/amd64. It's a IMB x3250 m2 system, 1Gb RAM, > dualcore intel e3110, two bge(4) and LSI1064e disk controller. > > Suddenly it can stop answering to network requests and nothing works except of > the keyborad, so I guess the system isn't really dead. Can you enter debugger via its key combination? > No trap screen, no reboot. > > I realize very clearly that this description isn't useful in any way. :) > > So I'm asking what can I do to localize the source of the problem or get > additional diagnostics ? > Only reset button currently comes to my mind, it helps of course, but it doesn't > provide me with any information about what is happening. After reboot logs are > empty for the period of the hangup. -- Andriy Gapon