From owner-freebsd-bugs@freebsd.org  Mon Dec  4 04:27:31 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2FC27DED157
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon,  4 Dec 2017 04:27:31 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1DB9177B12
 for <freebsd-bugs@FreeBSD.org>; Mon,  4 Dec 2017 04:27:31 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vB44RUDE092045
 for <freebsd-bugs@FreeBSD.org>; Mon, 4 Dec 2017 04:27:30 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 210446] vt(4) when switching between virtual consoles there is
 a 4 second hesitation in graph mode.
Date: Mon, 04 Dec 2017 04:27:30 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: vt
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: sblachmann@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-210446-8-1FvDaZmsjl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210446-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-210446-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Dec 2017 04:27:31 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210446

Stefan B. <sblachmann@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sblachmann@gmail.com

--- Comment #2 from Stefan B. <sblachmann@gmail.com> ---
I also confirm that bug.

CAUSE:
The setvideomode stuff is unnecessarily called.
Highly annoying, because mode gets reset, with sync stopping, monitor blank=
ing
and taking some time to lock in its PLL again.
One reason why I use sc.

HOW TO FIX:
When changing from one vt to another, do NOT do an unnecessary call to
setvideomode BIOS function. This is ONLY necessary when switching between X=
 and
vts.
Just blit the framebuffer with the contents of the newly selected VT.

--=20
You are receiving this mail because:
You are the assignee for the bug.=