All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: Dave Airlie <airlied@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org
Subject: [regression,bisected] Missing boot messages with VESAFB after VT initialization
Date: Sat, 17 Apr 2010 17:18:55 +0200	[thread overview]
Message-ID: <201004171718.55867.elendil@planet.nl> (raw)

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@redhat.com>
   Date:   Thu Jan 7 17:04:54 2010 +1000
       x86-64: Allow fbdev primary video code

Kernel config is available in: http://lkml.org/lkml/2010/4/16/230

Relevant part of the boot log (I boot with 'quiet'):
[...]
Sat Apr 17 16:52:07 2010: Starting portmap daemon...Already running..
Sat Apr 17 16:52:07 2010: Starting NFS common utilities: statd idmapd.
Sat Apr 17 16:52:08 2010: Setting sensors limits.
Sat Apr 17 16:52:08 2010: Setting console screen modes and fonts.
[Messages after this point are not displayed]
Sat Apr 17 16:52:08 2010: Setting up ALSA...done.
Sat Apr 17 16:52:09 2010: INIT: Entering runlevel: 2
Sat Apr 17 16:52:09 2010: Loading cpufreq kernel modules...done (acpi-cpufreq).
Sat Apr 17 16:52:10 2010: Starting system log daemon....
Sat Apr 17 16:52:10 2010: Starting kernel log daemon....
Sat Apr 17 16:52:10 2010: Starting ACPI services....
Sat Apr 17 16:52:10 2010: Starting system message bus: dbus.
Sat Apr 17 16:52:11 2010: Starting OpenBSD Secure Shell server: sshd.
Sat Apr 17 16:52:11 2010: CPUFreq Utilities: Setting ondemand CPUFreq governor...CPU0...CPU1...done.
Sat Apr 17 16:52:11 2010: Starting HTTP server: boa.
Sat Apr 17 16:52:11 2010: Starting Common Unix Printing System: cupsd.
Sat Apr 17 16:52:13 2010: Starting DirMngr: dirmngr.
Sat Apr 17 16:52:13 2010: Starting MTA: exim4.
Sat Apr 17 16:52:14 2010: Starting LAN Information Server: lisa.
Sat Apr 17 16:52:14 2010: Setting up Machine Check Exceptions trigger... done.
Sat Apr 17 16:52:14 2010: Running Machine Check Exceptions decoder... done.
Sat Apr 17 16:52:14 2010: Starting NFS common utilities: statd idmapd.
Sat Apr 17 16:52:14 2010: Not starting internet superserver: no services enabled.
Sat Apr 17 16:52:14 2010: Setting sysfs variables....
Sat Apr 17 16:52:15 2010: Starting file alteration monitor: FAM.
Sat Apr 17 16:52:15 2010: Starting Hardware abstraction layer: hald.
Sat Apr 17 16:52:17 2010: Starting bluetooth: disabled. see /etc/default/bluetooth.
Sat Apr 17 16:52:17 2010: Starting /usr/sbin/chronyd...
Sat Apr 17 16:52:18 2010: chronyd is running and online.
Sat Apr 17 16:52:18 2010: Starting anac(h)ronistic cron: anacron.
Sat Apr 17 16:52:18 2010: Starting deferred execution scheduler: atd.
Sat Apr 17 16:52:19 2010: Starting periodic command scheduler: crond.
Sat Apr 17 16:52:19 2010: Starting K Display Manager: kdm.

The "Setting console screen modes and fonts" message comes from the init
script /etc/rcS.d/S48console-screen.sh. When that script is run the 2 tux
logos for my 2 CPU cores also disappear.

Cheers,
FJP

             reply	other threads:[~2010-04-17 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17 15:18 Frans Pop [this message]
2010-04-18 21:10 ` [regression,bisected] Missing boot messages with VESAFB after VT initialization 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

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=201004171718.55867.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=airlied@redhat.com \
    --cc=hpa@zytor.com \
    --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.