Date: Sun, 12 Apr 2009 14:53:41 -0700 From: Maksim Yevmenkin <emax@freebsd.org> To: Alexander Kabaev <kabaev@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: svn commit: r190857 - head/sys/dev/kbdmux Message-ID: <bb4a86c70904121453o4af4cd3duf1fb55a5aea46df9@mail.gmail.com> In-Reply-To: <20090412154413.1e250cc7@kan.dnsalias.net> References: <200904082052.n38KqU9p075633@svn.freebsd.org> <20090412170335.5a8a3169@fabiankeil.de> <bb4a86c70904121000p60b48632q22a5b92fc791f4f8@mail.gmail.com> <20090412154413.1e250cc7@kan.dnsalias.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 12, 2009 at 12:44 PM, Alexander Kabaev <kabaev@gmail.com> wrote: > On Sun, 12 Apr 2009 10:00:35 -0700 > Maksim Yevmenkin <emax@freebsd.org> wrote: > >> On Sun, Apr 12, 2009 at 8:03 AM, Fabian Keil >> >> > How about turning this into a compile-time or sysctl option >> > or at least mentioning the change in /usr/src/UPDATING? >> >> i do not believe that compile-time nor sysctl option is the right >> choice here as it is never allowed to use locks in low-level keyboard >> drivers. entry in UPDATING is probably a good idea. >> >> > With this commit, providing the geli key phrase on >> > boot is impossible on my AMD64 dual core system. >> >> right, i really hate to say this, but the amount of bug reports, lor's >> etc.that were submitted after this change is far more (imo) than >> amount of people that ran relatively uncommon setup with encrypted >> root (which, btw, prompted the original commit). of course, there is >> no question, it has to be fixed. > > This also affects DDB prompts, correct? What is the timeframe for > fixing this? not really, imo. in ddb prompts interrupts are disabled (as i understand it). as far as fixing it, it could be as simple as the patch i sent in my previous email. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70904121453o4af4cd3duf1fb55a5aea46df9>