NMI watchdog, die(), & console_loglevel

Jonathan Lundell (linux@lundell-bros.com)
Wed, 31 Jul 2002 09:15:07 -0700


The i386 NMI watchdog handler prints a message, sets console_loglevel
to 0 (no output to console), and then kills the current task
(arch/i386/kernel/nmi.c:nmi_watchdog_tick()); it then leaves the
console turned off.

die(), on the other hand, starts out by setting console_loglevel to
15 (print everything), and leaves it there.

Neither behavior seems particularly appropriate, and taken together
they seem at least inconsistent. What's the justification, if any,
and wouldn't it be better to leave console_loglevel alone and set an
appropriate message loglevel? (Not that I'd claim for an instant that
message loglevels are used consistently; have a look at the various
applications of KERN_EMERG, for example.)

-- 
/Jonathan Lundell.
-
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/