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] [thread-next>] [day] [month] [year] [list]

Message-Id: <201004191403.09593.elendil@planet.nl>
Date:	Mon, 19 Apr 2010 14:03:08 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Dave Airlie <airlied@...hat.com>
Cc:	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	x86@...nel.org
Subject: Re: [regression,bisected] Missing boot messages with VESAFB after VT initialization

On Sunday 18 April 2010, you wrote:
> On Sat, 2010-04-17 at 17:18 +0200, 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 bisected this to the following commit:
> >    commit 477346ff74f4c2aed50e8a0db96a61069f3e5b80
> >    Author: Dave Airlie <airlied@...hat.com>
> >    Date:   Thu Jan 7 17:04:54 2010 +1000
> >        x86-64: Allow fbdev primary video code
>
> Can you diff dmesg with/without this?

There is no relevant difference between the dmesg for 477346ff ("bisect-5": 
bad) and its predecessor b0483e78 ("bisect-6": good). See attachment.

> It shouldn't do anything unless you have multiple framebuffer drivers.

Unfortunately "shouldn't" isn't always the same as "doesn't" :-)

$ cat /proc/fb
0 VESA VGA

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile
    GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
00:02.1 Display controller [0380]: Intel Corporation Mobile
    GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c)

Cheers,
FJP


View attachment "dmesg_2.6.34-bisect.diff" of type "text/x-diff" (36762 bytes)