Date: Mon, 12 Aug 1996 12:24:19 +0100 (BST) From: Doug Rabson <dfr@render.com> To: Jim Lowe <james@miller.cs.uwm.edu> Cc: freebsd-current@freebsd.org, wangel@wgrobez1.remote.louisville.edu Subject: Re: locking up Message-ID: <Pine.BSI.3.95.960812122157.10082W-100000@minnow.render.com> In-Reply-To: <199608061721.MAA23320@miller.cs.uwm.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 6 Aug 1996, Jim Lowe wrote: > > From: Gary Roberts <wangel@wgrobez1.remote.louisville.edu> > > To: freebsd-current@freebsd.org > > Subject: locking up > > > > Sometimes, at no predetermined time, without warning, when switching VC's, > > I'll lock up. FreeBSD doesn't lockup just the keyboard, and I can only fix > > it by rebooting. > > > > A while ago Bruce Evans had posted this, if you run it, it > unlocks the keyboard. I don't know why this happens or why > it hasn't been fixed. The way I run it is to remote login > from some other machine. > > -Jim > > > Date: Tue, 20 Feb 1996 23:52:48 +1100 > > From: Bruce Evans <bde@zeta.org.au> > > Message-Id: <199602201252.XAA23329@godzilla.zeta.org.au> > > To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de > > Subject: Re: Keyboard lockout on 2.x.x > > > > To fix it if you can log in as root from another host, try > > > > echo "set ipending=2" | gdb -k -w /kernel /dev/mem > > > > This fakes a keyboard interrupt. This happens to me whenever I break into DDB. The ipending thing fixes it. I guess this motherboard manages to misplace the keyboard interrupt while I am in the debugger :-(. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.960812122157.10082W-100000>