Skip to contentSkip to conversation

2.5.67-mm1 cause framebuffer crash at bootup

DISCUSSION Petr Vandrovec 1 participant 1 message Apr 9, 2003

lore
Share & tools
lore
#0 lore raw
Quoted 12 lines · Randy.Dunlap

On Wed, 9 Apr 2003 23:52:51 +0200 "Petr Vandrovec" <[email protected]> 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.
Quoted 3 lines

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.

Thanks. It looks like that I missed that there is still large window where we use fbcon before mode is set on underlying fbdev, even after reorg. I did at console level. For now it is easier to remove this printk...
Petr