>Number:         17512
>Category:       kern
>Synopsis:       /dev/wskbd and /dev/wsmouse don't update mtime when events occur
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 07 16:21:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Luke Mewburn
>Release:        NetBSD 1.6_BETA3
>Organization:
Luke Mewburn  <lukem@wasabisystems.com>  http://www.wasabisystems.com
Luke Mewburn     <lukem@netbsd.org>      http://www.netbsd.org
Wasabi Systems - NetBSD hackers for hire
NetBSD - the world's most portable UNIX-like operating system
>Environment:
System: NetBSD argo.mewburn.net 1.6_BETA3 NetBSD 1.6_BETA3 (ARGO from GENERIC-$Revision: 1.491 $) #1: Fri Jun 28 08:52:16 EST 2002 lukem@argo.mewburn.net:/var/scratch/obj.i386/usr/src/sys/arch/i386/compile/ARGO i386
Architecture: i386
Machine: i386
>Description:
	screenblank(1) checks if the atime or mtime of "input" devices
	has changed to determine if it should "unblank" the display.
	the default input devices are /dev/wskbd and /dev/wsmouse (the
	wsmux devices).  these don't update their atime or mtime when
	events (such as an arbitrary keypress) occur.

>How-To-Repeat:
	start up screenblank(1) on a wscons framebuffer. 
	notice that pressing a CTRL key or moving the mouse doesn't
	unblank the screen.  add "-i /dev/ttyE0" to rc.conf(5)'s
	screenblank_flags so that at least screen output results in
	the unblanking if you press a key that results in a character
	output.

>Fix:
	no idea.  i tried to work out how (pseudo) devices update
	their [acm]time values and got lost in the kernel :(
>Release-Note:
>Audit-Trail:
>Unformatted: