Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Mar 2006 17:50:09 +1030
From:      Greg 'groggy' Lehey <grog@FreeBSD.org>
To:        FreeBSD Hackers <hackers@freebsd.org>, FreeBSD Developers <developers@FreeBSD.org>
Subject:   Programs not accepting input?
Message-ID:  <20060326072009.GL25392@wantadilla.lemis.com>

next in thread | raw e-mail | index | archive | help

--9RXjJcDGNuBviZqz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

In the last month or two I've seen increasing occurrences of programs
refusing keyboard input after they've been running for a while
(between hours and days).  They still respond to the mouse.  At first
I thought it was hardware, but it happens on a number of different
machines, and only with certain programs, all of them X clients.
Here's an overview (system names are simply to show that they're
different machines).

- System echunga, running a version of the klondike game that used to
  come with the X distribution.
- System wantadilla, running firefox.  After it refuses keyboard
  input, I can open a new window with the mouse, and the new window
  accepts input.  The old one still doesn't.
- The same problem again with system teevee.

wantadilla had what I think were hardware problems a couple of weeks
ago, so I changed the entire system board and memory (but kept the
disks).  The new system is stable, but the problems continue.  echunga
and teevee have been up for months:

echunga       up  49+02:25,     1 user,   load 0.60, 0.50, 0.35
teevee        up 100+22:08,     0 users,  load 0.06, 0.31, 0.28
tvremote      up  36+21:07,     0 users,  load 0.18, 0.04, 0.01
wantadilla    up  18+02:44,     3 users,  load 0.46, 0.38, 0.49

One thing that the machines have in common is that they all run x2x
(which joins X servers).  echunga and wantadilla run one instance, and
teevee runs another instance with tvermote, which I don't think has
shown any problems.  I've been running x2x for years as well, and only
one of the machines has had a software upgrade anywhere near the time
when the problem began.  Here are the versions:

FreeBSD echunga.lemis.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Sun Feb=
  5 14:15:02 CST 2006     grog@echunga.lemis.com:/usr/obj/src/FreeBSD/6-STA=
BLE/src/sys/ECHUNGA  i386
FreeBSD teevee.lemis.com 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #4: Sun Mar =
13 14:58:24 CST 2005     grog@teevee.lemis.com:/usr/obj/src/FreeBSD/TEEVEE/=
src/sys/TEEVEE  i386
FreeBSD tvremote.lemis.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov  5 0=
4:19:18 UTC 2004     root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENER=
IC  i386
FreeBSD wantadilla.lemis.com 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Tue Jul 12=
 11:57:56 CST 2005     grog@wantadilla.lemis.com:/usr/obj/src/FreeBSD/6-CUR=
RENT/src/sys/WANTADILLA  i386

Does this ring a bell with anybody?  Any idea how to start debugging?
The fact that new firefox windows accept input suggests that it's
somewhere in X.

Greg
--=20
See complete headers for address and phone numbers.

--9RXjJcDGNuBviZqz
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFEJkCpIubykFB6QiMRAvayAJ46uTMS5ibB6P8h5lD1Z0VgjfMS0gCeOXmQ
nVrttcoXqsUWhS8OcschD98=
=UbyO
-----END PGP SIGNATURE-----

--9RXjJcDGNuBviZqz--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060326072009.GL25392>