On Tue 2019-11-19 10:46:22, Jonathan Richardson wrote: > > > not just when a normal con replaces a bootconsole. A simple way of > > > avoiding the problem I'm seeing is to not even set the CON_PRINTBUFFER > > > flag on my consoles. > > > > This is up to the console driver to decide. > > > > > It skips the replay and the output on all consoles looks fine. The flag > > > is only used by register_console(), although I don't think that is the > > > intended usage? There are no console drivers that do this. > > > > Not sure I'm following. There are consoles that want all logbuf messages > > once those consoles are available. > > I meant mine would be the only driver that didn't set CON_PRINTBUFFER. > Thanks for clarifying why it would be set. I guess what I didn't > understand is why are all the consoles updated (potentially) when a > new console is registered. As I mentioned before I can not set > CON_PRINTBUFFER to avoid the issue but it's probably not what I want. > I would possibly lose some of the log I guess if there was something > in the buffer during registration of the new console. Exactly, many things happen before and during the console registration. There might already be (are) several messages when new consoles are registered. Now, people register more different consoles for different purpose. For example, one is shown on a display, another can be stored by an external device. It makes sense to show all messages on all interfaces. It can cause duplicated messages because there is no support to match proper console with the early one. The current console registration code somehow works only with one early console. Best Regards, Petr
