Date: Wed, 14 Jun 2006 11:51:42 +0400 From: Yar Tikhiy <yar@comp.chem.msu.su> To: Goran Gajic <ggajic@tesla.rcub.bg.ac.yu> Cc: freebsd-current@freebsd.org, emax@freebsd.org Subject: Re: 7.0-CURRENT panics if scroll lock is pressed during boot Message-ID: <20060614075142.GA57496@comp.chem.msu.su> In-Reply-To: <Pine.LNX.4.63.0606101204120.2718@tesla.rcub.bg.ac.yu> References: <Pine.LNX.4.63.0606062002380.6606@tesla.rcub.bg.ac.yu> <20060608110046.GD69869@comp.chem.msu.su> <Pine.LNX.4.63.0606101204120.2718@tesla.rcub.bg.ac.yu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 10, 2006 at 12:08:48PM +0200, Goran Gajic wrote: > On Thu, 8 Jun 2006, Yar Tikhiy wrote: > > >It might be another issue in kbdmux, as keyboard not working in the > >debugger apparently is. You can try hitting Scroll Lock with kbdmux > >disabled in device.hints or not compiled into the kernel in order > >to see if it's the case. Should the system still panic, you'll at > >least have the keyboard working in the debugger. > > You were right: when I have disabled kbdmux in /boot/device.hints > scroll lock hitting is no longer causing panics and I have > noticed that scroll lock, caps lock and pause/break LEDs are working > again. For some reason after cvsup at the end of May LEDs stopped > working.. Did you inform Maksim Yevmenkin of this problem? He is the author of kbdmux, so he is very likely to be interested in finding and fixing such issues. I carbon copied this message to him. Perhaps he will tell if you should file a PR on the problem for future reference. -- Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060614075142.GA57496>