Re: PREEMPT_RT (2.6.33-rt17) disabled printk-to-console after console_init

From: Xianghua Xiao
Date: Tue May 18 2010 - 16:50:04 EST

On Tue, May 18, 2010 at 2:47 PM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
> On Tue, 18 May 2010, Xianghua Xiao wrote:
>> I could not get dmesg output to console/serial and
>> klogd(/var/log/messages) anymore with 2.6.33-rt17 _after_ the kernel
>> boot is done(on non-RT kernel it works fine). I made below changes it
>> starts to work again, however I'm unsure how safe the change is.
>> Please advise.
> Well, obviously it's unsafe if you remove safety checks. And if you
> care to look at the changelog of kernel/printk.c you'll find out why.
> Short story: It's introducing nasty latencies.
> Use "earlyprintk=serial,ttyS0,115200,keep" if you care, but do not
> complain about the resulting latencies.
> Thanks,
> Â Â Â Âtglx

The earlyprintk bootargs did not work...

will try to see if helps on latencies.

While latency is key, we also need klogd to work at least(disabling
output to serial console may be fine), without that hack somehow klogd
did not get invoked and we have nothing logged from the kernel onto
storage device.

Thanks again,
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at