linux-kernel - Re: [regression,bisected] Missing boot messages with VESAFB after VT initialization

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 29 Apr 2010 06:25:39 +0200
From:	Frans Pop <elendil@...net.nl>
To:	linux-kernel@...r.kernel.org
Cc:	x86@...nel.org, Alan Cox <alan@...ux.intel.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Ari Entlich <atrigent@....neu.edu>
Subject: Re: [regression,bisected] Missing boot messages with VESAFB after VT initialization

On Thursday 29 April 2010, Frans Pop wrote:
>  * commit eec9fe7d1ab4a0dfac4cb43047a7657fffd0002f
>    Author: Ari Entlich <atrigent@....neu.edu>
>       tty: Add a new VT mode which is like VT_PROCESS but doesn't
>            require a VT_RELDISP
>
> The last one is probably the most likely as the issue occurs after an
> init script loops over all VTs to run 'consolechars' and/or 'charset'.

I just see this patch has already been reverted, so that can't be it.
I'm still seeing the problem with v2.6.34-rc5-270-gbc113f1.
--
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/