Date: Fri, 16 Aug 1996 11:55:03 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: terry@lambert.org (Terry Lambert) Cc: msmith@atrad.adelaide.edu.au, jlemon@americantv.com, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: locking up Message-ID: <199608160225.LAA16667@genesis.atrad.adelaide.edu.au> In-Reply-To: <199608160156.SAA01893@phaeton.artisoft.com> from "Terry Lambert" at Aug 15, 96 06:56:43 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert stands accused of saying: > > > > 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. DOS doesn't VC switch. The keyboard code I've worked on (at the keyboard end), _specifically_ hangs around after a key that it thinks will generate a LED update has been pressed, waiting for the update so that it doesn't collide. (Mind you, this code also snooped for collisions and generally did a fairly good job of avoiding them). > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608160225.LAA16667>