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

[Frans Pop]

On Thursday 29 April 2010, Frans Pop wrote:
>  * commit eec9fe7d1ab4a0dfac4cb43047a7657fffd0002f
>    Author: Ari Entlich <atrigent@xxxxxxxxxxx>
>       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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/