Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks

Anton Shterenlikht <[email protected]>
Newsgroups gmane.os.freebsd.devel.ia64,gmane.os.freebsd.current
Message-ID <[email protected]>
>From [email protected] 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
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ia64
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.