Jan Engelhardt wrote:
On May 22 2007 12:09, Randy Dunlap wrote:
From: Randy Dunlap <[email protected]>
Add "notime" boot option to prevent timing data from being printed on
each printk message line.
We've seen a few cases of 'time' data locking problems (possibly
involving netconsole or net drivers). If a kernel is built with
CONFIG_PRINTK_TIME=y, it may have a boot locking hang. Booting
with "notime" may (i.e., could) prevent the lock hang and allow the
kernel to boot successfully, without requiring a kernel rebuild.
Wonderful, now we have _three_ options to control time...
time=<bool>
printk.time=<bool>
notime=<bool>
Currently the middle one is "printk.printk_time".
And the first and last are just "time" and "notime", without a bool value.
And as I wrote later, I'd be happy to remove #s 1 and 3 and use only the
middle one, renaming the param so that it _is_ printk.time.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
