Re: DEADLKRES crash

From: Ryan Stone <rysto32_at_gmail.com>
Date: Mon, 18 Aug 2014 16:45:04 -0400
On Mon, Aug 18, 2014 at 11:21 AM, Larry Rosenman <ler_at_lerctr.org> 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_at_borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER  amd64
>
> panic: deadlkres: possible deadlock detected for 0xfffff8002abeb000, blocked for 1800926 ticks
>
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "amd64-marcel-freebsd"...
>
> Unread portion of the kernel message buffer:
> panic: deadlkres: possible deadlock detected for 0xfffff8002abeb000, blocked for 1800926 ticks
>
> cpuid = 3
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe100bff1a10
> kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe100bff1ac0
> vpanic() at vpanic+0x126/frame 0xfffffe100bff1b00
> panic() at panic+0x43/frame 0xfffffe100bff1b60
> deadlkres() at deadlkres+0x35c/frame 0xfffffe100bff1bb0
> fork_exit() at fork_exit+0x84/frame 0xfffffe100bff1bf0
> fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe100bff1bf0
> --- trap 0, rip = 0, rsp = 0xfffffe100bff1cb0, rbp = 0 ---
> Uptime: 7d14h14m38s

The first thing that I'd like to see is (in kgdb):

set $td=(struct thread)0xfffff8002abeb000
tid $td->td_tid
bt

That will show us the backtrace of the thread that was blocked for so long.
Received on Mon Aug 18 2014 - 18:45:05 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:51 UTC