From nobody  Tue Mar  3 02:18:07 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA15242;
          Tue, 3 Mar 1998 02:18:07 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199803031018.CAA15242@hub.freebsd.org>
Date: Tue, 3 Mar 1998 02:18:07 -0800 (PST)
From: xcene@c2i.net
To: freebsd-gnats-submit@freebsd.org
Subject: VIDCONTROL VGA_80x60 resets PC completely w/o warning
X-Send-Pr-Version: www-1.0

>Number:         5907
>Category:       bin
>Synopsis:       VIDCONTROL VGA_80x60 resets PC completely w/o warning
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar  3 02:20:01 PST 1998
>Closed-Date:    Tue May 19 02:32:35 PDT 1998
>Last-Modified:  Tue May 19 02:33:38 PDT 1998
>Originator:     Frode E. Moe
>Release:        FreeBSD 2.2.5-STABLE, CVSup'ed till yesterday
>Organization:
N/A
>Environment:
FreeBSD beauty.net 2.2.5-STABLE FreeBSD 2.2.5-STABLE #0: Tue Mar  3 10:09:44 CET 1998    root@beauty.net:/usr/src/sys/compile/BEAUTY  i386
>Description:
Previously I filed a bugreport about VIDCONTROL VGA_80x50 using the 8x14 font instead of the 8x8, visible because  1. only upper half of font was displayed, and 2. changing the 8x14 on the fly while in the so-called VGA_80x50 mode changed the displayed font. I was advised to CVSup and rebuild the syscons stuff; well, I did a 'make world' last night. The problem seems to have gotten worse; if I issue a vidcontrol VGA_80x60 as a normal user, my PC resets completely, without warning, without syncing the disks or anything.

In DOS, I can set 80x50 textmode properly with this assembly snippet:
mov ax, 1112h / xor bl, bl / int 10h
>How-To-Repeat:
'vidcontrol VGA_80x60' at any time; resets completely
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: yokota 
State-Changed-When: Tue May 19 02:32:35 PDT 1998 
State-Changed-Why:  
Fix is now in both 3.0-CURRENT (syscons.c 1.258) and 2.2-STABLE (syscons.c 
1.182.2.33.) 
>Unformatted:
