Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.edu.au!news.apana.org.au!cantor.edge.net.au!news.teragen.com.au!news.access.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!agate!news.ucsc.edu!ese.UCSC.EDU!not-for-mail From: tgs@cats.ucsc.edu (Thomas Gunnar Sparks) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Keyboard lockups Date: 3 Mar 1997 01:27:33 GMT Organization: University of California, Santa Cruz Lines: 29 Message-ID: <5fd9e5$bbe@darkstar.ucsc.edu> References: <5f5e98$ekp$1@Venus.mcs.net> NNTP-Posting-Host: ese.ucsc.edu X-Newsreader: TIN [UNIX 1.3 BETA-950824-16colors PL0] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36430 Font (font@MCS.COM) wrote: : Every so often, under FreeBSD 2.1.6.1, the keyboard locks up for no : apparent reason. No key elicits a response, and if a screensaver is : activate, it will run after the specified time period as if no : keyboard input had been received. Logins across the network are : unaffected, and I can remotely login and shut down the computer. This has happened to me a couple times... I thought for a while it was my cheap keyboard, but I'm not sure.. I'm going to put my other keyboard on and see if it happens again? I think this problem has manifested itself to me 3-4 times on my system.. I usually login remotely and reboot once I get the problem... : My configuration is: Dell Dimension P75t, 16M RAM, AHA2940AU. The : keyboard is a PS/2 style. The mouse is a PS/2 style (activated in : GENERIC kernel, but unused as yet since I haven't installed X). : Network is 3C595. No errors noted on startup. My config is : Intel Endeavor MB, P166, 48MB of ram, Cheapo Win95 Mitsumi Keyboard, IDE Disks, Advansys PCI SCSI Card (pleading for drivers) I would usually notice this problem when using the CTRL-ALT-F? vtty switching... So far it has only happened to me in X... : I checked in Deja News and noted that a few other people had related : problems, but that no responses to their queries was evident. I posted about this myself, but I didn't get any response either.. I'm going to look through the mailing list archives again just to make sure there are no answers about this...