Date: Wed, 11 Sep 1996 06:15:48 +1000 From: Bruce Evans <bde@zeta.org.au> To: cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-sys@freefall.freebsd.org, peter@freefall.freebsd.org Subject: Re: cvs commit: src/sys/i386/isa syscons.c Message-ID: <199609102015.GAA02194@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
> Modified: sys/i386/isa syscons.c > Log: > Hack workaround XFree86 switching failure when used with /dev/sysmouse > and xdm, possibly in general. > > What was happening was that the server was doing a tcsetattr(.. TCSADRAIN) > on the mouse fd after a write. Since /dev/sysmouse had a null t_oproc, > the drain failed with EIO. Somehow this spammed XFree86 (!@&^#%*& binary > release!!), and the driver was left in a bogus state (ie: switch_in_progress > permanently TRUE). This reminds me of what happens when crtscts is locked on for the mouse. My mouse doesn't supply CTS, so draining takes forever. Killing XFree86 require kill -9 from somewhere other than the console IIRC, and leaves the console driver in a bogus state. Some graphics cards go into a strange state when XFree86 is started up again in this state. Sometimes XFree86 manages to kill itself after a timeout, but the console driver is left in a bogus state. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609102015.GAA02194>