On (03/07/19 09:17), John Ogness wrote: > > If the serial console is a really slow one and we have a CPU in atomic > > context spinnig on prb_lock, while the prb_lock is always acquired by > > other CPUs, then it may look like a lock-up scenario. > > When the console is constantly printing messages, I wouldn't say that > looks like a lock-up scenario. It looks like the system is busy printing > critical information to the console (which it is). What if we have N tasks/CPUs calling printk() simultaneously? -ss