Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Sep 1997 11:04:05 -0700 (PDT)
From:      atrens@nortel.ca
To:        freebsd-gnats-submit@FreeBSD.ORG
Subject:   kern/4454: X drops characters/locks up keyboard when run from `xdm'
Message-ID:  <199709021804.LAA18755@hub.freebsd.org>
Resent-Message-ID: <199709021810.LAA19028@hub.freebsd.org>

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

>Number:         4454
>Category:       kern
>Synopsis:       X drops characters/locks up keyboard when run from `xdm'
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep  2 11:10:01 PDT 1997
>Last-Modified:
>Originator:     Andrew Atrens
>Organization:
self
>Release:        2.2.2 and 3.0-SNAP-Aug08 with Xfree86 3.3 and 3.3.1
>Environment:
3.0 August 08 SNAP. Also seen with 2.2.2. Tried with XFree86 3.3 and 
3.3.1.
>Description:

Problems were seen on a ASUS-TX97 motherboard with 430TX chipset.

Previously I was running on an ASUS T2P4 motherboard with a 430HX 
chipset and didn't seeany of these problems...

Running X11 from an `xdm'
When `xlock -inroot -mode galaxy' is running in the root window, or
some other graphics intensive stuff is running, xterms, rxvts, and
even the xdm login window drop characters and eventually lock up the
keyboard. When the keyboard is locked up, all the keyboard leds turn
off. Pressing caps-lock, or num-lock doesn't cause the corresponding
leds to illuminate. The mouse, disk and other things seem fine. I
can open new windows and cut and paste between them... just no keyboard
i/o :( .

When I run X from a `startx' everything works perfectly.

>How-To-Repeat:

Need an ASUS TX97 motherboard with 430TX chipset.

Need FreeBSD-2.2.2 or 3.0-SNAP-Aug08.

Need XFree86 3.3 or 3.3.1

Run X from an `xdm'. Start `xlock -inroot -mode galaxy' or some similar
graphics-intensive thing in the root window. Open an xterm and start
typing away until the keyboard leds go 'off' and keyboard is locked up.
Note: if you run two or more xlocks, the keyboard lockup will occur
proportionately quicker.
>Fix:

Don't use xdm. Use startx ( this isn't a fix for everyone I guess ).
>Audit-Trail:
>Unformatted:



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