linux-kernel - "Glove box" BIOS patch causes boot flicker

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.01.1009220135380.25692@obet.zrqbmnf.qr>
Date:	Wed, 22 Sep 2010 01:53:09 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	hpa@...ux.intel.com
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: "Glove box" BIOS patch causes boot flicker

Hi,

some (long) time ago, I noticed a change whereby at the start of Linux 
(before any log messages are output) the monitor would do one reset on 
x86/VGA (the classic modes à la 80x25 - no fbdev stuff). It is only now 
that I found enough joy to revisit this.

Between 2.6.30 and 2.6.31, commit cf06de7b9cdd was introduced by you, 
which I have bisected the problem down to.

commit cf06de7b9cdd3efee7a59dced1977b3c21d43732
Author: H. Peter Anvin <hpa@...ux.intel.com>
Date:   Wed Apr 1 18:20:11 2009 -0700

    x86, setup: "glove box" BIOS interrupts in the video code

    Impact: BIOS proofing

    "Glove box" off BIOS interrupts in the video code.

The exact artifacts caused by it are:

- a mode set from 80x25 to 80x25...
- cursor position is reset to the top-left corner, overwriting any 
logs from previous code such as BIOSes or bootloaders. Previously, the 
linux kernel log nicely followed these, now it is intersecting.

("glove box off" is a ventured description to me. Even the German 
translation gave no hint; an image search was required. Suggesting "seal 
off".)

Anyhow, the commit description lacks a bit of information to coders 
whose area of expertise is outside hardware (net/ is what I do), and why 
this commit is needed, given all I seemingly got from it was a 
degradation of my VGA console experience.

Could you elaborate on it, and/or what could be done to address the two 
issues?

thanks,
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/