Date: Wed, 25 Sep 2013 16:30:55 +0100 (BST) From: Anton Shterenlikht <mexas@bris.ac.uk> To: davide.italiano@gmail.com, mexas@bris.ac.uk Cc: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org Subject: Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks Message-ID: <201309251530.r8PFUtMG002713@mech-cluster241.men.bris.ac.uk> In-Reply-To: <CACYV=-FRo-5kGVgLjyFPOc2Bfe3imUFL2_Zkx6SEPAw7qzfMiA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>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? I've never used trace. Also, I'm getting a panic, so cannot run ps, I think. Thanks Anton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201309251530.r8PFUtMG002713>