Home
last modified time | relevance | path

Searched refs:messages (Results 1 – 200 of 361) sorted by relevance

12

/linux-4.1.27/drivers/media/pci/bt8xx/
Ddst_ca.c160 if ((dst_put_ci(state, command, sizeof(command), state->messages, GET_REPLY)) < 0) { in ca_get_app_info()
167 state->messages[7], (state->messages[8] << 8) | state->messages[9], in ca_get_app_info()
168 (state->messages[10] << 8) | state->messages[11], __func__, (char *)(&state->messages[12])); in ca_get_app_info()
172 length = state->messages[5]; in ca_get_app_info()
180 put_command_and_length(&state->messages[0], CA_APP_INFO, length); in ca_get_app_info()
183 memmove(&state->messages[4], &state->messages[7], 5); in ca_get_app_info()
186 state->messages[9] = str_length; in ca_get_app_info()
187 memmove(&state->messages[10], &state->messages[12], str_length); in ca_get_app_info()
199 if ((dst_put_ci(state, slot_command, sizeof (slot_command), state->messages, GET_REPLY)) < 0) { in ca_get_ca_info()
207 for (i = 0; i < state->messages[0] + 1; i++) { in ca_get_ca_info()
[all …]
Ddst_common.h132 u8 messages[256]; member
/linux-4.1.27/tools/testing/selftests/ipc/
Dmsgque.c30 struct msg1 *messages; member
65 if (msgsnd(msgque->msq_id, &msgque->messages[i].mtype, in restore_queue()
66 msgque->messages[i].msize, IPC_NOWAIT) != 0) { in restore_queue()
95 if (ret != msgque->messages[cnt].msize) { in check_and_destroy_queue()
97 msgque->messages[cnt].msize); in check_and_destroy_queue()
101 if (message.mtype != msgque->messages[cnt].mtype) { in check_and_destroy_queue()
106 if (memcmp(message.mtext, msgque->messages[cnt].mtext, ret)) { in check_and_destroy_queue()
149 msgque->messages = malloc(sizeof(struct msg1) * ds.msg_qnum); in dump_queue()
150 if (msgque->messages == NULL) { in dump_queue()
160 ret = msgrcv(msgque->msq_id, &msgque->messages[i].mtype, in dump_queue()
[all …]
/linux-4.1.27/net/mac80211/
DKconfig103 bool "Trace all mac80211 debug messages"
108 collect all debugging messages, independent of
111 The overhead in this option is that all the messages
142 many debugging messages. It should not be selected
143 on production systems as some of the messages are
153 debugging messages for the managed-mode MLME. It
155 of the messages are remotely triggerable.
164 debugging messages for station addition/removal.
176 of the messages are remotely triggerable.
185 very verbose OCB debugging messages. It should not
[all …]
/linux-4.1.27/Documentation/networking/
Dnetif-msg.txt20 to shed the more verbose level messages as they matured.
21 0 Minimal messages, only essential information on fatal errors.
22 1 Standard messages, initialization status. No run-time messages
23 2 Special media selection messages, generally timer-driver.
24 3 Interface starts and stops, including normal status messages
25 4 Tx and Rx frame error messages, and abnormal driver operation
41 More selective control over the type of messages emitted.
Dbatman-adv.txt131 All error messages, warnings and information messages are sent to
135 or /var/log/syslog. All batman-adv messages are prefixed with
136 "batman-adv:" So to see just these messages try
141 times necessary to see more detail debug messages. This must be
146 Those additional debug messages can be accessed using a special
155 1 - Enable messages related to routing / flooding / broadcasting
156 2 - Enable messages related to route added / changed / deleted
157 4 - Enable messages related to translation table operations
158 8 - Enable messages related to bridge loop avoidance
160 31 - Enable all messages
[all …]
Dnetlink_mmap.txt17 The RX ring is used by the kernel to directly construct netlink messages into
19 additionally as long as the ring contains messages no recvmsg() or poll()
22 The TX ring is used to process messages directly from user-space memory, the
23 kernel processes all messages contained in the ring using a single sendmsg()
32 - conversion of the RX path to get messages from the ring instead of recvmsg()
33 - conversion of the TX path to construct messages into the ring
48 processed in order until no more messages are available, as indicated by
158 to wait for new messages.
167 new messages.
192 processed some messages following it in the ring. The
[all …]
Dtlan.txt48 debug messages, where x is a bit field where the bits mean
51 0x01 Turn on general debugging messages.
52 0x02 Turn on receive debugging messages.
53 0x04 Turn on transmit debugging messages.
54 0x08 Turn on list debugging messages.
Dipvs-sysctl.txt73 0 - transmission error messages (default)
74 1 - non-fatal error messages
89 Higher debugging levels include the messages for lower debugging
91 messages. Thus, logging becomes more and more verbose the higher
164 It controls sending icmp error messages (ICMP_DEST_UNREACH)
222 synchronisation messages.
225 should be used when sending synchronisation messages to a legacy
231 Kernels with this sync_version entry are able to receive messages
Dnetconsole.txt12 This module logs kernel printk messages over UDP allowing debugging of
59 The remote host has several options to receive the kernel messages,
158 messages is high, but should have no other impact.
161 printing all messages from the sender, it is likely that you have set
163 priority messages to the console. You can change this at runtime using:
168 all kernel messages to the console. A specific value for this parameter
Drds.txt47 control messages, while other extensions use the getsockopt/
82 continue to accept and queue incoming messages, even if that
114 notifications via control messages (for instance, there is a
118 messages is described in manpages.
133 However, the kernel will refuse to accept messages to
141 This allows the application to discard all messages queued to a
144 This allows the application to cancel outstanding messages if
149 nuke any pending messages.
200 to ack messages that have been received. The problem is that IB
Drxrpc.txt18 (*) Control messages.
245 (*) When receiving data or messages for a call, MSG_EOR is flagged by recvmsg
250 Any messages waiting in the receive queue for that call will be discarded.
253 and control data messages will be set to indicate the context. Receiving
285 (*) If there's a sequence of data messages belonging to a particular call on
315 AF_RXRPC makes use of control messages in sendmsg() and recvmsg() to multiplex
336 message. recvmsg() passes it in conjunction with all messages except
638 of sendmsg() calls, each with the following control messages attached:
647 control messages attached:
657 control messages attached:
[all …]
Ds2io.txt24 c. View log messages
26 You will see messages similar to:
31 The above messages identify the adapter type(Xframe I/II), adapter revision,
Dsctp.txt8 transparent multi-homing, and multiple ordered streams of messages.
De100.txt113 In order to see link messages and other Intel driver information on your
119 If you wish to see all messages issued by the driver, including debug
120 messages, set the dmesg level to eight.
DREADME.sb1000143 2.) I get "unresolved symbol" error messages on executing `insmod sb1000.o'.
167 6.) I'm getting *tons* of firewall deny messages in the /var/kern.log,
168 /var/messages, and/or /var/syslog files, and they're filling up my /var
173 messages to figure out what the attack is and where it's coming from. Next,
Dx25-iface.txt5 This is a description of the messages to be passed between the X.25 Packet
15 All messages are held in sk_buff's just like real data to be transmitted
Diphase.txt74 You can also check the system log file /var/log/messages for messages
Dcxacru.txt93 Changes in adsl/line state are reported via kernel log messages:
Dphonet.txt9 receive and send messages from/to the modem, or any other external
92 Applications can send Phonet messages using the Phonet datagram socket
Dcan.txt233 creates an appropriate error message frame. Error messages frames can
236 errors may be selected. The reception of error messages is disabled
629 In order to receive such messages, CAN_RAW_RECV_OWN_MSGS must be set.
634 interface to filter and send (e.g. cyclic) CAN messages in kernel space.
636 Receive filters can be used to down sample frequent messages; detect events
638 monitoring of received messages.
664 messages to the broadcast manager from user space have this structure.
693 socket messages the originating CAN interface is provided in can_ifindex.
733 Sent on first message received or on receipt of revised CAN messages.
770 In this case the BCM sends a number of messages ('count') at an interval
[all …]
Dcdc_mbim.txt72 The cdc_mbim driver does not process or police messages on the control
111 The MBIM control messages from the management application *must not*
117 The management application *must* accept control messages of up the
Dcxgb.txt184 The following messages are the most common messages logged by syslog. These
185 may be found in /var/log/messages.
Dl2tp.txt45 handled by userspace. L2TP control frames carry messages between L2TP
173 messages may be optionally enabled per tunnel and per session. Care is
174 needed when debugging a live system since the messages are not
/linux-4.1.27/Documentation/isdn/
DREADME.avmb197 recvqueuelen: number of messages on receive queue
104 recvctlmsg: capi messages received without DATA_B3_IND
106 sentctlmsg: capi messages sent without DATA_B3_REQ
115 nrecvdropmsg: capi messages dropped (messages in recvqueue in close)
116 nrecvctlmsg: capi messages received without DATA_B3_IND
118 nsentctlmsg: capi messages sent without DATA_B3_REQ
124 /proc/capi/capidrv: statistics of capidrv.o (capi messages)
126 nrecvctlmsg: capi messages received without DATA_B3_IND
128 nsentctlmsg: capi messages sent without DATA_B3_REQ
142 nrecvctlmsg: capi messages received without DATA_B3_IND
[all …]
DINTERFACE.CAPI17 corresponding hardware driver. Kernel CAPI then forwards CAPI messages in both
20 Format and semantics of CAPI messages are specified in the CAPI 2.0 standard.
61 After a successful return from register_appl(), CAPI messages from the
70 messages for that application may be passed to or from the device anymore.
182 CAPI messages are passed between Kernel CAPI and the driver via send_message()
187 For the data transfer messages, DATA_B3_REQ and DATA_B3_IND, the actual
240 messages between their transport encoding described in the CAPI 2.0 standard
345 parameter controlling how CAPI messages sent from and to tha controller are
350 If the value of traceflag is non-zero, CAPI messages are logged.
351 DATA_B3 messages are only logged if the value of traceflag is > 2.
DsyncPPP.FAQ12 Q09: Starting the ipppd, I get only error messages from i4l
138 Q09: When I start the ipppd I only get error messages
197 - only a few LCP-conf-req SENT messages (less then 10)
202 Configure your ISDN card to print debug messages and
205 - there are at least a few RECV messages in the log:
DREADME65 write: raw D-channel-messages (format: depends on driver).
66 read: raw D-channel-messages (format: depends on driver).
190 Bit 0: 0 = Suppress response messages.
191 1 = Show response messages.
192 Bit 1: 0 = English response messages.
193 1 = Numeric response messages.
215 Bit 3: 0 = Standard response messages
216 1 = Extended response messages
227 Bit 7: 0 = Don't show display messages from net
228 1 = Show display messages from net
[all …]
DREADME.hysdn143 get the cards and drivers log data. Card messages always start with the
146 appropriate bitmask. The cards log messages will always be send to this
166 0x00000080 Log all card related boot messages
DREADME.gigaset315 The isdnlog program emits error messages or just doesn't work.
345 enables a reasonable set of debugging output messages. These values are
358 in /var/log/, e.g. /var/log/messages.
375 - error messages
376 - relevant system log messages (it would help if you activate debug
DINTERFACE683 With this call, the HL-driver delivers CAUSE-messages to the LL.
684 Currently the LL does not use this messages. Their contents is simply
685 logged via kernel-messages. Therefore, currently the format of the
686 messages is completely free. However they should be printable.
696 With this call, the HL-driver delivers DISPLAY-messages to the LL.
697 Currently the LL does not use this messages.
/linux-4.1.27/Documentation/acpi/
Ddebug.txt11 option is turned off, the debug messages are not even built into the
17 When CONFIG_ACPI_DEBUG=y, you can select the component and level of messages
21 the debug messages.
70 The "debug_level" is a mask that selects different types of messages, e.g.,
71 those related to initialization, method execution, informational messages, etc.
134 Enable PCI and PCI interrupt routing debug messages:
138 Enable all ACPI hardware-related messages:
142 Enable all ACPI_DB_INFO messages after boot:
/linux-4.1.27/fs/pstore/
DKconfig18 bool "Log kernel console messages"
22 messages, even if no oops or panic happened.
25 bool "Log user space messages"
29 interface /dev/pmsg0 to log user space messages. On reboot
56 This enables panic and oops messages to be logged to a circular
/linux-4.1.27/Documentation/ABI/testing/
Ddev-kmsg8 Injecting messages:
19 is not possible to inject messages from userspace with the
21 the messages can always be reliably determined.
37 there are never partial messages received by read().
39 In case messages get overwritten in the circular buffer while
46 messages, in case the buffer gets overwritten. And they allow
96 unrelated messages, but merging the lines in the output
98 logic is used internally when messages are printed to the
Dsysfs-bus-rpmsg23 inbound messages arrive to this address, the rpmsg core
41 inbound messages arrive to this address, the rpmsg core
49 and it is listening for inbound messages that may be sent
65 or remote, starts listening on it for messages (and is thus
71 can start sending messages).
Dsysfs-devices16 Or rely on the uevent messages to notify programs of
21 chain will have emitted uevent messages, so userspace
Dsysfs-class-net-mesh6 Indicates whether the batman protocol messages of the
101 sends its protocol messages.
Dsysfs-class-mic.txt137 debugging purpose and early kernel boot messages, the user can
151 debugging purpose and early kernel boot messages, the user can
/linux-4.1.27/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.1.27/drivers/pnp/
DKconfig25 bool "PNP debugging messages"
29 messages if needed. The messages can be enabled at boot-time with
33 the messages to even be built into the kernel.
/linux-4.1.27/net/dccp/ccids/
DKconfig4 bool "CCID-2 debugging messages"
6 Enable CCID-2 specific debugging messages.
39 bool "CCID-3 debugging messages"
42 Enable CCID-3 specific debugging messages.
/linux-4.1.27/security/integrity/
DKconfig51 controls the level of integrity auditing messages.
52 0 - basic integrity auditing messages (default)
53 1 - additional integrity auditing messages
55 Additional informational integrity auditing messages would
/linux-4.1.27/tools/perf/Documentation/
Dperf.txt22 verbose - general debug messages
23 ordered-events - ordered events object debug messages
24 data-convert - data convert command debug messages
Dperf-data.txt21 It's possible to set data-convert debug variable to get debug messages from conversion,
/linux-4.1.27/arch/arm/
DKconfig.debug62 bool "Verbose user fault messages"
97 bool "Kernel low-level debugging messages via Alpine UART0"
154 bool "Kernel low-level debugging messages via BCM KONA UART"
185 messages to appear over the UART, select this option.
188 bool "Kernel low-level debugging messages via UART1"
195 bool "Kernel low-level debugging messages via UART2"
247 If you have a ZC702 board and want early boot messages to
251 bool "Kernel low-level debugging messages via footbridge serial port"
258 bool "Kernel low-level debugging messages via Digicolor UA0"
265 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
[all …]
/linux-4.1.27/Documentation/nfc/
Dnfc-pn544.txt24 HCI messages consist of an eight bit header and the message body. The
26 33. In HCI mode sent messages are tested for a correct
27 checksum. Firmware update messages have the length in the second (MSB)
/linux-4.1.27/drivers/atm/
DKconfig221 bool "Enable debugging messages"
224 Somewhat useful debugging messages are available. The choice of
225 messages is controlled by a bitmap. This may be specified as a
229 When active, these messages can have a significant impact on the
256 bool "Enable debugging messages"
259 Somewhat useful debugging messages are available. The choice of
260 messages is controlled by a bitmap. This may be specified as a
267 When active, these messages can have a significant impact on the
280 bool "Enable debugging messages"
283 Somewhat useful debugging messages are available. The choice of
[all …]
/linux-4.1.27/Documentation/blockdev/
Dfloppy.txt45 modprobe floppy floppy="omnibook messages"
50 options floppy floppy="omnibook messages"
92 if you frequently get "Unable to allocate DMA memory" messages.
112 master arbitration error" messages from your Ethernet card (or
127 To tune the fifo threshold, switch on over/underrun messages
128 using 'floppycontrol --messages'. Then access a floppy
130 messages, then the fifo threshold is too low. Try with a
135 that you need to do 'floppycontrol --messages' every time you
184 Print debugging messages.
186 floppy=messages
[all …]
DREADME.DAC96039 Please include with the bug report the complete configuration messages reported
40 by the driver at startup, along with any subsequent system messages relevant to
294 is also available in /proc/rd/cN/current_status, and progress messages are
419 earlier version of the driver and the messages have changed somewhat with newer
448 The above messages indicate that everything is healthy, and /proc/rd/status
453 driver logs the following console status messages indicating that Logical
591 earlier version of the driver and the messages have changed somewhat with newer
620 The above messages indicate that everything is healthy, and /proc/rd/status
625 driver logs the following console status messages:
Dparide.txt143 chain ID. While your system is booting, a number of messages are
144 displayed on the console. Like all such messages, they can be
145 reviewed with the 'dmesg' command. Among those messages will be
389 Use 'dmesg' to capture a log of all the PARIDE messages (any messages
/linux-4.1.27/drivers/net/wireless/zd1211rw/
DKconfig16 ZD1211 debugging messages. Choosing Y will result in additional debug
17 messages being saved to your kernel logs, which may help debug any
/linux-4.1.27/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.1.27/net/sctp/
DKconfig24 -- sequenced delivery of user messages within multiple streams,
26 messages,
27 -- optional bundling of multiple user messages into a single SCTP
33 module will be called sctp. Debug messages are handeled by the
/linux-4.1.27/Documentation/
Ddynamic-debug-howto.txt216 t Include thread ID in messages not generated from interrupt context
229 Debug messages during Boot Process
232 To activate debug messages for core code and built-in modules during
241 messages in all code run after this arch_initcall via this boot
293 the sysfs interface if the debug messages are no longer needed:
304 // enable all the messages in file svcsock.c
308 // enable all the messages in the NFS server module
312 // enable all 12 messages in the function svc_process()
316 // disable all 12 messages in the function svc_process()
320 // enable messages for NFS calls READ, READLINK, READDIR and READDIR+.
[all …]
Dbraille-console.txt3 To get early boot messages on a braille device (before userspace screen
20 mode). To review previous messages, press the Insert key to switch to the VT
Drpmsg.txt46 it can send messages on, and if possible, minimize how much control
47 it has over the content of the messages.
55 a unique rpmsg local address (a 32-bit integer). This way when inbound messages
158 inbound messages arrive, they are dispatched by the rpmsg bus using the
172 relevant inbound messages arrive (i.e. messages which their dst address
280 processor supports dynamic name service announcement messages.
290 by the bus, and can then start sending messages to the remote service.
Dinit.txt16 to get more detailed kernel messages.
47 e.g. by providing additional error messages at affected places.
DIPMI.txt96 system. It handles all messages, message timing, and responses. The
111 I2C kernel driver's SMBus interfaces to send and receive IPMI messages
202 all the messages are defined in the spec (and thus makes counting the
207 block of data, even when receiving messages. Otherwise the driver
269 the sequence number of messages. It is simply a long value that is
280 or poll() to wait for messages to come in. However, you cannot use
301 MUST call ipmi_free_recv_msg() on it, or you will leak messages. Note
316 commands (commands are messages that are not responses, they are
514 IPMI messages: 1, driver state: 2, timing: 4, I2C probe: 8
686 is longer than 11 bytes, multiple messages will be sent with increasing
DCodingStyle87 printk messages, because that breaks the ability to grep for them.
568 logging of avc messages output). Does not do system-call
682 Chapter 13: Printing kernel messages
685 of kernel messages to make a good impression. Do not use crippled
686 words like "dont"; use "do not" or "don't" instead. Make the messages
689 Kernel messages do not have to be terminated with a period.
694 which you should use to make sure messages are matched to the right device
696 dev_info(), and so forth. For messages that aren't associated with a
700 Coming up with good debugging messages can be quite a challenge; and once
703 messages. While the other pr_XXX() functions print unconditionally,
[all …]
Dsysrq.txt127 '0'-'9' - Sets the console log level, controlling which kernel messages
129 it so that only emergency messages like PANICs or OOPSes would
166 kernel messages you do not want to see. Selecting '0' will prevent all but
167 the most urgent kernel messages from reaching your console. (They will
Doops-tracing.txt24 /var/log/messages (depends on /etc/syslog.conf). Sometimes klogd dies,
35 nothing. If the messages scroll off the top of the console, you
61 messages ;-)
151 translates important addresses in the kernel log messages to their
Dxillybus.txt232 hardware will send the messages that are necessary to support select() and
252 messages, which inform the host what the interrupt was about.
263 related messages from the FPGA, and has no pipe attached to it.
376 XILLYMSG_OPCODE_NONEMPTY messages sent by the FPGA when a channel goes from
379 These messages are used only to support poll() and select(). The IP core can
Dparport.txt232 the messages that parport_pc spits out when it initialises. There are
240 The kernel messages that parport_pc logs give an indication of which
/linux-4.1.27/arch/mn10300/
DKconfig.debug69 would like kernel messages to be formatted into GDB $O packets so
73 bool "Debug GDB stub by messages to serial port"
76 This causes debugging messages to be displayed at various points
77 during execution of the GDB stub routines. Such messages will be
93 protocol messages generated exchanged with GDB.
/linux-4.1.27/drivers/usb/dwc2/
DKconfig73 Say Y here to enable debugging messages in the DWC2 Driver.
79 Say Y here to enable verbose debugging messages in the DWC2 Driver.
95 Say N here to disable (verbose) debugging messages to be
98 incomplete. Note that this also disables some debug messages
/linux-4.1.27/net/can/
DKconfig29 To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
36 sending of RTR frames, and cyclic CAN messages without permanent user
40 CAN messages are used on the bus (e.g. in automotive environments).
/linux-4.1.27/drivers/s390/net/
DKconfig46 Select this option if you want to be able to receive SMSG messages
51 prompt "Deliver IUCV special messages as uevents (VM only)"
54 Select this option to deliver CP special messages (SMSGs) as
55 uevents. The driver handles only those special messages that
/linux-4.1.27/drivers/usb/wusbcore/
DKconfig33 bool "Enable CBA debug messages"
36 Say Y here if you want the CBA to produce a bunch of debug messages
/linux-4.1.27/drivers/usb/usbip/
DKconfig38 bool "Debug messages for USB/IP"
41 This enables the debug messages from the USB/IP drivers.
/linux-4.1.27/Documentation/w1/
Dw1.netlink7 There are three types of messages between w1 core and userspace:
62 zero or more attached w1_netlink_cmd messages.
64 For event messages there are no w1_netlink_cmd embedded structures,
74 messages looks like the following:
94 exceeds this, it will be split into several messages.
176 Sequence number for event messages is appropriate bus master sequence number
/linux-4.1.27/drivers/pps/
DKconfig26 bool "PPS debugging messages"
29 messages to the system log. Select this if you are having a
/linux-4.1.27/drivers/usb/gadget/
DKconfig48 bool "Debugging messages (DEVELOPMENT)"
52 messages if you use this option to ask for those messages.
54 Avoid enabling these messages, even if you're actively
56 messages that the driver timings are affected, which will
58 trying to track down. Never enable these messages for a
66 messages if you use this option to ask for those messages.
68 Avoid enabling these messages, even if you're actively
70 messages that the driver timings are affected, which will
72 trying to track down. Never enable these messages for a
/linux-4.1.27/Documentation/i2c/
Di2c-protocol53 setting these flags for i2c messages. With the exception of I2C_M_NOSTART, they
60 These messages may still fail to SCL lo->hi timeout.
88 between the messages of one transfer.
Dten-bit-addresses6 I2C messages to and from 10-bit address devices have a different format.
Dsummary21 implement all the common SMBus protocol semantics or messages.
Ddev-interface90 transactions (mixing read and write messages in the same transaction)
129 struct i2c_msg *msgs; /* ptr to array of simple messages */
130 int nmsgs; /* number of messages to exchange */
/linux-4.1.27/sound/core/
DKconfig191 Say Y here to enable verbose log messages. These messages
193 printed messages.
206 Say Y here to enable extra-verbose debugging messages.
208 Let me repeat: it enables EXTRA-VERBOSE DEBUGGING messages.
/linux-4.1.27/Documentation/hwmon/
Dsubmitting-patches74 * If the driver has a detect function, make sure it is silent. Debug messages
75 and messages printed after a successful detection are acceptable, but it
76 must not print messages such as "Chip XXX not found/supported".
79 address if a chip is detected on that address. Unnecessary messages will just
/linux-4.1.27/Documentation/scsi/
Dscsi-changer.txt87 If the module finds the changer, it prints some messages about the
105 CONFIG_SCSI_CONSTANTS=y improves the quality of the error messages a lot
109 You can display these messages with the dmesg command (or check the
111 driver, please include these messages.
118 Enable debug messages (see above, default: 0).
Dadvansys.txt109 b. Kernel messages are routed to console output. Check
117 This will cause printk() messages to be be displayed on the
123 Debug output is logged in /var/log/messages.
131 40960 allows more debug messages to be buffered in the kernel
DNinjaSCSI.txt25 # cat /var/log/messages
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Didle.fuc60 // keep looping while there's pending messages for any process
65 // process the process' messages until there's none left
/linux-4.1.27/drivers/net/wireless/ath/ath6kl/
DKconfig38 Enables ath6kl debug support, including debug messages
51 messages and commands are delivered to using individually
/linux-4.1.27/Documentation/dvb/
Dbt8xx.txt47 verbose=0: messages are disabled
48 1: only error messages are displayed
50 3: other useful messages are displayed
/linux-4.1.27/drivers/ssb/
DKconfig84 bool "No SSB kernel messages"
89 messages are turned off.
100 messages. Turn this on for SSB troubleshooting.
/linux-4.1.27/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.1.27/net/bluetooth/cmtp/
DKconfig6 for CAPI messages. CMTP is required for the Bluetooth Common
/linux-4.1.27/drivers/rapidio/
DKconfig40 bool "RapidIO subsystem debug messages"
44 debug messages to the system log. Select this if you are having a
/linux-4.1.27/drivers/mailbox/
DKconfig5 on-chip processors through queued messages and interrupt driven
24 send short messages between Highbank's A9 cores and the EnergyCore
/linux-4.1.27/drivers/infiniband/hw/amso1100/
DKconfig14 debug messages. Select this if you are developing the driver
/linux-4.1.27/drivers/infiniband/hw/nes/
DKconfig15 This option enables debug messages from the NetEffect RNIC
/linux-4.1.27/net/decnet/netfilter/
DKconfig14 unless you just want to monitor routing messages from other nodes.
/linux-4.1.27/drivers/staging/dgnc/
DTODO3 * remove unecessary error messages. Example kzalloc() has its
/linux-4.1.27/arch/powerpc/kernel/
Dsmp.c209 int messages; /* current messages */ member
224 char *message = (char *)&info->messages; in smp_muxed_ipi_message_pass()
252 all = xchg(&info->messages, 0); in smp_ipi_demux()
261 } while (info->messages); in smp_ipi_demux()
/linux-4.1.27/tools/power/cpupower/
DToDo10 with a --force option and some "be careful" messages
/linux-4.1.27/drivers/md/persistent-data/
DKconfig15 Enable this for messages that may help debug problems with the
/linux-4.1.27/drivers/media/usb/b2c2/
DKconfig14 Say Y if you want to enable the module option to control debug messages
/linux-4.1.27/drivers/media/pci/b2c2/
DKconfig14 Say Y if you want to enable the module option to control debug messages
/linux-4.1.27/Documentation/input/
Dcs461x.txt40 are printed via printk(KERN_INFO "..."), see the /var/log/messages to
41 inspect cs461x: prefixed messages to determine possible card detection
Dwalkera0701.txt40 walkera0701 module, check dmesg for error messages. Connect TX to PC by
/linux-4.1.27/Documentation/blackfin/
Dbfin-gpio-notes.txt58 warning messages like,
66 warning messages.
/linux-4.1.27/Documentation/sysctl/
Dnet.txt121 These parameters are used to limit the warning messages written to the kernel
124 fewer messages that will be written. Message_burst controls when messages will
125 be dropped. The default settings limit warning messages to one every five
133 This was used to control console messages from the networking stack that
137 These messages are now emitted at KERN_DEBUG and can generally be enabled
Dkernel.txt267 from using dmesg(8) to view messages from the kernel's log buffer.
646 logging error messages. See 'man 2 syslog' for more info on
649 - console_loglevel: messages with a higher priority than
651 - default_message_loglevel: messages without an explicit priority
669 Some warning messages are rate limited. printk_ratelimit specifies
670 the minimum length of time between these messages (in jiffies), by
680 seconds, we do allow a burst of messages to pass through.
681 printk_ratelimit_burst specifies the number of messages we can
Dfs.txt95 of error messages about running out of file handles, you might
268 maximum number of messages in a queue value. In fact it is the limiting value
277 default number of messages in a queue value if attr parameter of mq_open(2) is
/linux-4.1.27/arch/microblaze/
DKconfig.debug16 This option turns on/off early printk messages to console.
/linux-4.1.27/Documentation/video4linux/bttv/
DInsmod-options33 bttv_debug=0/1 debug messages (for capture).
35 irq_debug=0/1 irq handler debug messages.
61 messages are lost (16 is known to work on
99 debug = 1 print debug messages
DREADME.freeze20 The only way to capture any kernel messages is to hook up a serial
21 console and let some terminal application log the messages. /me uses
DSound-FAQ96 bttv_gpio=0/1 enable/disable gpio debug messages
103 The messages printed with bttv_gpio=1 look like this:
/linux-4.1.27/drivers/media/platform/
DKconfig98 bool "OMAP 3 Camera debug messages"
101 Enable debug messages on OMAP 3 camera controller driver.
248 bool "VPE debug messages"
251 Enable debug messages on VPE driver.
/linux-4.1.27/net/rds/
DKconfig25 bool "RDS debugging messages"
Dsend.c58 static void rds_send_remove_from_sock(struct list_head *messages, int status);
592 static void rds_send_remove_from_sock(struct list_head *messages, int status) in rds_send_remove_from_sock() argument
598 while (!list_empty(messages)) { in rds_send_remove_from_sock()
601 rm = list_entry(messages->next, struct rds_message, in rds_send_remove_from_sock()
/linux-4.1.27/drivers/pci/pcie/aer/
DKconfig12 (AER) driver support. Error reporting messages sent to Root
/linux-4.1.27/tools/testing/selftests/rcutorture/bin/
Dparse-torture.sh99 …tle no success message, `grep --binary-files=text 'ver:' $file | wc -l` successful version messages
/linux-4.1.27/Documentation/rapidio/
Dtsi721.txt15 For inbound messages this driver uses destination ID matching to forward messages
/linux-4.1.27/fs/afs/
DKconfig18 Say Y here to make runtime controllable debugging messages appear.
/linux-4.1.27/drivers/infiniband/hw/cxgb3/
DKconfig26 amounts of debug messages. Select this if you are developing
/linux-4.1.27/drivers/w1/
DKconfig22 There are three types of messages between w1 core and userspace:
/linux-4.1.27/Documentation/i2c/busses/
Di2c-via29 Q: No error messages, but still i2c doesn't seem to work.
/linux-4.1.27/Documentation/devicetree/bindings/input/
Datmel,maxtouch.txt14 - linux,gpio-keymap: When enabled, the SPT_GPIOPWN_T19 object sends messages
/linux-4.1.27/net/rxrpc/
DKconfig27 Say Y here to make runtime controllable debugging messages appear.
/linux-4.1.27/Documentation/wimax/
DREADME.wimax44 The WiMAX stack is compiled, by default, with debug messages that can
45 be used to diagnose issues. By default, said messages are disabled.
DREADME.i2400m109 and output messages in the kernel log (dmesg, /var/log/messages or
229 5.2.3. Tracing messages received from user space
231 To echo messages received from user space into the trace pipe that the
/linux-4.1.27/Documentation/video4linux/
Dzr364xx.txt12 You can get these values by looking at /var/log/messages when you plug your camera, or by typing : …
25 - debug : set to 1 to enable verbose debug messages
/linux-4.1.27/Documentation/RCU/
Dstallwarn.txt26 Stall-warning messages may be enabled and disabled completely via
140 across repeated stall-warning messages, it is possible that RCU's softirq
167 If a stall lasts long enough, multiple stall-warning messages will be
168 printed for it. The second and subsequent messages are printed at
211 memory, you might see stall-warning messages.
220 messages.
/linux-4.1.27/net/wimax/
DKconfig33 By default, debug messages are disabled at runtime and can
/linux-4.1.27/drivers/video/fbdev/omap2/dss/
DKconfig18 This enables printing of debug messages. Alternatively, debug messages
/linux-4.1.27/Documentation/x86/
Dearlyprintk.txt59 and use lsusb or look at the kernel info messages emitted by the
108 Now this channel of kernel messages is ready to be used: start
119 kernel messages on the host/target system. You can provoke a harmless
Dpat.txt157 Another, more verbose way of getting PAT related debug messages is with
158 "debugpat" boot parameter. With this parameter, various debug messages are
/linux-4.1.27/Documentation/networking/caif/
DREADME63 The first two tx messages sent look like this. Note: The initial
89 The RX messages for LinkSetup look almost identical but they have the
DLinux-CAIF.txt90 - CFCTRL CAIF Control layer. Encodes and Decodes control messages
92 response messages.
/linux-4.1.27/drivers/base/
DKconfig193 bool "Driver Core verbose debug messages"
197 debug messages to the system log. Select this if you are having a
204 bool "Managed device resources verbose debug messages"
208 non-zero, devres debug messages are printed. Select this if
242 bool "Enable verbose FENCE_TRACE messages"
/linux-4.1.27/arch/frv/
DKconfig.debug45 would like kernel messages to be formatted into GDB $O packets so
/linux-4.1.27/arch/m68k/
DKconfig.debug44 Do not output any debug BUG messages within the kernel.
/linux-4.1.27/Documentation/spi/
Dspi-sc18is60226 This driver requires the I2C adapter driver to support raw I2C messages. I2C
/linux-4.1.27/Documentation/sound/alsa/
DProcfile.txt101 bit 0 = Enable XRUN/jiffies debug messages
105 When the bit 0 is set, the driver will show the messages to
209 mode. This will give you the kernel messages when and where xrun
/linux-4.1.27/Documentation/connector/
Dconnector.txt83 u16 len - for *_multi multiple cn_msg messages can be sent
133 uses the connector to request notification and to send messages.
139 Netlink itself is not a reliable protocol. That means that messages can
/linux-4.1.27/drivers/scsi/aic94xx/
DKconfig42 the driver prints some messages to the console.
/linux-4.1.27/arch/arm/mach-ux500/
DKconfig73 Choose the UART on which kernel low-level debug messages should be
/linux-4.1.27/Documentation/infiniband/
Dipoib.txt46 messages.
76 to 'y', tracing messages are compiled into the driver. They are
/linux-4.1.27/drivers/media/usb/pwc/
DKconfig37 messages.
Dphilips.txt69 Should you experience a lot of 'Dumping frame...' messages during
194 1 0x1 Module initialization; this will log messages On
206 messages
/linux-4.1.27/drivers/staging/unisys/Documentation/
Doverview.txt50 destruction messages sent by s-Par's Command service partition through
51 a channel. These messages result in creation (or destruction) of each
146 create/destroy messages that are currently not in use by linux guests.
/linux-4.1.27/net/dccp/
DKconfig33 bool "DCCP debug messages"
/linux-4.1.27/net/decnet/
DKconfig35 network link driver", "Routing messages" and "Network packet
/linux-4.1.27/fs/jfs/
DKconfig41 Y here. This will result in additional debugging messages to be
/linux-4.1.27/drivers/isdn/capi/
DKconfig6 of CAPI messages. This feature can be enabled/disabled via IOCTL for
/linux-4.1.27/drivers/staging/ozwpan/
DREADME24 requests are converted into a request/response pair of messages. (See
/linux-4.1.27/drivers/char/
DKconfig52 tristate "TTY driver to output user messages via printk"
56 If you say Y here, the support for writing user messages (i.e.
57 console messages) via printk is available.
59 The feature is useful to inline user messages with kernel
60 messages.
61 In order to use this feature, you should output user messages
124 If you want kernel messages to be printed out as they occur, you
133 but it'll lose the kernel messages.
/linux-4.1.27/drivers/scsi/mvsas/
DKconfig43 the driver prints some messages to the console.
/linux-4.1.27/Documentation/devicetree/bindings/pci/
Dxilinx-pcie.txt33 The core provides a single interrupt for both INTx/MSI messages. So,
/linux-4.1.27/Documentation/zh_CN/
Demail-clients.txt176 - 在用户帐号设置里，组成和寻址，不要选择"Compose messages in HTML format"。
Doops-tracing.txt43 典型地是/var/log/messages(依赖于/etc/syslog.conf)。有时klogd崩溃了,这种情况下你
/linux-4.1.27/Documentation/watchdog/
Dwdt.txt21 The third interface logs kernel messages on additional alert events.
/linux-4.1.27/Documentation/frv/
Dgdbstub.txt54 command line. That tells the kernel to pass system console messages to
57 messages to the outside world.
/linux-4.1.27/Documentation/PCI/
Dpcieaer-howto.txt72 log level to filter out correctable error messages.
209 messages to root port when an error is detected. Note that devices
215 messages to root port when an error is detected.
227 error is fatal, kernel will print out warning messages. Please refer
/linux-4.1.27/net/
DKconfig32 netlink messages.
39 This option makes it possible to send different netlink messages
46 compat-independent messages instead!
165 You can say Y here if you want to get additional messages useful in
/linux-4.1.27/fs/ufs/
DKconfig42 Y here. This will result in _many_ additional debugging messages to be
/linux-4.1.27/crypto/asymmetric_keys/
DKconfig46 This option provides support for parsing PKCS#7 format messages for
/linux-4.1.27/drivers/firmware/efi/
DKconfig27 will allow writing console messages, crash dumps, or anything
/linux-4.1.27/drivers/net/wireless/ath/ath5k/
DKconfig29 Atheros 5xxx debugging messages.
/linux-4.1.27/Documentation/netlabel/
Dintroduction.txt32 formatting of these NetLabel messages as well as the Generic NETLINK family
/linux-4.1.27/Documentation/sound/oss/
DSoundPro65 If all goes well and you see no error messages, you should be able to
75 messages present in the system log are helpful, try adding 'debug=1'
/linux-4.1.27/drivers/net/can/
DKconfig159 bool "CAN devices debugging messages"
162 debug messages to the system log. Select this if you are having
/linux-4.1.27/drivers/bcma/
DKconfig105 This turns on additional debugging messages.
/linux-4.1.27/net/batman-adv/
DKconfig60 multicast messages.
/linux-4.1.27/fs/quota/
DKconfig22 bool "Report quota messages through netlink interface"
/linux-4.1.27/tools/usb/usbip/
DINSTALL51 some messages telling which features it is checking for.
227 Do not print messages saying which checks are being made. To
229 messages will still be shown).
/linux-4.1.27/Documentation/hid/
Duhid.txt96 may still be pending messages that you can receive with read() but no further
134 reports. If numbered reports are used for a type, all messages from
137 For messages sent by user-space to the kernel, you must adjust the
/linux-4.1.27/Documentation/fmc/
Dmezzanine.txt106 internal structure by means of kernel messages. It is disabled by
107 default because those lines tend to hide more important messages,
/linux-4.1.27/drivers/parisc/
DKconfig150 This driver will also display progress messages on LCD display,
151 such as "INI", "RUN" and "FLT", and might thus clobber messages
/linux-4.1.27/Documentation/arm/
Duefi.txt64 For verbose debug messages, specify 'uefi_debug' on the kernel command line.
DSetup55 all the bootup messages to be displayed correctly.
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-cd.1994-2004145 * 4.06 Dec 17, 1997 -- fixed endless "tray open" messages -ml
171 * messages, since this is not an error.
172 * -- Change error messages to be const
/linux-4.1.27/arch/arm/plat-samsung/
DKconfig31 int "S3C UART to use for low-level messages"
35 Choice of which UART port to use for the low-level messages,
/linux-4.1.27/Documentation/fault-injection/
Dfault-injection.txt68 specifies the verbosity of the messages when failure is
69 injected. '0' means no messages; '1' will print only a single
/linux-4.1.27/net/wireless/
DKconfig212 bool "lib80211 debugging messages"
216 You can enable this if you want verbose debugging messages
/linux-4.1.27/drivers/usb/dwc3/
DKconfig105 Say Y here to enable debugging messages on DWC3 Driver.
/linux-4.1.27/Documentation/usb/
Diuu_phoenix.txt66 - debug will produce a lot of debugging messages...
/linux-4.1.27/drivers/staging/lustre/
DREADME.txt75 Enable mount/umount console messages (or not)
/linux-4.1.27/mm/
DKconfig512 bool "CMA debug messages (DEVELOPMENT)"
515 Turns on debug messages in CMA. This produces KERN_DEBUG
516 messages for every CMA call as well as various messages while
518 This option does not affect warning and error messages.
/linux-4.1.27/Documentation/serial/
Drocket.txt61 in the system log at /var/log/messages.
171 kernel, and type of board you are using. Error messages and log
/linux-4.1.27/Documentation/device-mapper/
Dera.txt27 None of the dm messages take any arguments.
/linux-4.1.27/drivers/s390/block/
Ddasd_eckd.c4504 struct dasd_rssd_messages *messages, in dasd_eckd_read_message_buffer() argument
4566 memcpy(messages, message_buf, in dasd_eckd_read_message_buffer()
4764 static void dasd_eckd_handle_cuir(struct dasd_device *device, void *messages, in dasd_eckd_handle_cuir() argument
4767 struct dasd_cuir_message *cuir = messages; in dasd_eckd_handle_cuir()
4797 struct dasd_rssd_messages *messages; in dasd_eckd_check_attention_work() local
4804 messages = kzalloc(sizeof(*messages), GFP_KERNEL); in dasd_eckd_check_attention_work()
4805 if (!messages) { in dasd_eckd_check_attention_work()
4811 rc = dasd_eckd_read_message_buffer(device, messages, data->lpum); in dasd_eckd_check_attention_work()
4815 if (messages->length == ATTENTION_LENGTH_CUIR && in dasd_eckd_check_attention_work()
4816 messages->format == ATTENTION_FORMAT_CUIR) in dasd_eckd_check_attention_work()
[all …]
/linux-4.1.27/arch/sh/
DKconfig.debug26 This option will cause messages to be printed if free stack space
/linux-4.1.27/drivers/tty/serial/
DKconfig39 messages and warnings and which allows logins in single user mode).
67 messages and warnings and which allows logins in single user mode).
111 kernel messages and warnings and which allows logins in single user
132 console is the device which receives all kernel messages and
200 receives all kernel messages and warnings and which allows
218 receives all kernel messages and warnings and which allows
362 kernel messages and warnings and which allows logins in single user
392 kernel messages and warnings and which allows logins in single user
612 messages and warnings and which allows logins in single user mode).
884 messages and warnings and which allows logins in single user mode).
[all …]
/linux-4.1.27/drivers/staging/speakup/
Dspkguide.txt103 the bootup messages.
110 It will speak all the boot up messages that the kernel prints on the
130 You probably won't want to listen to all the bootup messages every time
133 you during the boot process. You can always review these messages after
139 bootup messages, just press the keypad enter key. This key is located
543 able to speak some of the bootup messages if your system administrator
968 Speakup indicates various conditions to the user by speaking messages.
971 Prior to version 3.1.0 of Speakup, all of these messages were in English,
973 you still heard English messages, such as "left" and "cursoring on."
975 messages via the /sys filesystem.
[all …]
/linux-4.1.27/Documentation/accounting/
Dtaskstats.txt68 The messages are in the format
177 Despite these measures, if the userspace receives ENOBUFS error messages
/linux-4.1.27/fs/cifs/
DKconfig137 Enabling this option adds helpful debugging messages to
147 messages in some error paths, slowing performance. This
/linux-4.1.27/lib/
DKconfig.debug8 messages to be added to the output of the syslog() system
33 This build option allows you to read kernel boot messages
54 Compiles debug level messages into the kernel, which would not
55 otherwise be available at runtime. These messages can then be
98 // enable all the messages in file svcsock.c
102 // enable all the messages in the NFS server module
106 // enable all 12 messages in the function svc_process()
110 // disable all 12 messages in the function svc_process()
187 (declared at kernel/power/somefile.c:1234)" messages.
195 attribute warn_unused_result" messages.
[all …]
/linux-4.1.27/Documentation/dmaengine/
Ddmatest.txt37 emitted. After that only test failure messages are reported until the test
/linux-4.1.27/Documentation/pti/
Dpti_intel_mid.txt28 a console device to further capture debugging messages to PTI.
/linux-4.1.27/drivers/pci/
DKconfig34 messages to the system log. Select this if you are having a
/linux-4.1.27/drivers/net/
DKconfig185 If you want to log kernel messages over the network, enable this.
266 purpose of this is to analyze netlink messages with packet sockets.
268 messages if they tap into the netlink device, record pcaps for further
/linux-4.1.27/Documentation/power/
Dinterface.txt34 we are able to look in the log messages and work out, for example, which code
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DSuspend.txt109 This option prints messages to the serial console before and after
/linux-4.1.27/arch/blackfin/
DKconfig.debug6 bool "Verbose fault messages"
202 to print messages very early in the bootup process.
/linux-4.1.27/scripts/
Dspelling.txt597 messags||messages
598 messgaes||messages
600 messsages||messages
/linux-4.1.27/Documentation/powerpc/
Deeh-pci-error-recovery.txt107 In addition, error messages are reported through RTAS and also through
108 syslogd (/var/log/messages) to alert the sysadmin of PCI resets.
148 syslog (/var/log/messages). This stack trace has proven to be very
/linux-4.1.27/Documentation/cdrom/
Dide-cd114 6. You should be able to see any error messages from the driver with
247 - If you own a Pioneer DR-A24X, you _will_ get nasty error messages
315 always give meaningful error messages.
319 `buffer botch' error messages from the driver.
/linux-4.1.27/Documentation/filesystems/
Dcoda.txt228 be able to retrieve and place messages and to be notified of the
231 when no messages are waiting or being processed.
258 receive and be notified of messages are platform specific. We will
269 proceeds through messages. The synchronization between processes
272 on behalf of a process P, creates messages for Venus, awaits replies
274 of messages is platform specific, but the semantics have (so far)
306 queue of processing messages and setting flags to READ. Venus is
362 retrieves messages by doing a read on the device, replies are sent
1636 +o Before opening, no messages can be placed.
1638 +o Opening will remove any old messages still pending.

12