From owner-freebsd-current@freebsd.org  Sun Jan 22 12:43:44 2017
Return-Path: <owner-freebsd-current@freebsd.org>
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 4B8C9CB059C
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 22 Jan 2017 12:43:44 +0000 (UTC)
 (envelope-from julian@freebsd.org)
Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "vps1.elischer.org",
 Issuer "CA Cert Signing Authority" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 1FCC5C8
 for <freebsd-current@freebsd.org>; Sun, 22 Jan 2017 12:43:43 +0000 (UTC)
 (envelope-from julian@freebsd.org)
Received: from Julian-MBP3.local
 (ppp121-45-228-247.lns20.per1.internode.on.net [121.45.228.247])
 (authenticated bits=0)
 by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v0MChcdV059414
 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
 Sun, 22 Jan 2017 04:43:41 -0800 (PST)
 (envelope-from julian@freebsd.org)
Subject: Re: r312602: panic: Panic String: __lockmgr_args: unknown lockmgr
 request 0x0
To: "O. Hartmann" <o.hartmann@walstatt.org>, Mateusz Guzik <mjguzik@gmail.com>
References: <20170121204555.30582a5d@thor.intern.walstatt.dynvpn.de>
 <20170121201345.GA20930@dft-labs.eu>
 <20170121215140.64ec90c8@thor.intern.walstatt.dynvpn.de>
Cc: "O. Hartmann" <ohartmann@walstatt.org>,
 FreeBSD CURRENT <freebsd-current@freebsd.org>
From: Julian Elischer <julian@freebsd.org>
Message-ID: <818c4a1a-5318-e40c-64e7-77c63899e43c@freebsd.org>
Date: Sun, 22 Jan 2017 20:43:32 +0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <20170121215140.64ec90c8@thor.intern.walstatt.dynvpn.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jan 2017 12:43:44 -0000

On 22/01/2017 4:51 AM, O. Hartmann wrote:
> Am Sat, 21 Jan 2017 21:13:49 +0100
> Mateusz Guzik <mjguzik@gmail.com> schrieb:
>
>> On Sat, Jan 21, 2017 at 08:45:55PM +0100, O. Hartmann wrote:
>>> The most recent CURRENT panics spontanously and crashes with the error message:
>>>
>>>   
>>> Panic String: __lockmgr_args: unknown lockmgr request 0x0
>>>    
>> That's a braino in r312600, will be fixed shortly.
>>
> ??? What is a "braino"?
>
it's like a typo but more in the head than in the fingers.

The sort of error you make when your wife/girlfriend/boss/kids 
distract you right in the middle of some bit of code and you forget 
that you just decided to reverse the sense of the conditional, and 
complete the rest of the code backwards.

Some of us older folks don't need an external source of confusion.