From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.67-mm1 cause framebuffer crash at bootup
Date: Wed, 9 Apr 2003 15:55:38 -0700 [thread overview]
Message-ID: <20030409155538.5df5cc1f.rddunlap@osdl.org> (raw)
In-Reply-To: <1B46F2144C@vcnet.vc.cvut.cz>
On Wed, 9 Apr 2003 23:52:51 +0200 "Petr Vandrovec" <VANDROVE@vc.cvut.cz> wrote:
| On 9 Apr 03 at 14:45, Randy.Dunlap wrote:
| > [<c029367a>] fbcon_set_display+0x33a/0x4c0
| > [<c01f8031>] set_inverse_transl+0x41/0xa0
|
| Can you remove 'printk(KERN_DEBUG "%s: %ux%u, vt=%u, init=%u, ...'
| from fbcon_set_display (drivers/video/console/fbcon.c)? On my system
| printk(KERN_DEBUG) does not print nothing to the console even before
| syslogd is started (one wonders why...), but on your system it apparently
| triggers output to console before video mode was set.
Yes, I did that and can report that this one printk() kills it for me.
I.e., it boots and runs fine with this line commented out, but when I
put it back and rebuild, that kernel gets the same oops during boot.
--
~Randy
next prev parent reply other threads:[~2003-04-09 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 21:52 Petr Vandrovec
2003-04-09 22:55 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-09 23:00 Petr Vandrovec
2003-04-09 20:58 Petr Vandrovec
2003-04-09 21:45 ` Randy.Dunlap
2003-04-09 13:51 Chuck Ebbert
2003-04-09 12:24 Petr Vandrovec
2003-04-08 11:22 2.5.67-mm1 Andrew Morton
2003-04-09 9:42 ` 2.5.67-mm1 cause framebuffer crash at bootup Helge Hafting
[not found] ` <PAO-EX01DJb0LxA56iY0000151b@pao-ex01.pao.digeo.com>
2003-04-09 20:30 ` Randy.Dunlap
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=20030409155538.5df5cc1f.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®