They get stuffed into a buffer to be printed later. It is possible to
overflow that buffer, and lose some of your printk messages.
* This is printk. It can be called from any context. We want it to
* We try to grab the console_sem. If we succeed, it's easy - we log
* the output and
* call the console drivers. If we fail to get the semaphore we place
* the output
* into the log buffer and return. The current holder of the
* console_sem will
* notice the new output in release_console_sem() and will send it to
* consoles before releasing the semaphore.
* One effect of this deferred printing is that code which calls
* printk() and
* then changes console_loglevel may break. This is because
* is inspected when the actual printing occurs.
/* This stops the holder of console_sem just where we want him
-- Crutcher <firstname.lastname@example.org> GCS d--- s+:>+:- a-- C++++$ UL++++$ L+++$>++++ !E PS+++ PE Y+ PGP+>++++ R-(+++) !tv(+++) b+(++++) G+ e>++++ h+>++ r* y+>*$ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/