From owner-freebsd-current@FreeBSD.ORG Thu Sep 26 10:45:47 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BF892D6A for ; Thu, 26 Sep 2013 10:45:47 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog123.obsmtp.com (eu1sys200aog123.obsmtp.com [207.126.144.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1D2CF2289 for ; Thu, 26 Sep 2013 10:45:46 +0000 (UTC) Received: from mail-wi0-f173.google.com ([209.85.212.173]) (using TLSv1) by eu1sys200aob123.postini.com ([207.126.147.11]) with SMTP ID DSNKUkQQWdKlhf7V0tWy2LPb8ZvKKb2i2Z/A@postini.com; Thu, 26 Sep 2013 10:45:47 UTC Received: by mail-wi0-f173.google.com with SMTP id hq15so6828747wib.0 for ; Thu, 26 Sep 2013 03:45:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:message-id:to:subject:cc :reply-to:in-reply-to; bh=XPbui4ChMzMWcyMSYQ0w01dPYS3siL8QUqyrichb/LI=; b=PjhGuVAqCS02k59xb8s2qxf16nnOowq3hMJwNo5CpLOOkGDuxN+kRH7YzfSqjn6DJX xZNZqOWOL58uzAM/wQKqWp18yKNAp6OgaJXbJUhagXhKv+Qfe95u8hD7wcWctCX5c/Me IFF0Fe3fkS/TBmP4trVtifRjTR/zCU50FTZmjcCzxF89VaSugbSvsz8ZpQhtDKRjPSCk AWh5HtvgoOqoNICIwijiZNNz65ETkuEz0fVf7xk799/4CGIxySzwB7PkQPP6IA0ISQ1P Z6wnBoI3lJMmoPoSKaAmZ1OAh80ryUWJOpGYHdp8j1tiu12nKxmnCe5NX2lYl0XHkQWs hbfw== X-Received: by 10.181.12.112 with SMTP id ep16mr41848wid.59.1380190987693; Thu, 26 Sep 2013 03:23:07 -0700 (PDT) X-Gm-Message-State: ALoCoQnCezGLh0wr5cjFT9d5xqD1GJp1OSwgZ0o2/4W8p7vEaPMtuH988shnQSANGdc2aVEW2vmTGVeEGaXbMMq1/xlHxrPShQAop6VgLpXfBQn2lmaXg74NBBTAmJvpuSoiaB2SYnyAEcL8lYOli1T0qDPNt2l8kcTKd4AePDdHYN7iltjIx1w= X-Received: by 10.181.12.112 with SMTP id ep16mr41836wid.59.1380190987593; Thu, 26 Sep 2013 03:23:07 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id ed12sm26728968wic.11.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 26 Sep 2013 03:23:06 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r8QAN48f013219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 26 Sep 2013 11:23:04 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r8QAN45I013218; Thu, 26 Sep 2013 11:23:04 +0100 (BST) (envelope-from mexas) Date: Thu, 26 Sep 2013 11:23:04 +0100 (BST) From: Anton Shterenlikht Message-Id: <201309261023.r8QAN45I013218@mech-cluster241.men.bris.ac.uk> To: davide@freebsd.org, mexas@bris.ac.uk Subject: Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks In-Reply-To: Cc: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bris.ac.uk List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Sep 2013 10:45:47 -0000 >From davide.italiano@gmail.com Wed Sep 25 19:00:09 2013 > >On Wed, Sep 25, 2013 at 5:30 PM, Anton Shterenlikht wrote: >> >From davide.italiano@gmail.com Wed Sep 25 16:12:47 2013 >>> >>>Can you please paste the output of 'show locks', 'show alllocks', >>>'show lockedvnods' at least? >>>Ideally you should provide all the informations listed here. >>>http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html >> >> ok, I'll need to study this. >> >> I've in the kernel: >> >> # Debugging support. Always need this: >> options KDB # Enable kernel debugger support. >> options KDB_TRACE # Print a stack trace for a panic. >> # For full debugger support use (turn off in stable branch): >> options DDB # Support DDB >> options GDB # Support remote GDB >> options DEADLKRES # Enable the deadlock resolver >> options INVARIANTS # Enable calls of extra sanity checking >> options INVARIANT_SUPPORT # required by INVARIANTS >> options WITNESS # Enable checks to detect deadlocks and cycles >> options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed >> options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones >> >> so I'm missing DEBUG_LOCKS, DEBUG_VFS_LOCKS and DIAGNOSTIC >> from the handbook list. >> >> What about all debug options in GENERIC which are >> not mentioned in your link? Specifically, do I need >> to have DEADLKRES? >> > >Yes, you need that option because it's DEADLKRES that triggers the panic. > >> I've never used trace. >> Also, I'm getting a panic, so cannot run ps, I think. >> > >You can run 'ps' from ddb prompt. >As an advice I suggest you to setup textdump(4) on your machine and >set up a script to gather the required informations, so that you can >get those informations pretty easily for report. The manpage has >detailed description about how to do this. Regarding textdump(4), I'm not clear where the following "scripts" should be located and used: *quote* EXAMPLES In the following example, the script kdb.enter.panic will run when the kernel debugger is entered as a result of a panic, enable output capture, dump several useful pieces of debugging information, and then invoke panic in order to force a kernel dump to be written out followed by a reboot: script kdb.enter.panic=textdump set; capture on; show allpcpu; bt; ps; alltrace; show alllocks; call doadump; reset In the following example, the script kdb.enter.witness will run when the kernel debugger is entered as a result of a witness violation, printing lock-related information for the user: script kdb.enter.witness=show locks These scripts may also be configured using the ddb(8) utility. *end quote* Are these ddb(8) commands? Or do I set these in /etc/rc.conf? Please advise Thanks Anton