From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, Alan Cox <alan@linux.intel.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Ari Entlich <atrigent@ccs.neu.edu>
Subject: Re: [regression,bisected] Missing boot messages with VESAFB after VT initialization
Date: Thu, 29 Apr 2010 06:25:39 +0200 [thread overview]
Message-ID: <201004290625.40469.elendil@planet.nl> (raw)
In-Reply-To: <201004290614.24016.elendil@planet.nl>
On Thursday 29 April 2010, Frans Pop wrote:
> * commit eec9fe7d1ab4a0dfac4cb43047a7657fffd0002f
> Author: Ari Entlich <atrigent@ccs.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.
prev parent reply other threads:[~2010-04-30 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 15:18 [regression,bisected] Missing boot messages with VESAFB after VT initialization Frans Pop
2010-04-18 21:10 ` Dave Airlie
2010-04-19 12:03 ` Frans Pop
2010-04-19 12:57 ` Frans Pop
2010-04-29 4:14 ` Frans Pop
2010-04-29 4:25 ` Frans Pop [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201004290625.40469.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=alan@linux.intel.com \
--cc=atrigent@ccs.neu.edu \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).