Searched full:always_kmsg_dump (Results 1 – 8 of 8) sorted by relevance
106 * printk.always_kmsg_dump boot param" (which is either108 * true); see printk.always_kmsg_dump for more details.
20 * KMSG_DUMP_OOPS will not be logged by default unless printk.always_kmsg_dump
85 controlled by the printk.always_kmsg_dump boot param.
46 ``printk.always_kmsg_dump`` boot param: if unset, it'll be KMSG_DUMP_OOPS,
151 ``printk.always_kmsg_dump`` boot param: if unset, it'll be KMSG_DUMP_OOPS,
4600 printk.always_kmsg_dump=
348 * changing printk.always_kmsg_dump, so instead log everything that in ramoops_pstore_write()350 * based on the combination of printk.always_kmsg_dump and our in ramoops_pstore_write()
4023 static bool always_kmsg_dump; variable4024 module_param_named(always_kmsg_dump, always_kmsg_dump, bool, S_IRUGO | S_IWUSR);4061 * to KMSG_DUMP_OOPS, unless always_kmsg_dump was set. in kmsg_dump()4064 max_reason = always_kmsg_dump ? KMSG_DUMP_MAX : in kmsg_dump()
