From nobody  Sun Jun  1 07:39:16 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA23019;
          Sun, 1 Jun 1997 07:39:16 -0700 (PDT)
Message-Id: <199706011439.HAA23019@hub.freebsd.org>
Date: Sun, 1 Jun 1997 07:39:16 -0700 (PDT)
From: dmm125@bellatlantic.net
To: freebsd-gnats-submit@freebsd.org
Subject: pause key not disabled; weird stuff when pressed
X-Send-Pr-Version: www-1.0

>Number:         3739
>Category:       kern
>Synopsis:       pause key not disabled; weird stuff when pressed
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jun  1 07:40:01 PDT 1997
>Closed-Date:    Fri Jul 3 02:04:13 PDT 1998
>Last-Modified:  Fri Jul  3 02:05:27 PDT 1998
>Originator:     Donn Miller
>Release:        2.2.2-RELEASE
>Organization:
>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 file will resume scrolling only after pressing 'pause' key
2 or 3 times.  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 is restored.
>How-To-Repeat:
cat a really big file, then press 'pause'.  Try pressing 'pause' key
again to resume scrolling ( > 3 times).  Then try pressing some keys.
There should be some weird stuff happening. Then:  if you press ^C,
you may get logged out.  If you press 'scroll lock' several times
THEN ^C (may need several ^C's), the terminal will come back.
>Fix:
Add a patch to the syscons driver that disables 'pause' or modifies
the functionality of it.  This may only be a problem on certain
keyboards.
>Release-Note:
>Audit-Trail:

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: dmm125@bellatlantic.net
Cc: freebsd-gnats-submit@freebsd.org, yokota@freebsd.org
Subject: Re: kern/3739: pause key not disabled; weird stuff when pressed 
Date: Mon, 02 Jun 1997 11:59:12 +0900

 >>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? How does your system behave if you activate
 the `back scroll' mode by pressing the `Scroll Lock' key instead of
 the `Pause' key. Are you using the default, built-in US keymap, or do
 you load any keymap?
 
 Kazu

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
 

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:59:00 +0000 (GMT)

 On Mon, 2 Jun 1997, Donn Miller wrote:
 
 > 
 > 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.
 
 I think I know what happens here:  on (U.S.) PC's, the 'pause' key is tied
 to a particular BIOS routine that pauses whatever output is being sent to
 the screen.  However, the syscons driver wants to do another routine when
 this key is pressed.  Maybe the interaction between the BIOS activities
 and the syscons driver is causing weird things to happen.
 
 This is similar to the BIOS routine that reboots the machine when
 cntrl-alt-delete is pressed.  
 
 A possible solution would be to 'trap' the pause key to prevent the BIOS
 from intervening, if this is what's happening.  Then, the syscons driver
 would be free to assign the sroll-back routine to the pause key.
 
 I think this because I think under plain DOS, many BIOS activities are
 left alone to their default values, and the pause key does a particular
 thing there.
 
 Hopefully, I have been a little more clear on this.
 
 Thanks,
 
 	Donn (dmm125@bellatlantic.net)
 

From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: Donn Miller <dmm125@bellatlantic.net>
Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: kern/3739: pause key not disabled; weird stuff when pressed 
Date: Mon, 02 Jun 1997 14:14:34 +0900

 >I think I know what happens here:  on (U.S.) PC's, the 'pause' key is tied
 >to a particular BIOS routine that pauses whatever output is being sent to
 >the screen.  However, the syscons driver wants to do another routine when
 >this key is pressed.  Maybe the interaction between the BIOS activities
 >and the syscons driver is causing weird things to happen.
 
 No. This isn't the case here. BIOS is not involved in any way. While
 FreeBSD is running, the keyboard BIOS won't get control; we are in
 the protected mode :-)
 
 Kazu
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Fri Jul 3 02:04:13 PDT 1998 
State-Changed-Why:  
As part of our PR audition campaign, this PR has been closed.  The subject 
seems to be in the category of pilot error and consequently I will now 
close the PR. 

We apologize for late response to this PR. 

>Unformatted:
