From owner-freebsd-bugs  Sun Dec 21 18:40:04 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA18607
          for bugs-outgoing; Sun, 21 Dec 1997 18:40:04 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA18574;
          Sun, 21 Dec 1997 18:40:02 -0800 (PST)
          (envelope-from gnats)
Date: Sun, 21 Dec 1997 18:40:02 -0800 (PST)
Message-Id: <199712220240.SAA18574@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Subject: Re: kern/4454: X drops characters/locks up keyboard when run from `xdm' 
Reply-To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/4454; it has been noted by GNATS.

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