From owner-freebsd-hackers Thu Aug 15 19:05:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA20234 for hackers-outgoing; Thu, 15 Aug 1996 19:05:27 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA20214; Thu, 15 Aug 1996 19:05:22 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA01893; Thu, 15 Aug 1996 18:56:43 -0700 From: Terry Lambert Message-Id: <199608160156.SAA01893@phaeton.artisoft.com> Subject: Re: locking up To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Thu, 15 Aug 1996 18:56:43 -0700 (MST) Cc: jlemon@americantv.com, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG In-Reply-To: <199608160155.LAA16474@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 16, 96 11:25:53 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Yet I still get random lockups. :-( > > LED state is updated at every VC switch, even if the LEDs are all off. > > The biggest problem with automating a recovery from the hung state is that > it's almost impossible for the keyboard driver to tell the difference > between a hung keyboard and a user off making a coffee. > > None of the reset methods that I know of are safe enough to run on a > regular basis - you'd have too many people complaining about losing > keystrokes. I guess you could have a 'no LEDs' option for syscons > for people who lock up too regularly... Yet, DOS does it. I suspect that it would be a good idea to disassemble the ROMs for the keyboard handling code on machines which misbehave. This will tell you once and for all what the problem is for that machine. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.