From gvs@road.yandex.ru  Wed Jun  9 07:19:28 2004
Return-Path: <gvs@road.yandex.ru>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C9C4A16A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; Wed,  9 Jun 2004 07:19:28 +0000 (GMT)
Received: from road.yandex.ru (road.yandex.ru [213.180.193.165])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2608F43D2F
	for <FreeBSD-gnats-submit@freebsd.org>; Wed,  9 Jun 2004 07:19:28 +0000 (GMT)
	(envelope-from gvs@road.yandex.ru)
Received: from road.yandex.ru (localhost.yandex.net [127.0.0.1] (may be forged))
	by road.yandex.ru (8.12.11/8.12.11) with ESMTP id i597Kgpc028816
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 9 Jun 2004 11:20:42 +0400 (MSD)
	(envelope-from gvs@road.yandex.ru)
Received: (from gvs@localhost)
	by road.yandex.ru (8.12.11/8.12.11/Submit) id i597Kft2028815;
	Wed, 9 Jun 2004 11:20:41 +0400 (MSD)
	(envelope-from gvs)
Message-Id: <200406090720.i597Kft2028815@road.yandex.ru>
Date: Wed, 9 Jun 2004 11:20:41 +0400 (MSD)
From: Seva Gluschenko <gvs@rinet.ru>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: smth was broken in keyboard processing since 5.2.1-RELEASE
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         67739
>Category:       i386
>Synopsis:       [kbd] smth was broken in keyboard processing since 5.2.1-RELEASE
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-i386
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jun 09 07:20:20 GMT 2004
>Closed-Date:    Mon Nov 01 22:18:31 GMT 2004
>Last-Modified:  Mon Nov 01 22:18:31 GMT 2004
>Originator:     Seva Gluschenko
>Release:        FreeBSD 5.2-CURRENT i386
>Organization:
Yandex LLC
>Environment:
System: FreeBSD road.yandex.ru 5.2-CURRENT FreeBSD 5.2-CURRENT #8: Fri Jun 4 13:37:30 MSD 2004 gvs@road.yandex.ru:/local/obj/local/usr/src/sys/ROAD i386


	
>Description:
	My workstation operates on 5.2-CURRENT and I noticed some misterious
	keyboard behaviour after some point in March, I think. At first, an
	attempt to switch from X to text console and type something there
	resulted to X Server crash. I didn't bothered much considering it
	just XFree86-4.3.0 (from ports) bug.

	Next I noticed occasional "cycling" of keyboard input, only <Space>
	and <Enter> was affected. It means both ignorance for the key pressed
	(lost event?) and occasional repeating (just like Enter or Space was
	pressed many times while it actually was pressed just once) which stops
	right after the next keypress.

	It was hardly to believe it's XFree86 bug again, 'cause 5.2 before March
	and 4.X didn't show that behaviour, but it happens not to often, so I
	didn't care much.

	But, I tried to update my homestation from 5.2.1-RELEASE to 5.2-CURRENT
	last evening, and the result was terrible. The key difference is my
	workstation has PS/2 keyb but my homestation has USB keyb.

	'twas alright after installworld/mergemaster/reboot, but I noticed the
	absence of acpi.ko (complained during boot process), so I did
	cd /sys/modules/acpi ; make install clean ; reboot
	Right after reboot things went really bad: the keypresses were totally
	ignored for about first ten seconds, then the first symbol entered (say, l)
	was repeated ad infinitum or, speaking determiningly, up to reset button
	pressed (because there were no more method eventually).

	I was forced to install 5.2.1 back from CD because there were no more ways
	to return the homestation under my control.

	I apologize for very long and not too technical bug report, but I just don't
	know what should I inspect to provide the needed amount of technical details.
>How-To-Repeat:
	
>Fix:

	


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: brooks 
State-Changed-When: Mon Nov 1 22:01:28 GMT 2004 
State-Changed-Why:  
Please verify that this problem exists with 5.3. You may need to set 
hint.atkbd.0.flags="0x1" at the loader prompt to have a USB keyboard at 
all, but lots of things have changed and I haven't heard other reports 
of this issue so I'm hoping it was a transient bug in -CURRENT. 

Thanks, 
Brooks 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67739 
State-Changed-From-To: feedback->closed 
State-Changed-By: brooks 
State-Changed-When: Mon Nov 1 22:17:35 GMT 2004 
State-Changed-Why:  
Submitter reports the problem has gone in 5.3: 

> Things returned to OK state at least in 5.3-BETA6 which I installed by 
> occasion when refined HDD partitioning. So you may safely close this 
> issue, thanks for taking care. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67739 
>Unformatted:
