Date: Thu, 25 Aug 2005 14:12:04 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Ulrich Spoerlein <q@galgenberg.net> Cc: freebsd-current@freebsd.org Subject: Re: kbdmux(4) freezing the system Message-ID: <bb4a86c7050825141236e9d01d@mail.gmail.com> In-Reply-To: <430E3197.9080406@savvis.net> References: <430E3197.9080406@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ulrich, > I tried using kbdmux(4) and after a lot of fiddling with rc.d/syscons > and devd.conf I worked out a solution that more or less works for me. >=20 > Sadly, in the two days I've been using kdbmux(4) I had my box freeze > suddenly several times. This almost always happened when I was using the > touchpad (and no other keyboard present). I have no panic strings or > dumps or whatsoever, since it always happened in X and somehow I can't > reproduce how to get a DDB prompt via Firewire. unfortunately its true. i was able to narrow it down on my system to ps/2 mouse and/or keyboard. basically if i use ps/2 mouse (and probably ps/2 keyboard) with kbdmux(4) i have system freeze. the solution that works for me is to _not_ use ps/2 mouse. you should also know that there is a keyboard state synchronization problem with kbdmux(4) (seems to be related to control/shift/alt keys) that i can reproduce, but still can not fix :( > So, are there any users of kbdmux out there? Are there any known > problems with system freezes? (I'm running RELENG_6 btw). i did not get much of a feedback, so i assume not many people are using it. =20 > I stopped using kbdmux(4) for now and not another freeze occurred, so it > strongly points to kbdmux being the culprit. yes, kbdmux(4) is definitely involved here. this is a high priority item on my todo list and as soon as i get enough free time i will look into this again. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c7050825141236e9d01d>