From nobody  Tue Sep  2 11:04:05 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA18755;
          Tue, 2 Sep 1997 11:04:05 -0700 (PDT)
Message-Id: <199709021804.LAA18755@hub.freebsd.org>
Date: Tue, 2 Sep 1997 11:04:05 -0700 (PDT)
From: atrens@nortel.ca
To: freebsd-gnats-submit@freebsd.org
Subject: X drops characters/locks up keyboard when run from `xdm'
X-Send-Pr-Version: www-1.0

>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:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep  2 11:10:01 PDT 1997
>Closed-Date:    Sat Sep 8 01:38:02 PDT 2001
>Last-Modified:  Sat Sep 08 01:38:11 PDT 2001
>Originator:     Andrew Atrens
>Release:        2.2.2 and 3.0-SNAP-Aug08 with Xfree86 3.3 and 3.3.1
>Organization:
self
>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 ).
>Release-Note:
>Audit-Trail:

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: atrens@nortel.ca
Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: kern/4454: X drops characters/locks up keyboard when run from `xdm' 
Date: Tue, 04 Nov 1997 20:22:41 +0900

 >>Number:         4454
 >>Category:       kern
 >>Synopsis:       X drops characters/locks up keyboard when run from `xdm'
 [...]
 >>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...
 
 Strange.
 
 >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. 
 
 Was it possible to switch to a text console by pressing Ctl-Alt-Fx?
 How about Ctl-Alt-Backspace? Did it kill the X server?
 
 >The mouse, disk and other things seem fine. I
 >can open new windows and cut and paste between them... just no keyboard
 >i/o :( .
 
 Do you use a serial mouse or a PS/2 mouse?
 
 >When I run X from a `startx' everything works perfectly.
 
 Hmm. Even more puzzling.
 
 Kazu

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: atrens@nortel.ca
Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: kern/4454: X drops characters/locks up keyboard when run from `xdm' 
Date: Mon, 22 Dec 1997 11:39:26 +0900

 >>Number:         4454
 >>Category:       kern
 >>Synopsis:       X drops characters/locks up keyboard when run from `xdm'
 [snip]
 >>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 ).
 
 Looking at your PR again, I start wondering if this is something to do
 with power management of the motherboard.
 
 You see, keyboard LESs go off when lock-up happens. It's difficult to
 imagine why either the X server or the console driver automatically do
 so (the console driver syscons certainly doesn't do that). Besides the
 X server is working properly sans keyboard I/O.
 
 I suspect that power to the keyboard is somehow cut and the keyboard
 stops working. Aside from the possibilty of hardware problems, it must
 be power management function in the mother board BIOS which is
 turning off the keyboard interface. How is your power management set
 up in BIOS?
 
 What do you think?
 
 Kazu
 yokota@freebsd.org
 
 

From: Shell Shock <shellshock@rockford.com>
To: freebsd-gnats-submit@freebsd.org, atrens@nortel.ca
Cc:  
Subject: Re: kern/4454: X drops characters/locks up keyboard when run from `xdm'
Date: Thu, 09 Sep 1999 18:56:04 -0500

 This also happens with  > wdm < as well as xdm, im not sure about the
 motherboard, but its not ASUS for sure ;) if you've gotten anywhere with
 this, please reply to me
 
     Kyle Martin
     shellshock@rockford.com
 
 
 
 

From: Vasek Petricek <petricek@kolej.mff.cuni.cz>
To: freebsd-gnats-submit@FreeBSD.org, atrens@nortel.ca
Cc: yokota@FreeBSD.org
Subject: Re: kern/4454: X drops characters Flocks up keyboard when run from
 xdm
Date: Wed, 8 Mar 2000 00:07:23 +0100 (CET)

 I just tried to switch to xdm and encountered the same problem. It seems
 to be caused by hitting more meta keys at once - Ctrl + Alt + Shift. The
 keyboard freezes completely - Nothing of the following works:
 
 Ctrl+Backspace
 Ctrl+Alt+Del
 Ctrl+Alt+Fx
 
 Sometimes it seems like Ctrl has stayed pressed and so the functionality
 of mouse is changed too.
 
 The only tthing I found on deja.com was a some similar problem under
 OpenBSD - kern/1115.
 
 System:
 FreeBSD 3.3-RELEASE #5: Mon Jan 24 20:18:44 CET 2000
 XFree86 3.3.5
 Motherboard: Octec
 Keyboard: Silitek
 Window manager: fvwm2
 
 Vasek Petricek
 
 
State-Changed-From-To: open->feedback 
State-Changed-By: mike 
State-Changed-When: Sat Jul 21 23:00:53 PDT 2001 
State-Changed-Why:  

Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=4454 
State-Changed-From-To: feedback->closed 
State-Changed-By: kris 
State-Changed-When: Sat Sep 8 01:38:02 PDT 2001 
State-Changed-Why:  
Feedback timeout 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=4454 
>Unformatted:
