[6853] in Hotline Meeting
Re: mouse on jabberwock 24-618
daemon@ATHENA.MIT.EDU (sethf@Athena.MIT.EDU)
Fri Nov 22 10:44:42 1991
From: sethf@Athena.MIT.EDU
Date: Fri, 22 Nov 91 10:44:47 -0500
To: hotline@Athena.MIT.EDU
> In regards to the mouse on the RT called jabberwock in 24-618, we had
> DEC Field Service, (DEC services the contract systems at Athena now-
> including RTs), and they could not find a problem with the mouse.
> If you feel that the problem has not been corrected, please let hotline
> know. (And also the problems that the mouse is causing.)
The symptoms of the problem are not reproducable on demand.
Rebooting the machine will fix it for a while, but after some time (on
the order of tens of minutes), the mouse will go bad again. This has
happened to two people within the last day. It's definitely located in
the mouse, as the problems have followed it when it switched machines.
It may have finally given up the ghost, as at the moment the machine
(jabberwock) hasn't completely recovered from the last freeze. It won't
display an X screen and /usr/adm/messages is full of repeated messages
of the sort:
Nov 22 10:30:42 jabberwock vmunix: klsint: Error code detected 0xea.
Nov 22 10:30:42 jabberwock vmunix: Uart acknowledge timed out.
Nov 22 10:30:42 jabberwock vmunix: reset_mouse: Bad block count = 255
Nov 22 10:30:42 jabberwock vmunix: reset_mouse: Mouse didn't reset (ff)
================
Seth Finkelstein
sethf@athena.mit.edu
