From owner-freebsd-current@FreeBSD.ORG Wed Dec 17 15:32:30 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 546651065672 for ; Wed, 17 Dec 2008 15:32:30 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from mail-chaos.rambler.ru (mail-chaos.rambler.ru [81.19.68.130]) by mx1.freebsd.org (Postfix) with ESMTP id 0F8D38FC14 for ; Wed, 17 Dec 2008 15:32:29 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from [192.168.1.15] (unknown [81.19.90.156]) (Authenticated sender: citrin@citrin.ru) by mail-chaos.rambler.ru (Postfix) with ESMTPSA id CC40317039 for ; Wed, 17 Dec 2008 18:32:27 +0300 (MSK) Message-ID: <49491B8B.70603@citrin.ru> Date: Wed, 17 Dec 2008 18:32:27 +0300 From: Anton Yuzhaninov User-Agent: Thunderbird 2.0.0.18 (X11/20081129) MIME-Version: 1.0 To: current@freebsd.org References: <4947C526.2080702@citrin.ru> In-Reply-To: <4947C526.2080702@citrin.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: hangup (livelock) - db> prompt in endless loop 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, 17 Dec 2008 15:32:30 -0000 Anton Yuzhaninov wrote: > My box with fresh current sometimes stops to respond. > > On screen in endless loop printed debugger prompt > > db> > > but I can't type anything here. > > Alt+Ctrl+Esc and Alt+Ctrl+Del don't stops this loop. > > How I can debug this problem? > > system: current from Mon Dec 15 16:16:23 MSK 2008 with GENERIC kernel, > amd64, SMP. > with this sysctls set: debug.debugger_on_panic=0 debug.trace_on_panic=1 db> prmopt not shown, and I can see the panic backtrace: http://img-fotki.yandex.ru/get/3002/bgp4.1/0_25e8a_45ba0879_orig But coredump on disk don't written. -- Anton Yuzhaninov P. S. printing db> prompt in endless loop seems to be separate bug...