Date: Fri, 19 Oct 2018 23:42:45 +0300 From: Vladimir Kondratyev <vladimir@kondratyev.su> To: Greg V <greg@unrelenting.technology>, Warner Losh <imp@bsdimp.com> Cc: FreeBSD X11 mailing list <freebsd-x11@freebsd.org> Subject: Re: Graphics Team Meeting notes from 2018-10-17 Message-ID: <70ea687c-2657-f5e8-9462-f02a0f4f326f@kondratyev.su> In-Reply-To: <1539971696.1750.0@smtp.migadu.com> References: <CANCZdfrGk3MF3FXLnUtVZPizrYHJCABd2b=Xn8NjbOL3qzQ3Yg@mail.gmail.com> <1539971696.1750.0@smtp.migadu.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19.10.2018 20:54, Greg V wrote: >> =A0=A0 input stack >> =A0=A0 - >> =A0=A0=A0=A0=A0 There are reports of regression with things like ddb> = prompt that >> =A0=A0=A0=A0=A0 need to be investigated before people will be comforta= ble >> turning EVDEV on >> =A0=A0=A0=A0=A0 by default in GENERIC. >> =A0=A0=A0=A0=A0 - > > A fix for the keyboard deadlock has been posted back in April: > https://reviews.freebsd.org/D15070 > > I've been running EVDEV on two machines since EVDEV was a thing > (without the patch) and never encountered any deadlocks or any other > bugs. > Being an author of D15070, I want to add my 2 cents to discussion: I have never seen this deadlock "in a wild" yet. I have to insert DELAY()s into locked regions of EVDEV to trigger it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?70ea687c-2657-f5e8-9462-f02a0f4f326f>