From owner-freebsd-current@freebsd.org Wed Feb 24 12:32:51 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD3CFAB28BA for ; Wed, 24 Feb 2016 12:32:51 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from relay16.nicmail.ru (relay16.nicmail.ru [195.208.5.134]) by mx1.freebsd.org (Postfix) with ESMTP id 94EFF1A78 for ; Wed, 24 Feb 2016 12:32:50 +0000 (UTC) (envelope-from afiskon@devzen.ru) Received: from [31.177.73.134] (port=36444 helo=nicmail.ru) by f17.mail.nic.ru with esmtp (Exim 5.55) (envelope-from ) id 1aYYcT-000MJv-3O for freebsd-current@freebsd.org; Wed, 24 Feb 2016 15:32:41 +0300 Received: from [10.0.6.225] (account afiskon@devzen.ru HELO fujitsu) by fcgp20.nicmail.ru (CommuniGate Pro SMTP 5.2.3) with ESMTPA id 78767747 for freebsd-current@freebsd.org; Wed, 24 Feb 2016 15:32:40 +0300 Received: from [93.174.131.138] (account afiskon@devzen.ru HELO fujitsu) by proxy05.mail.nic.ru (Exim 5.55) with id 1aYYcS-0000NA-Ol for freebsd-current@freebsd.org; Wed, 24 Feb 2016 15:32:40 +0300 Date: Wed, 24 Feb 2016 15:30:07 +0300 From: Eax Melanhovich To: freebsd-current@freebsd.org Subject: Lock order reversal in CURRENT Message-ID: <20160224153007.79bcf4ec@fujitsu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Feb 2016 12:32:52 -0000 Hello. Yesterday I built a kernel and world using master branch (6a8922d3) of FreeBSD GitHub repository (a mirror of SVN as I understand?). Today I got a "lock order reversal" report: http://i.imgur.com/jDZ4A3O.png According to this FAQ it could be a sign of a deadlock: https://www.freebsd.org/doc/faq/troubleshoot.html#idp63366608 Do I have to report this issue anywhere except freebsd-current@ ? -- Best regards, Eax Melanhovich http://eax.me/