Messages in this thread | | | From | "Petr Vandrovec" <> | Date | Thu, 10 Apr 2003 01:00:51 +0200 | Subject | Re: 2.5.67-mm1 cause framebuffer crash at bootup |
| |
On 9 Apr 03 at 15:55, Randy.Dunlap wrote: > 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.
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |