On Wed, 2005-07-06 at 15:15, Alistair John Strachan wrote: > On Wednesday 06 Jul 2005 22:02, Ingo Molnar wrote: > > * Alistair John Strachan <[EMAIL PROTECTED]> wrote: > > > This is a completely unrelated question, but now we've got everything > > > under control.. how do I make "quiet" actually do something on the RT > > > patchset? > > > > > > Currently I flag it on the kernel cmdline, but I still get everything > > > spewed to my primary VT. > > > > do you have CONFIG_PRINTK_IGNORE_LOGLEVEL enabled perhaps? > > Good idea, but nope. Find attached the config I'm using, and here's the > output > from /proc/cmdline: > > [alistair] 23:07 [~] cat /proc/cmdline > BOOT_IMAGE=2.6.12rt ro root=301 acpi_sleep=s3_bios lapic quiet > > [alistair] 23:07 [~] uname -r > 2.6.12-RT-V0.7.51-06 > > What I see are the kernel messages pre-init not suppressed (like I think they > should be with quiet) and spurious noise from usb, etc. as the system boots > up. sysklogd starts up but the messages are still duplicated on the console. > > Maybe my configuration is subtlely broken. Is anybody else experiencing this?
I see the same thing. "CONFIG_PRINTK_IGNORE_LOGLEVEL is not set" but still printk ignores the loglevel (I commented out the #ifdef in kernel/printk.c to make the spurious messages go away). -- Fernando - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
