Date: Sun, 22 Jan 2017 20:43:32 +0800 From: Julian Elischer <julian@freebsd.org> To: "O. Hartmann" <o.hartmann@walstatt.org>, Mateusz Guzik <mjguzik@gmail.com> Cc: "O. Hartmann" <ohartmann@walstatt.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: r312602: panic: Panic String: __lockmgr_args: unknown lockmgr request 0x0 Message-ID: <818c4a1a-5318-e40c-64e7-77c63899e43c@freebsd.org> In-Reply-To: <20170121215140.64ec90c8@thor.intern.walstatt.dynvpn.de> References: <20170121204555.30582a5d@thor.intern.walstatt.dynvpn.de> <20170121201345.GA20930@dft-labs.eu> <20170121215140.64ec90c8@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?818c4a1a-5318-e40c-64e7-77c63899e43c>