*BSD News Article 29945


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!foxhound.dsto.gov.au!fang.dsto.gov.au!yoyo.aarnet.edu.au!news.adelaide.edu.au!news.cs.su.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!EU.net!sun4nl!news.nic.surfnet.nl!utciva.civ.utwente.nl!infnews.cs.utwente.nl!olah
From: olah@cs.utwente.nl (Andras Olah)
Subject: Re: Keyboard lockup problem under FreeBSD
Message-ID: <1994Apr22.125900@cs.utwente.nl>
Keywords: FreeBSD 1.1BETA, keyboard, lockup
Sender: usenet@cs.utwente.nl
Nntp-Posting-Host: utis156.cs.utwente.nl
Organization: Univ. of Twente, Dept. of Comp. Sci.
References:  <1994Apr21.135939.368@ic.simbirsk.su>
Date: Fri, 22 Apr 1994 10:59:00 GMT
Lines: 25

In article <1994Apr21.135939.368@ic.simbirsk.su>, sm@ic.simbirsk.su (Serge Mikhailov) writes:
[ ... ]
|>    After each ~5 minutes the keyboard (its controller, I mean) lockups. 
|> Plugging/unplugging is helpless, but it can be reseted by SYSCONS. (For 
|> example: syscons -r fast </dev/vga). It can be done by "cron" or "rsh" from
|> remote computer.

I've experienced the same problem under 1.1BETA.  It usually happens to me if
I'm using vi in an xterm while cron starts a job.  Using a wm menu to switch
to another VT solves the problem.

|>    Does someone encountered something likes that? May be it can be fixed
|> by hacking the syscons driver?
|> 
|> 
|> 		Thanks in advance, SM.
|>    
|> -- 
|> **************************************************************
|> *  Serge N. Mikhailov, INFOCOM Center ltd, Simbirsk, Russia  *
|> *  E-mail: sm@ic.simbirsk.su       Phone: +7(8422)-32-72-71  *
|> **************************************************************

-- 
  Andras Olah