On Sat, 16 Dec 2017 10:18:27 -0600
Bruno Wolff III <bruno@xxxxxxxx> wrote:
> It looks like .config has reasonable (the same as Fedora) values for
> CONFIG_BUG, CONFIG_CONSOLE_LOGLEVEL_DEFAULT and
> CONFIG_MESSAGE_LOGLEVEL_DEFAULT.
>
> The loglevel kernel parameter is not used, so the defaults should
> apply.
>
> When I get physical access to the test machine on Monday I can try
> setting loglevel on boot, which might work in the WARN_ON code was
> actually compiled in. My guess is that it isn't, but I don't know why.
It seems to be that WARN_ON is a macro, so is always available.
tools/include/asm/bug.h:#define WARN_ON(condition) ({ \
tools/include/asm/bug.h: int __ret_warn_on = !!(condition); \
tools/include/asm/bug.h: if (unlikely(__ret_warn_on)) \
tools/include/asm/bug.h: unlikely(__ret_warn_on); \
Is it possible you just need to tell the system to display the messages
from the kernel?
sysctrl kernel.printk
should show you the current levels. From memory, higher numbers mean
less priority for what is displayed. I set to 3 4 1 3.
sysctrl -w kernel.printk "3 4 1 3"
You could try upping these to 7 (the max) to see what happens. Or, if
you are inclined, you could just read the man page to see if this
has anything to do with what you want. :-)
_______________________________________________
kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
