Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Aug 2014 13:56:17 -0400 (EDT)
From:      Benjamin Kaduk <kaduk@MIT.EDU>
To:        Larry Rosenman <ler@lerctr.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: DEADLKRES crash
Message-ID:  <alpine.GSO.1.10.1408181352070.21571@multics.mit.edu>
In-Reply-To: <20140818152138.GA3481@borg.lerctr.org>
References:  <20140818152138.GA3481@borg.lerctr.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Aug 2014, Larry Rosenman wrote:

> I got the following:
>
> borg.lerctr.org dumped core - see /var/crash/vmcore.8
>
> Mon Aug 18 07:30:42 CDT 2014
>
> FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #63 r269784M: Sun Aug 10 12:33:07 CDT 2014     root@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER  amd64
>
> panic: deadlkres: possible deadlock detected for 0xfffff8002abeb000,
> blocked for 1800926 ticks
[...]
> Current language:  auto; currently minimal
> (kgdb)
>
> What info do folks need?

Most useful would be the "show alllocks" from DDB.  Getting the lock
information from kgdb is rather more annoying, though jhb has some gdb
scripts which help. (http://people.freebsd.org/~jhb/gdb/)  I guess the
'allchains' command from gdb6 is the one in question, but it's been a
while since I tried to use these scripts.

-Ben



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1408181352070.21571>