On 01/27/2011 09:47 PM, David Miller wrote: > From: "Fabio M. Di Nitto" <fdinitto@xxxxxxxxxx> > Date: Thu, 27 Jan 2011 15:35:19 +0100 > >> According to kernel/print.k: >> >>> /* >>> * By unregistering the bootconsoles after we enable the real console >>> * we get the "console xxx enabled" message on all the consoles - >>> * boot consoles, real consoles, etc - this is to ensure that end >>> * users know there might be something in the kernel's log buffer that >>> * went to the bootconsole (that they do not see on the real console) >>> */ >> >> but my understanding, and please correct if I am wrong, is that when we >> load or initialize modules such as fbcon (I made this patch debugging a >> crash in atyfb), a console is indeed registered and bootconsole disable, >> while in reality the real console is not there yet (in my case fbcon was >> loaded but not atyfb yet). >> At a later stage, once atyfb is loaded, it registers with fbcon and then >> the console output starts again. > > It's not exactly "fbcon", it's the "VT" driver. Thanks for the clarification. I spotted both VT and fbcon (as they are the only two that register as console driver effectively) and of course picked the wrong one ;) > That loads, and nothing has attached to VT yet to provide the actual > console hookup. at least I got this part right... > > "fbcon" waits until a usable driver registers before it hooks itself > into the "VT" layer. > > So this is why we have this large gap of time with no console output. > It's because VT registers before it actually is able to provide > console output services, and frankly that's a bug. :-) Ok, I have no idea how complex and delicate that code is, but I'll try to see if we can actually fix VT to behave as fbcon rather than adding this patch as workaround. Thanks Fabio -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
