Messages in this thread | | | From | Keith Owens <> | Subject | Re: 2.4.14-pre8 Alt-SysRq-[TM] failure during lockup... | Date | Wed, 07 Nov 2001 14:49:23 +1100 |
| |
On Tue, 06 Nov 2001 11:10:54 -0800, "Randy.Dunlap" <rddunlap@osdl.org> wrote: >It bugged me because I often use the "debug" boot parameter >to set console_loglevel to 10, but all of a sudden it had been >set back to 6 IIRC! And right now on one of my test >systems it is set to 0 according to /proc/sys/kernel/printk, >although _I_ didn't ask for it to be changed to 0, and >I haven't been able to find what's changing it to 0, since >it was 10 during init/main.c.
Any chance that console_loglevel, default_message_loglevel, minimum_console_loglevel and default_console_loglevel are not together in memory? I see that the patch from Jesper Juhl <juhl@eisenstein.dk> to fix this bug has not gone into the kernel yet.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |