From: "Nikita V. Youshchenko" <yoush@cs.msu.su>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PREEMPT_RT (2.6.33-rt17) disabled printk-to-console after console_init
Date: Thu, 20 May 2010 12:33:55 +0400 [thread overview]
Message-ID: <201005201233.56877@zigzag.lvk.cs.msu.su> (raw)
In-Reply-To: <alpine.LFD.2.00.1005182143100.3368@localhost.localdomain>
> > 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.
Hmm... did a quick look and could not find anything related there.
Could you please give a pointer?
next prev parent reply other threads:[~2010-05-20 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 13:13 PREEMPT_RT (2.6.33-rt17) disabled printk-to-console after console_init Xianghua Xiao
2010-05-18 13:13 ` Xianghua Xiao
2010-05-18 19:28 ` Xianghua Xiao
2010-05-18 19:28 ` Xianghua Xiao
2010-05-18 19:47 ` Thomas Gleixner
2010-05-18 20:49 ` Xianghua Xiao
2010-05-18 20:49 ` Xianghua Xiao
2010-05-20 8:33 ` Nikita V. Youshchenko [this message]
2010-05-20 9:25 ` Sujit K M
2010-05-20 9:25 ` Sujit K M
2010-05-20 9:32 ` Sujit K M
2010-05-20 9:32 ` Sujit K M
2010-05-20 9:47 ` Thomas Gleixner
2010-05-20 10:23 ` Nikita V. Youshchenko
2010-05-20 10:52 ` Thomas Gleixner
2010-05-20 11:12 ` Nikita V. Youshchenko
2010-05-20 11:23 ` Thomas Gleixner
2010-05-20 11:40 ` Nikita V. Youshchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201005201233.56877@zigzag.lvk.cs.msu.su \
--to=yoush@cs.msu.su \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.