Date: Mon, 18 Aug 2014 13:05:42 -0500 From: Larry Rosenman <ler@lerctr.org> To: Benjamin Kaduk <kaduk@mit.edu> Cc: freebsd-current@freebsd.org Subject: Re: DEADLKRES crash Message-ID: <68bfaf46e716f5fa317896b4bb89b40b@thebighonker.lerctr.org> In-Reply-To: <alpine.GSO.1.10.1408181352070.21571@multics.mit.edu> References: <20140818152138.GA3481@borg.lerctr.org> <alpine.GSO.1.10.1408181352070.21571@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014-08-18 12:56, Benjamin Kaduk wrote: > 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 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" after source'ing the above, and typing allchains, it sits and spins, but no output... :( Ideas? I **CAN** give SSH access.... -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: ler@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?68bfaf46e716f5fa317896b4bb89b40b>