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:14:23 +0200 [thread overview]
Message-ID: <201004290614.24016.elendil@planet.nl> (raw)
In-Reply-To: <201004171718.55867.elendil@planet.nl>
On Saturday 17 April 2010, Frans Pop wrote:
> Initially all messages from init scripts are displayed correctly, but
> after the init script to set up the VT1-VT6 is run, messages from init
> scripts are no longer displayed. Instead the display is blank with only
> a cursor.
>
> However, if I switch back to VT1 from X.Org after the boot has
> completed, the missing messages are visible.
>
> System is x86_64 running Debian stable ("Lenny"). I'm using VESAFB
> (vga=791) and no KMS.
I've done a new bisection for this issue (with cold boots instead of
reboots) and now end up in the following merge:
commit 94468080220162f74dc6ce5c3e95e5fec8022902
Merge: fb7b096 137ee2f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Merge git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty-2.6
Unfortunately I cannot bisect into that merge as I get a NULL pointer bug
after typing the passphrase for my encrypted partition.
I suspect one of the following commits from that merge:
* commit 638b9648ab51c9c549ff5735d3de519ef6199df3
Author: Alan Cox <alan@linux.intel.com>
tty: Fix the ldisc hangup race
* commit 4165fe4ef7305609a96c7f248cefb9c414d0ede5
Author: Alan Cox <alan@linux.intel.com>
tty: Fix up char drivers request_room usage
* commit d9661adfb8e53a7647360140af3b92284cbe52d4
Author: Alan Cox <alan@linux.intel.com>
tty: Keep the default buffering to sub-page units
* 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'.
See http://lkml.org/lkml/2010/4/17/48 for my original mail with some
additional details.
Cheers,
FJP
next prev parent reply other threads:[~2010-04-30 18:46 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 [this message]
2010-04-29 4:25 ` Frans Pop
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=201004290614.24016.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.