From owner-freebsd-stable@FreeBSD.ORG Thu Jan 19 17:35:04 2012 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 DB4821065670 for ; Thu, 19 Jan 2012 17:35:04 +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 21E918FC0A for ; Thu, 19 Jan 2012 17:35:03 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA21242; Thu, 19 Jan 2012 19:35:01 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <4F185445.7080605@FreeBSD.org> Date: Thu, 19 Jan 2012 19:35:01 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120111 Thunderbird/9.0 MIME-Version: 1.0 To: =?UTF-8?B?TMOhc3psw7MgS8OBUk9MWUk=?= References: <4F181FE7.30904@karolyi.hu> <4F182516.3020506@gmail.com> <4F182FB3.7050405@karolyi.hu> <4F183008.9040603@karolyi.hu> <4F1835ED.3050609@karolyi.hu> <4F1836E1.1080105@karolyi.hu> <4F1848BF.2050900@karolyi.hu> <4F184F8F.4040708@FreeBSD.org> In-Reply-To: <4F184F8F.4040708@FreeBSD.org> X-Enigmail-Version: undefined Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@FreeBSD.org Subject: Re: Strange 'hangs' with RELENG_9 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: Thu, 19 Jan 2012 17:35:04 -0000 on 19/01/2012 19:14 Alexander Motin said the following: > On 19.01.2012 18:51, Oliver Pinter wrote: >> CC: Alexander Motin >> >> On 1/19/12, László KÁROLYI wrote: >>> László KÁROLYI wrote: >>>> Ok, couldn't get it through... So here is it, uploaded: >>>> >>>> http://www.freeimagehosting.net/s836i >>> Another screenshot here: >>> >>> http://www.freeimagehosting.net/xv26d > > I am not sure how freezes that could be fixed with key press could be related to > panics around storage. I would try to go two different ways: > - for panics, if dumping is not possible, I would try to resolve address of the > "instruction pointer" from both messages with `addr2line -e /path/to/kernel address`. I would recommend to add the following options to the kernel config: options STACK options DDB options DDB_NUMSYM options KDB options KDB_TRACE options KDB_UNATTENDED (if you don't have any of them already). That should add some useful information to the panic messages. Please try to capture the first panic report before any secondary panics cloud the situation. And I agree with Alexander that the panics and the hangs could be unrelated. -- Andriy Gapon