Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.Hawaii.Edu!ames!enews.sgi.com!news.sgi.com!su-news-hub1.bbnplanet.com!news.bbnplanet.com!newsxfer3.itd.umich.edu!news1.best.com!nntp1.ba.best.com!shell3.ba.best.com!lowtek From: lowtek@best.com (Spencer Low) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Keyboard Lockup; xload Date: 12 Mar 1997 23:56:41 GMT Organization: LowTek Creations <http://www.lowtek.com/> Lines: 21 Message-ID: <5g7frp$221@nntp1.ba.best.com> Reply-To: spencer@lowtek.com (Spencer Low) NNTP-Posting-Host: shell3.ba.best.com X-Newsreader: TIN [version 1.2 PL2] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37079 I'm running FreeBSD 2.1.6 on my Micron Millenia P100PCI system with a PS/2 mouse and keyboard, with a kernel compiled with psm0 support. Occasionally, my keyboard will totally lockup and not respond -- this usually happens at boot-up, even though I was able to send keystrokes to BootEasy to select what partition to boot from. I've also experienced keyboard lockups after exiting the kernel debugger (ddb) with the "c" command. I tried putting "options ASYNCH" in my kernel config file, but that hasn't helped. What is causing these keyboard lock-ups? In another note, the standard installation of the X Windows stuff with FreeBSD 2.1.6 installed xload, but it was not set-g-id in the kmem group. Is this a major security risk (for xload to be set-g-id to kmem), or is this just an oversight of the FreeBSD installation? Thanks, Spencer -- Spencer Low <spencer@lowtek.com> LowTek Creations <http://www.lowtek.com/>