From owner-freebsd-bugs  Sun Jun  1 21:10:03 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA24678
          for bugs-outgoing; Sun, 1 Jun 1997 21:10:03 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA24658;
          Sun, 1 Jun 1997 21:10:01 -0700 (PDT)
Date: Sun, 1 Jun 1997 21:10:01 -0700 (PDT)
Message-Id: <199706020410.VAA24658@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Donn Miller <dmm125@bellatlantic.net>
Subject: Re: kern/3739: pause key not disabled; weird stuff when pressed 
Reply-To: Donn Miller <dmm125@bellatlantic.net>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

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

From: Donn Miller <dmm125@bellatlantic.net>
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Cc: freebsd-gnats-submit@freebsd.org, yokota@freebsd.org
Subject: Re: kern/3739: pause key not disabled; weird stuff when pressed 
Date: Mon, 2 Jun 1997 00:05:39 +0000 (GMT)

 On Mon, 2 Jun 1997, Kazutaka YOKOTA wrote:
 
 > >>Number:         3739
 > >>Category:       kern
 > >>Synopsis:       pause key not disabled; weird stuff when pressed
 > >>Confidential:   no
 > >>Severity:       non-critical
 > >>Priority:       medium
 > >>Responsible:    freebsd-bugs
 > >>State:          open
 > >>Class:          sw-bug
 > >>Submitter-Id:   current-users
 > >>Arrival-Date:   Sun Jun  1 07:40:01 PDT 1997
 > >>Last-Modified:
 > >>Originator:     Donn Miller
 > >>Organization:
 > >>Release:        2.2.2-RELEASE
 > >>Environment:
 > >FreeBSD myname.my.domain 2.2.2-RELEASE FreeBSD 2.2.2-RELEASE #2: Sun Jun  1 06
 > >:5
 > >3:20 GMT 1997     root@myname.my.domain:/usr/src/sys/compile/CUSTOM  i386
 > >>Description:
 > >The pause key is not disabled on the AT keyboard.  When 'pause' is hit
 > >(like during 'cat' of a large file) some weird stuff happens.
 > 
 > The console driver `syscons' has the `back-scroll' feature which is
 > activated by the `Scroll-Lock' or `Pause' keys. When one of these keys
 > is pressed, the screen output is suspended and you can `back scroll'
 > lines recently printed on the screen. You navigate through the lines
 > with `Page-up/down', `Home', `End' and `Up/Down' keys.
 > 
 > The `Scroll Lock' LED should be on while in this mode.
 > 
 > >The file will resume scrolling only after pressing 'pause' key
 > >2 or 3 times.  
 > 
 > Just one press should bring you back to the normal output mode...
 > 
 > >After the scrolling of text is finished, the key
 > >mappings are screwed-up.  For example, pressing p is the same as
 > >'left arrow', the s key does something else, etc.  If you press ^C, the shell 
 > >exits.  If you press scroll lock about 5 times, followed by ^C, the terminal i
 > >s restored.
 > 
 > We may be seeing strange interaction between the output routine, the
 > `back scroll' routine and keyboard I/O routines.
 > 
 > Would you check the state of the `Scroll Lock' LED during the
 > phenomena you describe? 
 
 When I press pause, I can scroll up and down, but the LED does not turn
 on.  When I try to deactivate scroll-back by pressing pause a second time,
 the screen is still in scroll back mode; I have to press 'pause' an
 additional time to return my screen to normal behavior.  While it is in 
 normal behavior, I find that the 'p' key is mapped to the up arrow.  This
 is where all the weird key mappings come into play.  Pressing ^C once
 restores the key mappings.  The LED is unlit during all this.
 
 In summary:
 
 1.) Enter scroll-back - press pause key - (LED off)
 2.) can scroll up-down, etc. (LED off)
 3.) press pause again - still can scroll (LED off)
 4.) press pause again - normal screen restored, but keys-mappings "out of
 	whack"  (LED off)
 5.) press ^C once - key mappings restored. (LED off)
 
 >How does your system behave if you activate
 > the `back scroll' mode by pressing the `Scroll Lock' key instead of
 > the `Pause' key. 
     
 After pressing 'scroll lock', the scroll-lock LED comes on, and I can
 scroll up and down as usuall.  After pressing it another time, the LED
 goes out, and the screen is in the normal mode. (With no problems)
 
 Pressing the 'scroll lock' key operates the scroll-back mode properly,
 with the LED lighting at the right time/
 
 
  >Are you using the default, built-in US keymap, or do
 > you load any keymap?
 
 I normally use 'vidcontrol -r cyan black' or 'vidcontrol -r red black'
 with the built-in key map, but I use a blank screen-saver.  Pretty much
 all defaults.
 
 > 
 > Kazu
 > 
 
 	Donn Miller 
 	(dmm125@bellatlantic.net)
 		
 	412-547-9089