[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201004290614.24016.elendil@planet.nl>
Date: Thu, 29 Apr 2010 06:14:23 +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 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@...ux-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@...ux.intel.com>
tty: Fix the ldisc hangup race
* commit 4165fe4ef7305609a96c7f248cefb9c414d0ede5
Author: Alan Cox <alan@...ux.intel.com>
tty: Fix up char drivers request_room usage
* commit d9661adfb8e53a7647360140af3b92284cbe52d4
Author: Alan Cox <alan@...ux.intel.com>
tty: Keep the default buffering to sub-page units
* 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'.
See http://lkml.org/lkml/2010/4/17/48 for my original mail with some
additional details.
Cheers,
FJP
--
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/
Powered by blists - more mailing lists