Re: [PATCH] console: allow to retain boot console via boot optionkeep_bootcon

[Andrew Morton]

On Wed, 12 Jan 2011 09:40:24 +0100
"Fabio M. Di Nitto" <fabbione@xxxxxxxxxxxx> wrote:

> From: Fabio M. Di Nitto <fdinitto@xxxxxxxxxx>
> 
> On some architectures, the boot process involves de-registering the boot
> console (early boot), initialize drivers and then re-register the console.
> 
> This mechanism introduces a window in which no printk can happen on the console
> and messages are buffered and then printed once the new console is available.
> 
> If a kernel crashes during this window, all it's left on the boot console
> is "console [foo] enabled, bootconsole disabled" making debug of the crash
> rather 'interesting'.
> 
> By adding "keep_bootcon" option, do not unregister the boot console, that
> will allow to printk everything that is happening up to the crash.
> 
> The option is clearly meant only for debugging purposes as it introduces lots
> of duplicated info printed on console, but will make bug report from users
> easier as it doesn't require a kernel build just to figure out where we crash.
> 

I don't get it, as usual.

The architecture does

a) deregister boot console
b) initialize drivers
c) register console

and the patch basically disables step a).

But if we can do that without screwing things up, why not simply change
the architecture to not deregister the boot console until after
initializing the drivers?


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/