Home
last modified time | relevance | path

Searched refs:messages (Results 1 – 25 of 30) sorted by relevance

12

/linux-4.19.296/fs/ntfs/
DKconfig35 performed by the driver as well as additional debugging messages to
36 be written to the system log. Note that debugging messages are
40 you can enable debugging messages by doing (as root):
42 Replacing the "1" with "0" would disable debug messages.
44 If you leave debugging messages disabled, this results in little
45 overhead, but enabling debug messages results in very significant
49 debugging messages while the misbehaviour was occurring.
/linux-4.19.296/drivers/media/dvb-core/
DKconfig36 Enable extra log messages meant to detect packet loss
45 bool "Enable DVB net ULE packet debug messages"
49 Enable extra log messages meant to detect problems while
/linux-4.19.296/fs/pstore/
DKconfig111 bool "Log kernel console messages"
115 messages, even if no oops or panic happened.
118 bool "Log user space messages"
123 interface /dev/pmsg0 to log user space messages. On reboot
150 This enables panic and oops messages to be logged to a circular
/linux-4.19.296/drivers/i2c/
DKconfig124 bool "I2C Core debugging messages"
127 messages to the system log. Select this if you are having a
131 bool "I2C Algorithm debugging messages"
134 of debug messages to the system log. Select this if you are having
139 bool "I2C Bus debugging messages"
143 debug messages to the system log. Select this if you are having
/linux-4.19.296/drivers/s390/net/
DKconfig47 Select this option if you want to be able to receive SMSG messages
52 prompt "Deliver IUCV special messages as uevents (VM only)"
55 Select this option to deliver CP special messages (SMSGs) as
56 uevents. The driver handles only those special messages that
/linux-4.19.296/fs/jffs2/
DKconfig19 This controls the amount of debugging messages produced by the JFFS2
22 enable a few assertions and will print debugging messages at the
26 located and fixed, the detailed messages were relegated to level 2.
29 messages at debug level 1 while the misbehaviour was occurring.
/linux-4.19.296/drivers/s390/char/
Dsclp_rw.c61 buffer->messages = 0; in sclp_make_buffer()
161 buffer->messages++; in sclp_finalize_mto()
458 if (buffer->messages == 0) in sclp_emit_buffer()
Dsclp_rw.h78 unsigned int messages; /* # messages in sccb */ member
/linux-4.19.296/drivers/base/
DKconfig118 bool "Driver Core verbose debug messages"
122 debug messages to the system log. Select this if you are having a
129 bool "Managed device resources verbose debug messages"
133 non-zero, devres debug messages are printed. Select this if
186 bool "Enable verbose DMA_FENCE_TRACE messages"
/linux-4.19.296/fs/afs/
DKconfig18 Say Y here to make runtime controllable debugging messages appear.
/linux-4.19.296/drivers/ntb/
DKconfig23 messages over the ntb hardware. The transport exposes a queue pair api
/linux-4.19.296/drivers/lightnvm/
DKconfig37 vocal error messages, and extra tracking fields in the pblk sysfs
/linux-4.19.296/fs/jfs/
DKconfig38 Y here. This will result in additional debugging messages to be
/linux-4.19.296/drivers/char/
DKconfig55 tristate "TTY driver to output user messages via printk"
59 If you say Y here, the support for writing user messages (i.e.
60 console messages) via printk is available.
62 The feature is useful to inline user messages with kernel
63 messages.
64 In order to use this feature, you should output user messages
99 If you want kernel messages to be printed out as they occur, you
108 but it'll lose the kernel messages.
/linux-4.19.296/drivers/isdn/capi/
DKconfig6 of CAPI messages. This feature can be enabled/disabled via IOCTL for
/linux-4.19.296/fs/ufs/
DKconfig42 Y here. This will result in _many_ additional debugging messages to be
/linux-4.19.296/crypto/asymmetric_keys/
DKconfig42 This option provides support for parsing PKCS#7 format messages for
/linux-4.19.296/drivers/parisc/
DKconfig143 This driver will also display progress messages on LCD display,
144 such as "INI", "RUN" and "FLT", and might thus clobber messages
/linux-4.19.296/fs/quota/
DKconfig22 bool "Report quota messages through netlink interface"
/linux-4.19.296/fs/cifs/
DKconfig159 Enabling this option adds helpful debugging messages to
169 messages in some error paths, slowing performance. This
/linux-4.19.296/drivers/s390/block/
Ddasd_eckd.c5030 struct dasd_rssd_messages *messages, in dasd_eckd_read_message_buffer() argument
5093 memcpy(messages, message_buf, in dasd_eckd_read_message_buffer()
5589 static void dasd_eckd_handle_cuir(struct dasd_device *device, void *messages, in dasd_eckd_handle_cuir() argument
5592 struct dasd_cuir_message *cuir = messages; in dasd_eckd_handle_cuir()
5625 struct dasd_rssd_messages *messages; in dasd_eckd_check_attention_work() local
5631 messages = kzalloc(sizeof(*messages), GFP_KERNEL); in dasd_eckd_check_attention_work()
5632 if (!messages) { in dasd_eckd_check_attention_work()
5637 rc = dasd_eckd_read_message_buffer(device, messages, data->lpum); in dasd_eckd_check_attention_work()
5640 if (messages->length == ATTENTION_LENGTH_CUIR && in dasd_eckd_check_attention_work()
5641 messages->format == ATTENTION_FORMAT_CUIR) in dasd_eckd_check_attention_work()
[all …]
Ddasd_eckd.h387 char messages[4087]; member
/linux-4.19.296/drivers/pci/
DKconfig43 messages to the system log. Select this if you are having a
/linux-4.19.296/drivers/pci/pcie/
DKconfig33 (AER) driver support. Error reporting messages sent to Root
/linux-4.19.296/lib/
DKconfig.debug10 messages to be added to the output of the syslog() system
65 This build option allows you to read kernel boot messages
86 Compiles debug level messages into the kernel, which would not
87 otherwise be available at runtime. These messages can then be
130 // enable all the messages in file svcsock.c
134 // enable all the messages in the NFS server module
138 // enable all 12 messages in the function svc_process()
142 // disable all 12 messages in the function svc_process()
220 attribute warn_unused_result" messages.
723 option will show detailed messages if free stack space drops
[all …]

12